registry
Registries let you browse and install skills/plugins from adapters (for example skills.sh, Claude marketplaces, or internal catalogs). Adapters are materialized under ~/.capa/registries-managed/.
Synopsis
Section titled “Synopsis”capa registrycapa registry listcapa registry pathcapa registry add <source> [slug] [--type <type>] [--no-cache] [-y]capa registry approve <slug> [-y]capa registry remove <slug>capa registry refresh <slug> [--no-cache]capa registry enable <slug>capa registry disable <slug>capa registry search [slug] [query] [-q <query>] [-c <capability>] [-l <n>]Running capa registry with no subcommand is the same as capa registry list.
Subcommands
Section titled “Subcommands”| Command | Description |
|---|---|
list | List configured registries (status, type, source, resolved ref) |
path | Print the managed registries directory |
add <source> [slug] | Fetch a registry adapter, show its SHA-256 and a preview, and install it after you confirm |
approve <slug> | Review and execute a staged adapter that has not been approved yet |
remove <slug> | Delete the registry row and materialized adapter |
refresh <slug> | Re-fetch the adapter from its stored source (refused for a disabled registry: enable it first) |
enable <slug> | Re-enable a disabled registry |
disable <slug> | Hide a registry without removing it |
search [slug] [query] | Search skills/plugins (omit slug to search all enabled registries) |
Default registries
Section titled “Default registries”On the first server start, CAPA seeds three first-party registries: skills-sh, claude-plugins, and cursor-marketplace. Their adapters are compiled into the CAPA binary and pinned by SHA-256: they are never fetched from GitHub. capa registry refresh on these slugs re-installs the bundled copy.
An existing install keeps the adapter copy it already has after you upgrade CAPA. To pick up the copies bundled in the new binary, refresh them (with the server stopped, or use Refresh all in the Web UI):
capa registry refresh claude-pluginscapa registry refresh cursor-marketplaceIf you removed one, add it back with its original slug; CAPA installs the bundled copy instead of cloning the repo:
capa registry add infragate/capa@skills-shregistry add flags
Section titled “registry add flags”| Flag | Description |
|---|---|
--type <type> | Source type: github, gitlab, url, or claude-marketplace (auto-detected from the source by default) |
--no-cache | Bypass the on-disk repo cache when fetching |
-y, --yes | Skip confirmation (required in non-interactive / CI) |
registry approve flags
Section titled “registry approve flags”| Flag | Description |
|---|---|
-y, --yes | Skip confirmation (required in non-interactive / CI) |
registry refresh flags
Section titled “registry refresh flags”| Flag | Description |
|---|---|
--no-cache | Bypass the on-disk repo cache when refreshing |
registry search flags
Section titled “registry search flags”| Flag | Description |
|---|---|
-q, --query <query> | Search query (alternative to the positional query) |
-c, --capability <capability> | Restrict to skills or plugins |
-l, --limit <n> | Max results per registry |
Source forms for add
Section titled “Source forms for add”| Form | Example |
|---|---|
| GitHub search | capa registry add owner/repo@my-reg |
| GitHub exact path | capa registry add owner/repo::registries/internal |
| GitLab | capa registry add gitlab/group/proj::registries/internal --type gitlab |
| HTTPS URL | capa registry add https://example.com/adapter.ts |
| Claude marketplace | capa registry add owner/repo (a bare owner/repo is detected as a marketplace), or any source with --type claude-marketplace |
| Explicit slug | capa registry add owner/repo@my-reg my-reg |
Review before install
Section titled “Review before install”registry add stages the adapter first, then prints its source, SHA-256, and the first lines of the file, and asks before running it:
- Adapters (
github,gitlab,url): confirm to execute the TypeScript in-process with your privileges. - Claude marketplaces: confirm to store the
marketplace.jsoncatalog. No adapter code runs.
The approved SHA-256 is stored with the registry. Whenever CAPA loads the adapter, it re-checks the file on disk against that hash and refuses to load a modified copy. If you decline, the staged files are removed.
Examples
Section titled “Examples”capa registry listcapa registry path
capa registry add my-org/internal-tools@acme-skillscapa registry add https://example.com/adapter.ts --type urlcapa registry add anthropics/claude-plugins-official marketplacecapa registry add my-org/internal-tools@acme-skills --yes # CIcapa registry refresh acme-skills --no-cache # server stoppedcapa registry disable skills-shcapa registry enable skills-shcapa registry remove acme-skills
capa registry search "find skills"capa registry search skills-sh "vercel" -c skills -l 10capa registry search -q "frontend" -c plugins
# Install an item from a registrycapa add skills-sh:vercel-labs/skills/find-skills