Publishing Guide

Install the CLI

Install the CLI before running any aipm command.

npm install -g @aipm-registry/cli
aipm --version
aipm doctor # (optional)

1. Create an account and reserve a package name

Sign in with GitHub.
Create an org namespace, such as @team.
Reserve a package name, such as @team/review-helper.
Open the package dashboard. You will use it later to generate a 5-minute publish token.

2. Create a skill folder

The fastest path is to let the CLI create a folder named after the skill. It includes aipm.manifest.json, SKILL.md, and .aipmignore.

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

Manifest shape

Each skill needs an aipm.manifest.json file and a main file, usually SKILL.md.

{
  "schemaVersion": "0.1",
  "name": "@team/review-helper",
  "version": "1.0.0",
  "type": "skill",
  "description": "Review checklist for project PRs",
  "entry": "SKILL.md",
  "targets": ["cursor"],
  "license": "Apache-2.0"
}

3. Check and publish from the CLI

aipm publish explain # (optional)
aipm publish add .
aipm publish status # (optional)
aipm publish preview # (optional)
aipm publish validate # (optional)
aipm publish token --package @team/review-helper # (optional)
AIPM_TOKEN=<5-minute-token> aipm publish push --yes

Starter templates

Templates only create starter SKILL.md content. Pick the closest one, then edit the generated files before you stage and publish.

See the templates guide for when to use each starter.

Code review

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

Starts with review goals, a checklist, and a format for findings.

Issue summary

aipm publish init --name @team/issue-summary --template issue-summary

Starts with sections for impact, evidence, likely cause, and next action.

Release notes

aipm publish init --name @team/release-notes --template release-notes

Starts with sections for highlights, fixes, upgrade notes, and known issues.

Publish an existing AI-tool skill

If Cursor, Claude, Codex, or another AI tool already created skill files, import that file or folder into an AIPM package folder. This copies the source into a new folder and creates the AIPM manifest around it.

aipm publish import ~/.codex/skills/review-helper --name @team/review-helper
cd review-helper
aipm publish add .
aipm publish preview # (optional)

Self-service publishing flow

Create an AIPM account.
Register an organization and reserve a package name such as @team/review-helper.
Generate a publish token that is valid for 5 minutes.
Use the CLI to check, stage, and push the skill files to the registry.
Open the package page and confirm the install command works for the expected target.

Target examples

See supported targets for the folders AIPM writes to.

Cursor-only

"targets": ["cursor"]

Use this when the skill should install only into Cursor.

Claude-only

"targets": ["claude"]

Use this when the skill is built for Claude project instructions.

Multi-tool

"targets": ["cursor", "claude"]

Use this when the same skill should install into more than one AI tool.

Common publishing problems

Problem	What to do
Updating an existing skill	Change the manifest version, then publish again.
Duplicate version error	AIPM does not overwrite versions. Publish a new version.
Invalid package name	Use scoped names like @team/review-helper.
Registry unavailable	Check the registry URL and run curl <registry-url>/health.

Create a skill package and publish it.