Start with what you have
Write your own instructions, ask AI for a draft, or import a SKILL.md file or public Markdown file from GitHub.
Keep prompts, docs, diagrams, scripts, and skills in one private, version-controlled home. Reuse them across projects and agents. Attach docs to tasks ahead of time, or bring them in as you work.
Keep the working knowledge you rely on in one private library. Version every change, reuse any document across projects and agents, and stay in control of what gets attached to each task.
Write your own instructions, ask AI for a draft, or import a SKILL.md file or public Markdown file from GitHub.
Each edit saves a version. If a change doesn’t work out, find an earlier version and restore it.
Export as SKILL.md. Your instructions stay readable and usable outside senthion, too.
Write it once. Keep it ready. Use it anywhere.
Assign a task with its skills and context. Your MCP-connected agent loads them, does the work, and reports back.
TASK · PASSWORD RESET FLOW
AGENT IMPLEMENTATION
Help new users understand how senthion keeps their AI materials private and ready to use.
Task complete. Sign-in flow updated; smoke test passed. Ready for your review.
Illustrative session. The exact tools and responses depend on your MCP client.
Fictional examples of how teams might use senthion.
A practical look at how senthion helps you organize the context behind your AI work and bring the right pieces into each task.
Use it to keep the things you find yourself explaining to AI again and again. That might be project briefs, product facts, writing guidelines, research notes, reusable prompts, scripts, diagrams, or agent skills. Organize these resources so you can find the right context when a new task comes along, instead of hunting through old chats or scattered documents.
Your instructions can evolve as your product, team, and workflows change. senthion versions changes so you can review previous iterations and restore an earlier one if a new direction doesn’t work out. That gives you room to experiment without treating every edit as permanent.
No. Bring in an existing SKILL.md file or a public Markdown file from GitHub, or create something new when you’re ready. Start with one useful resource, such as a project brief or a workflow you already rely on. You can build your library over time.
Choose the resources relevant to the work at hand and bring them into the task, project, or agent you’re using. For example, a marketing draft might need your brand voice and product facts, while a coding task needs repository guidance. Reuse the same maintained source across projects instead of copying slightly different versions into every conversation.
Your skills can be exported as SKILL.md, a plain-text format that remains readable and useful beyond the product. Your instructions remain ordinary files that are easy to understand, not mysterious AI settings. You can keep using them with your own tools and workflows.