Skip to main content
The registry is the public catalog of skills. Any skill published with visibility=public shows up here, ranked by SkillScore — a quality-only composite computed from real activations (live eval pass rate + AI-judge rating). You browse the registry to find a skill, fork it into your own workspace, and rate it after use. This is distinct from the Skills API, which manages the skills your org owns. The registry is read-mostly: the only writes are forking a skill into your workspace and rating one you’ve used.

​
Lifecycle

​
Common patterns

Browse and rank

GET /api/v1/registry/skills lists public skills. Sort by SkillScore to surface what actually works, not just what’s popular.

Fork into your workspace

POST /api/v1/registry/skills/{skill_id}/fork copies a registry skill into your org as an editable fork. Your edits never touch the public version. (/install is a deprecated alias for the same operation.)

Trace lineage

GET /api/v1/registry/skills/{skill_id}/lineage shows where a skill came from and what was forked from it.

Rate after use

POST /api/v1/registry/skills/{skill_id}/rate records your rating. Ratings feed the AI-judge-adjacent signals behind SkillScore.

​
Fork vs install

fork is the canonical action for copying a registry skill into your workspace. The HTTP /install route is a deprecated alias that does the same thing — prefer /fork. The SDK’s install() is a superset: it forks the skill and writes the SKILL.md to disk for local editing.