Yours from the first minute
Rename it, rewrite it or split it into several skills. The frontmatter and the links between files are handled for you.
For operations teams
Turn your runbooks into skills your agent follows.
Checklists and runbooks usually live in a doc nobody has time to keep current. Put the steps in a skill and keep them in one place.
The document you already have
Start from what your team already writes down.
You do not need to author a skill from a blank page. Bring the document, and the guided chat does the structuring.
- 01
Bring the document
Paste a runbook, policy or style guide, or add a link. Whatever you attach is treated as the specification.
- 02
Answer what it does not cover
The assistant proposes the purpose, triggers and workflow, and asks about the cases your document leaves open. You correct it.
- 03
Review and edit
You get a skill in plain Markdown that your whole team can edit in one place.
Documents teams like yours start from
- Runbooks
- Onboarding and offboarding checklists
- Vendor and approval procedures
What you get
A skill is a folder of plain Markdown.
There is no template for this team yet, so you start from your own document. The result is the same shape every skill has.
Files
- SKILL.md
- references/
- scripts/
SKILL.md says when the skill applies. References hold the details that change; scripts hold anything an agent should run.
Before you publish
Test when the skill fires, and when it should stay quiet.
Write sample messages that should trigger the skill and ones that should not, then run them before you publish. A skill that fires on the wrong request is caught here rather than by a customer.
For example: a request to onboard a new vendor should trigger the skill, and a question about the weather should not.
Start with your own document.
Other teams