Overview
Track skills per project
AIPM keeps an aipm.package.json file in your project. It lists the skills you installed and their versions.
Install the AIPM CLI once before running these commands. See the install guide.
Project setup
Initialize a project
This creates aipm.package.json and points it at the public registry.
aipm init --target cursorPrivate packages
Sign in for private packages
Public packages install without an account. If your org has private packages, sign in once from the CLI. AIPM opens the browser, confirms your account, and stores a local session so future installs do not need a token pasted into every command.
aipm login
aipm whoami # (optional)Sign out
Use this when you want to remove the local CLI session from your machine.
aipm logoutInstall and manage
Install a skill
Choose a package from the registry and install it for the AI tool you use.
To install for one tool, choose a target like Cursor or Claude. Private org packages work the same way after aipm login. See supported targets for the folders AIPM writes to.
aipm add @scope/name@1.0.0 --target cursor --ciList installed skills
Show the packages currently recorded in this project lockfile.
aipm listSearch and update installed skills
Search finds registry packages; update checks configured packages for newer versions.
aipm search sentry
aipm updateUpdating a skill
Install the newer version with the same add command. The version is written down, so your team can review what changed.
CI and automation
Use install tokens in CI
Browser login is best for people working locally. For CI or automation, use an org install token with --token or AIPM_TOKEN so the job can read private packages.
AIPM_TOKEN=<install-token> aipm add @scope/private-skill@1.0.0 --target cursor --ciFile layout
Where files go
AIPM writes files into the folder your AI tool expects. For Cursor, skill files go into the project Cursor skill area. For Claude, AIPM writes a project skill folder.
See the targets guide for exact folders and supported tools.