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 0–100 composite of four weighted signals: benchmark lift (32%), live eval pass rate (32%), AI-judge rating (16%), and cross-org adoption (20%). You browse the registry to find a skill, Install or Fork a copy of 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 using a skill (a linked pointer), forking one 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 was an alias for this and was retired 2026-08-11 — it now answers 410.)

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.

Use vs fork vs install

POST /api/v1/registry/skills/{skill_id}/use creates a linked pointer to the public skill — no copy. It takes scope (workspace, the default, offers it to every agent; agent narrows it to the names in agents), mode (latest tracks the newest safe upstream version; pinned freezes one), and version (required when mode=pinned). Because it stays linked, upstream updates reach your agents. scope=agent is a Pro+ capability. POST /api/v1/registry/skills/{skill_id}/fork is the canonical action for copying a registry skill into your workspace as an owned, editable copy that no longer tracks upstream. The HTTP /install route was retired on 2026-08-11 and answers 410 Gone, because install now means a LINK everywhere else in the product — see Vocabulary. Use /use for a linked pointer or /fork for an editable copy.