Skip to main content
Choose a publishing method based on where the skills live and how often they change. Each method writes a skill in one workspace. None installs that skill into Claude Code or Codex automatically.

​
Prepare every package

  1. Put SKILL.md at the package root with only the references, templates, examples, scripts, and small assets the skill needs.
  2. Remove secrets, customer data, and private source material.
  3. Decide whether the skill belongs in your personal workspace or a shared workspace. Choose shared scope only when the team needs to discover or maintain the same registry record.

​
Verify the published skill

  1. Open the resulting skill profile and inspect Source.
  2. Confirm the live version, the expected file list, and the source details.
  3. Retrieve the selected version when a consuming environment requires a local copy, then compare its manifest with the source package.
  4. Review any available relationship and usage evidence before treating the version as the team’s maintained copy.
Do not claim publication succeeded until the version is discoverable in the intended scope and the expected package files are visible.

​
Correct a release

Publish a corrected package when source content changes. If you need to return to an earlier package, use Source to select that version and choose Restore. Restore publishes a new version and keeps history intact.