FAQ | AIPM

The registry is not reachable.

Check the registry URL and run curl <registry-url>/health. If it fails, the server or network route is down.

Package not found.

Confirm the exact scoped name and version. AIPM package names use the format @scope/name.

Version already published.

Published versions are immutable. Increase the manifest version and publish again.

The skill installed but does not appear in my tool.

Check that you installed with the right --target, then restart or reload the AI tool if it caches project files.

Can I publish a public skill?

Yes. Sign in with GitHub, create an org, reserve a package name, generate a 5-minute publish token, then push from the CLI.

Can I publish private skills?

Not yet. Current packages are public registry packages. Keep private prompts, credentials, customer data, and internal-only files out of published skills.

My publish token expired.

Generate a fresh token from the package dashboard. Tokens are intentionally short-lived and are not stored by the CLI.

Publisher identity is unavailable on a package.

That package was published before account-backed reservations were attached, or through an admin-only path. Review it carefully before installing.

How do I install the CLI?

Install AIPM CLI 0.2.12 via npm with npm install -g @aipm-registry/cli, via macOS/Linux standalone with curl -fsSL https://github.com/abhisri2090/aipm/releases/download/cli-v0.2.12/install.sh | sh, or via Windows PowerShell with irm https://github.com/abhisri2090/aipm/releases/download/cli-v0.2.12/install.ps1 | iex. Then run aipm --version and aipm doctor.

Where are package files stored?

Metadata is stored by the registry backend. Package tarballs are stored in the configured blob storage backend.

Common questions and fixes.