AIPM
Theme

Use AIPM

Install AI skills into your project.

AIPM adds the files an AI tool needs directly to your repo. Your prompts, rules, and skill files stay with the code instead of living in scattered notes.

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. Use --target cursor, --target claude, or --target codex.

aipm init --target claude

One-shot install

Install without project tracking

--no-init writes the skill into your AI tool folder and leaves aipm.package.json and aipm-lock.json untouched. Use it when you want the files once and do not need teammates to restore the same pin with aipm install.

aipm add @scope/name@1.0.0 --target claude --no-init

The same flag works on aipm update @scope/name --no-init (latest version, and a package name is required) and aipm remove @scope/name --no-init. Prompt URLs still need project tracking. If the project is already initialized, the CLI asks whether to keep one-shot mode. --ci --no-init fails in that case.

Private 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 logout

Install 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 claude, codex, or cursor. 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 claude --ci

List installed skills

Show the packages currently recorded in this project lockfile.

aipm list

Search and update installed skills

Search finds registry packages; update checks configured packages for newer versions.

aipm search sentry
aipm update

Updating a skill

Install the newer version with the same add command. The version is written down, so your team can review what changed.

Setting this up for a team? Commit aipm.package.json and aipm-lock.json, and teammates run aipm install. The team sharing guide compares this with committed skills, plugin marketplaces and Claude app sharing.

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 claude --ci

File layout

Where files go

AIPM writes files into the folder your AI tool expects. Claude Code gets .claude/skills/<skill>/SKILL.md, Codex gets .agents/skills/<skill>/SKILL.md, and the Cursor target writes .cursor/skills/<skill>/SKILL.md.

If the project has more than one of .cursor, .claude, and .codex, aipm asks where to install. Choose one tool for a normal copy, or .ai to keep the skill in .ai/skills/<skill>/ and shortcut every detected tool. In CI, pass --shared for that layout, or --target for one tool.

See the targets guide for exact folders and supported tools.