> ## Documentation Index
> Fetch the complete documentation index at: https://docs.decimal.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Registry API

> Browse, fork, and rate public skills. The shared catalog of reusable SKILL.md blocks, ranked by SkillScore.

The registry is the public catalog of skills. Any skill published with `visibility=public` shows up here, ranked by [SkillScore](/guides/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, **use** or **fork** it into your own workspace, and rate it after use.

This is distinct from the [Skills API](/api-reference/skills/overview), 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

```mermaid theme={null}
%%{init: {'theme':'base','themeVariables':{'primaryColor':'#f5f5f4','primaryBorderColor':'#a8a29e','primaryTextColor':'#44403c','lineColor':'#a8a29e'}}}%%
flowchart LR
    A[browse registry] --> B[get a skill]
    B --> C[activations / lineage]
    B --> D[fork into workspace]
    D --> E[edit your fork]
    D --> F[rate the skill]
```

## Common patterns

<CardGroup cols={2}>
  <Card title="Browse and rank" icon="store" href="/api-reference/skills/overview">
    `GET /api/v1/registry/skills` lists public skills. Sort by SkillScore to surface what actually works, not just what's popular.
  </Card>

  <Card title="Fork into your workspace" icon="code-fork">
    `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.)
  </Card>

  <Card title="Trace lineage" icon="diagram-project">
    `GET /api/v1/registry/skills/{skill_id}/lineage` shows where a skill came from and what was forked from it.
  </Card>

  <Card title="Rate after use" icon="star">
    `POST /api/v1/registry/skills/{skill_id}/rate` records your rating. Ratings feed the AI-judge-adjacent signals behind SkillScore.
  </Card>
</CardGroup>

## 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 is a deprecated alias for `/fork` — prefer `/fork`. The SDK's `install()` is a superset: it forks the skill **and** writes the SKILL.md to disk for local editing.

## Related

* [Skills API](/api-reference/skills/overview) — manage the skills your org owns
* [Skill Router](/api-reference/skills/router) — runtime selection + telemetry
* [SkillScore](/guides/skillscore) — how registry skills are ranked
* [Registry Guide](/guides/registry) — hands-on walkthrough