Skip to main content
An Agent Skill is a folder with a SKILL.md at its root — instructions an AI coding agent loads on demand — plus any supporting files (references/*.md, templates, scripts). MasterSkills doesn’t change the format; it gives skills a home, a name, versions, and permissions.

​
Naming

Every registry skill is @org/slug — npm-style, where org is your organization’s namespace:
Slugs are lowercase letters, digits, and dashes. The slug defaults to the name in the skill’s SKILL.md frontmatter when publishing. Kits share the same namespace, so a single masterskills add @acme/<slug> resolves either.

​
Visibility

Publishing defaults to private, always. Making a skill public is an explicit flag.

​
Versions

Versions are integers that bump automatically when the content changes — there is no version field to maintain. Every version records:
  • a sha256 content hash — the CLI verifies it on every download before writing anything to disk
  • size and file count
  • creation time, and a yankedAt timestamp if an admin yanks the version in the panel
The upcoming version number is always shown in the publish manifest before you approve it.

​
Required skills

Admins can mark a skill required for the organization. Required skills show up in everyone’s update check as missing — but they are never installed silently. The agent lists them and asks; the user confirms. This is one of the product’s trust rules.

​
Lifecycle

  • Publish — creates the skill on first publish, adds a version on every subsequent one. See Publish a skill.
  • Archive (unpublish) — retires the skill org-wide. Devices that still have it installed learn on their next sync and are offered the removal; nothing is deleted from anyone’s disk without approval.
  • Yank a version — panel-only; marks one version as not-installable while leaving the skill live.

​
Where skills live on disk

Installed skills have exactly one real copy per machine, in the central store:
Agent skill directories receive links into the store, flattened to org--slug (for example ~/.claude/skills/acme--api-conventions). One download serves every agent; one update refreshes them all. Skills that live inside a project repo are left alone — the repo is already a distribution mechanism.