Skip to main content
Reference for the registry binary from @atlanai/registry. For what the tool is and how installs are stored, start with the package manager guide.

Commands

Manage

Inspect

Maintain

Sources

add, use, and discover accept: Any form may be suffixed with @tag, @branch, or @sha:
Pin a @sha when you need the install to be reproducible regardless of what the branch does later.

Shared flags

-t claude,cursor and -t claude -t cursor mean the same thing. These are global and work on every command:
-s is selection, matching npx skills. If you are coming from npx plugins, where -s means scope, use -g, -p, or --scope instead.

Scopes

Inside a project the default is project; outside one, user.

Exit codes

These are a scripting contract. In CI, treat 3 as “someone changed an artifact by hand” and 4 as “the credential needs renewing” — they are not interchangeable failures.

Artifact kinds

plugin, skill, agent, command, hook, mcp, rule, lsp. plugin is the container kind: a directory the harness loads whole, keeping the inline hooks and MCP servers its manifest declares. The vocabulary matches the open-plugin conventions, so a repository written for npx plugins needs no translation. Harnesses accept different subsets — run registry targets to see what each detected harness supports.

Examples

Install only the skills you want, into one harness:
Check a repository before committing to it:
Verify a project in CI without letting it rewrite the lock:
Find out where something came from, then remove it:
Reclaim disk:

Package manager guide

Scopes, storage layout, and keeping a project in sync.

atlanai CLI reference

The other CLI — publishing to Agent Registry.