AIPM
Theme

Examples

Skill publishing examples.

These examples show the whole path: create a skill, stage it, publish it, and install it into an AI tool. Each step has its own command and a short explanation. Install the AIPM CLI once before you start — see the install guide.

Example 1

Code review helper for Cursor

Maya leads a small backend team. Every pull request gets different review comments because each developer prompts Cursor differently. She packages the team's PR checklist as a skill so every project installs the same review standards.

Publish

1. Create the skill folder

Creates a new package folder with a manifest, starter SKILL.md, and .aipmignore. The --targets cursor flag means this skill is for Cursor only.

aipm publish init --name @team/review-helper --template code-review --targets cursor

2. Open the folder

Move into the folder AIPM just created so the next commands run in the right place.

cd review-helper

3. Stage your files

Adds the skill files in this folder to the publish bundle. Run this after you edit SKILL.md or add other files.

aipm publish add .

4. Preview what will be published (optional)

Shows the file list and package size before you push. Use this to catch secrets or extra files early.

aipm publish preview

5. Publish to the registry

Sign in on the website, reserve the package name, create a 5-minute token in the dashboard, then paste it here and push.

AIPM_TOKEN=<5-minute-token> aipm publish push --yes

Install

Install into a project

Adds the published skill to your project and writes the Cursor skill file. --ci skips prompts in scripts or CI.

aipm add @team/review-helper@1.0.0 --target cursor --ci
  • Good for pull request reviews
  • Installs into .cursor/aipm/skills/<skill>.md

Example 2

Sentry issue summariser for Claude

James gets paged when Sentry fires. He spends the first ten minutes rewriting the same triage prompt in Claude. He publishes one skill so incident summaries follow the same format every time.

Publish

1. Create the skill folder

Creates a package for Claude with starter content for issue summaries.

aipm publish init --name @team/sentry-issue-summary --template issue-summary --targets claude

2. Open the folder

Go into the new package folder before staging or publishing.

cd sentry-issue-summary

3. Stage your files

Adds your edited skill files to the publish bundle.

aipm publish add .

4. Validate the package (optional)

Checks the manifest, entry file, and staged files before you publish.

aipm publish validate

5. Publish to the registry

Use a fresh dashboard token. It expires after 5 minutes.

AIPM_TOKEN=<5-minute-token> aipm publish push --yes

Install

Install into a project

Installs the skill as a Claude project skill folder.

aipm add @team/sentry-issue-summary@1.0.0 --target claude --ci
  • Good for incidents, support, and bug triage
  • Installs into .claude/aipm/skills/<skill>/SKILL.md

Example 3

Release notes skill for Cursor and Claude

Priya ships features weekly and uses both Cursor for day-to-day coding and Claude for release drafts. She wants one skill package that works in both tools without maintaining two separate copies.

Publish

1. Create the skill folder

Creates one package that supports both Cursor and Claude.

aipm publish init --name @team/release-notes --template release-notes --targets cursor,claude

2. Open the folder

Move into the package folder you just created.

cd release-notes

3. Stage your files

Adds the skill files to the publish bundle.

aipm publish add .

4. Preview what will be published (optional)

Review included files before pushing a new version.

aipm publish preview

5. Publish to the registry

Push the version to the public registry with a dashboard token.

AIPM_TOKEN=<5-minute-token> aipm publish push --yes

Install

Install for Cursor

Installs the Cursor version of the skill into your project.

aipm add @team/release-notes@1.0.0 --target cursor --ci

Install for Claude

Installs the Claude version into the same or another project.

aipm add @team/release-notes@1.0.0 --target claude --ci
  • Good for teams using more than one AI tool
  • The manifest should include both cursor and claude targets

Example 4

Import an existing Codex skill folder

Alex already built a review skill in Codex. The team wants it on the registry so others can install it with aipm add. He imports the folder instead of starting from scratch.

Publish

1. Import into an AIPM package

Copies an existing skill folder into a new AIPM package layout with a manifest.

aipm publish import ~/.codex/skills/review-helper --name @team/review-helper

2. Open the folder

Go into the imported package folder.

cd review-helper

3. Stage your files

Stages the imported files. Check .aipmignore first so private files stay out.

aipm publish add .

4. Preview what will be published (optional)

Confirms which files will go public before you push.

aipm publish preview

5. Publish to the registry

Publish with a short-lived token from the package dashboard.

AIPM_TOKEN=<5-minute-token> aipm publish push --yes

Install

Install into a project

Installs the published skill for Cursor in this example.

aipm add @team/review-helper@1.0.0 --target cursor --ci
  • Good when an AI tool created the first draft
  • Review .aipmignore before staging imported files