Skip to content

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/.

Terminal window
capa registry
capa registry list
capa registry path
capa 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.

CommandDescription
listList configured registries (status, type, source, resolved ref)
pathPrint 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
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)

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.

If you removed one, add it back with its original slug; capa installs the bundled copy instead of cloning the repo:

Terminal window
capa registry add infragate/capa@skills-sh
FlagDescription
--type <type>Source type: github, gitlab, url, or claude-marketplace (auto-detected from the source by default)
--no-cacheBypass the on-disk repo cache when fetching
-y, --yesSkip confirmation (required in non-interactive / CI)
FlagDescription
-y, --yesSkip confirmation (required in non-interactive / CI)
FlagDescription
--no-cacheBypass the on-disk repo cache when refreshing
FlagDescription
-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
FormExample
GitHub searchcapa registry add owner/repo@my-reg
GitHub exact pathcapa registry add owner/repo::registries/internal
GitLabcapa registry add gitlab/group/proj::registries/internal --type gitlab
HTTPS URLcapa registry add https://example.com/adapter.ts
Claude marketplacecapa registry add owner/repo (a bare owner/repo is detected as a marketplace), or any source with --type claude-marketplace
Explicit slugcapa registry add owner/repo@my-reg my-reg

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.json catalog. 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.

Terminal window
capa registry list
capa registry path
capa registry add my-org/internal-tools@acme-skills
capa registry add https://example.com/adapter.ts --type url
capa registry add anthropics/claude-plugins-official marketplace
capa registry add my-org/internal-tools@acme-skills --yes # CI
capa registry refresh acme-skills --no-cache
capa registry disable skills-sh
capa registry enable skills-sh
capa registry remove acme-skills
capa registry search "find skills"
capa registry search skills-sh "vercel" -c skills -l 10
capa registry search -q "frontend" -c plugins
# Install an item from a registry
capa add skills-sh:vercel-labs/skills/find-skills