How to publish
1. Start a draft
Open Publish a skill. The builder generates a valid SKILL.md live as you type,
with a starter body template you can replace.
2. Fill the frontmatter
Set the name, description, category, license, compatibility targets and any
allowed-tools. Validation errors appear next to each field, and the raw file preview
updates on every keystroke.
3. Write the body
Cover when to use, the workflow, expected input, the output contract and guardrails. The body must be at least 200 characters to publish.
4. Add an example
Provide one representative input and the output your skill should produce. This is shown on the public skill page and helps operators trust the skill before installing.
5. Save a version
Every save can create a new semantic version with a changelog. The editor shows a side-by-side diff against the previous version so reviewers can see exactly what changed.
6. Publish
Publishing flips the status from draft to published and makes the skill appear in
Explore immediately. You can unpublish at any time; admins may unpublish skills that
violate policy.
Status values
| Status | Visible in Explore | Editable |
|---|---|---|
draft | no | yes |
in_review | no | yes |
published | yes | yes (new version) |
unpublished | no | yes |
Good practice
- One job per skill. Split anything that needs "or".
- Write the description for routing, not for marketing.
- Keep the body under a few thousand words and link out for reference material.
- Never include credentials or customer data.