Skills
Skill Lifecycle
How a skill moves from draft to proposed to published, with versioning and the permissions each step requires.
A skill moves through three statuses before agents can use it. Only published skills are bundled into the team's agent context package.
| Status | Meaning |
|---|---|
draft | Saved but not submitted. Editable; not visible to agents by default. |
proposed | Submitted for review. Awaiting publish. |
published | Approved and live — bundled into the team's agent context. |
The flow
- Create or edit a skill → it's a
draft. - Submit for review → the draft becomes
proposed. - Publish → the version becomes
publishedand agents can load it.
Editing a published skill saves a new draft version; the previously published version keeps serving agents until you publish the new one.
Submit for review
- UI: use Submit for review in the skill editor.
- MCP: call
wato_save_skill_draftwithsubmitForReview: true.
Publish
- UI: use Publish in the skill editor.
- MCP: call
wato_publish_skillwith the skillidorslug.
wato_publish_skill({ "id": "debug-connector" })Publishing stamps the version as published and makes it the version agents receive.
Versioning & diffs
Every save creates a new sequential version of the skill.
- Open Teams → [Team] → Setup → Skills → [skill] → diff to compare two versions.
- The diff shows line-by-line changes to
SKILL.mdand every bundled file. - You can restore an older version from the diff view.
Permissions
| Permission | Grants |
|---|---|
skills:read | Read published skills. |
skills:propose | Save drafts and submit them for review. |
skills:publish | Publish skills. |
Team admins (and org admins, or holders of teams:manage) can both save drafts
and publish, regardless of the individual skill permissions.