Publish, deprecate, and archive a skill

A skill moves through four states — Draft → Published → Deprecated → Archived — and the status badge in the editor header always shows where it stands. Understanding the lifecycle explains most of how versioning and plan limits work.

Draft: where editing happens

Every skill starts as a draft, and every edit happens in one. Drafts are unlimited on every plan — write as many skills, and as many revisions, as you like. Nothing in a draft reaches your agents or AI tools.

Publish: freeze it and make it live

Publishing does two things at once:

• Freezes the version. A published version is immutable — it can never be silently edited, which is what makes history trustworthy.
• Makes it the live version. Agents and connected AI tools (Claude, ChatGPT, Cursor) immediately use it.

Editing a published skill automatically opens a new draft — the editor shows a "draft in progress" badge — and the published version keeps running untouched until you publish again. Re-publishing an updated version of an already-published skill does not use another Free-plan slot; only distinct published skills count.

Published does not mean public. Publishing changes which version runs, never who can see the skill. Your published skills are exactly as private as your drafts — see where skills live.

Deprecate: retire it gracefully

Deprecating marks a skill as no longer recommended and takes it out of live use. On the Free plan, deprecating a published skill frees one of your 10 slots — retire an old skill to make room for a new one.

Archive: close the book

Archiving is the end state for skills you're done with entirely. The skill and its history are preserved, out of everyone's way.

Availability

All plans. Publishing requires edit access to the skill. Free includes 10 published skills; Team and above are unlimited.