Skip to content

Registries

Registries let you browse and install skills or plugins beyond a single owner/repo URL. Each registry is tracked in capa’s database; the adapter is materialized under ~/.capa/registries-managed/<slug>/.

Supported types: github, gitlab, url, and claude-marketplace.

For the full lifecycle (add, refresh, disable, Web UI, Claude marketplace), see Managing registries.

capa ships with skills-sh, claude-plugins, and cursor-marketplace already configured. Their adapters are bundled in the capa binary and pinned by SHA-256: they are never downloaded from GitHub. See Managing registries.

Terminal window
capa registry # same as list
capa registry list
capa registry path # ~/.capa/registries-managed/
capa registry add owner/repo@my-reg
capa registry add owner/repo::registries/internal --type gitlab
capa registry add https://example.com/adapter.ts
capa registry add owner/repo@my-reg my-reg # explicit slug
capa registry add owner/repo@my-reg --yes # skip the confirmation (CI)
capa registry approve <slug> # execute a staged adapter after review
capa registry refresh <slug>
capa registry enable <slug>
capa registry disable <slug>
capa registry remove <slug>
capa registry search <query>
capa registry search <slug> <query>
capa registry search -q design --capability skills

Full flag details: CLI: registry.

  1. Choose a source

    • GitHub / GitLab: owner/repo@name (search) or owner/repo::path/to/adapter (exact)
    • Public HTTPS URL to an adapter.ts / .js / .mjs file (localhost and private addresses are rejected)
    • Claude marketplace: see below
  2. Install the adapter

    Terminal window
    capa registry add my-org/internal-tools@acme-skills

    capa derives a slug from the source (for example acme-skills). Pass a second argument to override. Review the printed SHA-256 and source preview, then confirm (or pass --yes in CI).

  3. Verify

    Terminal window
    capa registry list

    Confirm the registry shows as healthy / enabled.

  4. Install an item

    Terminal window
    capa add skills-sh:vercel-labs/skills/find-skills
    capa install

Point at a marketplace repo that publishes marketplace.json (source shaped like owner/repo). A bare owner/repo is detected as a marketplace; you can also set the type explicitly. Marketplaces are JSON catalogs, so no adapter code runs:

Terminal window
capa registry add anthropics/claude-plugins-official my-marketplace --type claude-marketplace

Then install with the usual slug:itemId form. Browse and manage registries from the Web UI as well (Registries → Manage registries).

Terminal window
capa add <slug>:<itemId>

The registry adapter decides whether the item is a skill or a plugin. You can still pass --plugin / --skill; if they conflict with the adapter result, capa warns and follows the adapter.

In the Web UI registry browser, items already present in the project show an Installed check mark instead of Add.