Skills
Reusable, versioned capability packages that can be reviewed once and installed into a project or user workspace.
From repository to installation
SKILL.md and allowed package files at a selected commit.
Paths, scripts, tools, publisher, tags, and media are indexed.
Content-only or reviewed executable releases become installable.
A pinned release is installed for Codex, Claude, or both.
Package shape
A skill starts with SKILL.md YAML frontmatter containing a lowercase slug and description. Packages may include reviewed files under supported directories such as references/, assets/, scripts/, examples/, and templates/.
The registry pins every release to a Git commit. Installation does not follow a moving branch implicitly.
Scanning and review
- Content only: instructions and references without executable behavior.
- Executable reviewed: scripts, executable files, dynamic tool declarations, or scanner findings require an explicit review decision.
- Publisher identity, category, source tags, commit, package files, and preview media remain visible in the registry record.
Install and update
Choose a project, installation scope, and target agent:
- Project scope installs only for that project.
- User scope makes the skill available in the user container.
- Targets can be Codex, Claude, or both.
Checking an installation compares its pinned release with the current published release. Updating is always explicit.
Publish from GitHub
Regular publishers select a repository authorized by their GitHub App installation. Administrators may index any public GitHub repository.
For administrator publications, the registry derives the visible publisher from the repository owner or organization. The administrator remains the reviewer, not the displayed author.