The registry is not reachable.
Check the status page or run curl <registry-url>/health and curl <registry-url>/ready. Health checks the API. Ready checks the database and package storage.
FAQ
Common questions and fixes.
Short answers for the problems users hit while publishing and installing skills.
Package not found.
Check the exact scoped name and version. If the package is private, run aipm login and retry, or pass an explicit install token in CI.
Version already published.
Published versions cannot be changed. Increase the manifest version and publish again.
The skill installed but does not appear in my tool.
Check that you used the right --target: --target cursor writes .cursor/skills/<skill>/SKILL.md, --target claude writes .claude/skills/<skill>/SKILL.md for Claude Code, and --target codex writes .agents/skills/<skill>/SKILL.md for Codex. Then restart or reload the AI tool if it caches project files. To see every folder each tool reads, go to where are Claude skills stored?
Can I install a skill without aipm.package.json?
Yes. Add --no-init to aipm add, aipm update, or aipm remove. AIPM writes or removes the skill files and does not create or update aipm.package.json or aipm-lock.json. Prompt URLs still need project tracking. See the use guide.
How does my team keep the same skill versions?
Commit aipm.package.json and aipm-lock.json. Teammates run aipm install to get the same pinned versions, aipm update moves a skill to its latest version, and aipm remove uninstalls it. In CI, run aipm install --ci --target <tool> with an org install token. Pin exact versions (@scope/name@1.2.0); version ranges are not supported.
Can I publish a public skill?
Yes. Sign in with GitHub, create an org, reserve a package name, generate a 5-minute token, then publish from the CLI. See the publishing guide for the full flow.
Can I publish private skills?
Yes. Reserve the package under an org and set package visibility to private. Members install private packages after aipm login; CI can use an org install token.
How do I avoid leaking files while publishing?
See the security guide for preview checks, .aipmignore, and incident steps.
What account data does AIPM use?
AIPM uses your account identity for publishing, profile details for ownership, org and package records for registry ownership, and short-lived tokens for CLI publishing.
What content is not allowed in public packages?
Do not publish secrets, private prompts, customer data, confidential documents, malware, misleading content, or names that impersonate another person, company, project, or tool.
My publish token expired.
Generate a new token from the skill dashboard. Tokens are short-lived and are not stored by the CLI.
Publisher identity is unavailable on a package.
That package does not have a linked publisher account. Review it carefully before installing.
How do I install the CLI?
Run npm install -g @aipm-registry/cli (Node.js 20 or later). Then run aipm --version and aipm doctor.
Where are package files stored?
Package metadata is stored by the registry. Package tarballs are stored in blob storage.