Publish once, install where needed
Turn an AI setup into a package so users can install it into the right repo and AI tool.
Publish with AIPM
Publish AI skills so others can install them.
AIPM helps you package prompts, rules, MCP setup, and tool files once. Then other projects can install the same setup from the registry. Publishing uses account ownership, reserved package names, and short-lived CLI tokens.
Benefits
Why publish with AIPM?
Keep team setup in one place
Teams can reserve package names and share approved prompts, skills, and MCP setup without sending files through chat.
Review every change
Each package has versions, so users can see when a skill or prompt changed.
Use cases
What teams can share
- Internal skills for code review, triage, release notes, and support work.
- MCP server setup, tool instructions, and assistant config shared as packages.
- Shared rules for Cursor, Claude, Codex, and future AI tools.
- Public packages that help other developers install useful AI workflows.
Workflow
From local files to an installable package
Reserve
Sign in, create an org, and reserve a package name before publishing.
Prepare
Create or import a skill folder, then stage and validate the public files.
Push
Generate a 5-minute token and push the version from the CLI.
Real user path
Everything needed to publish safely
- Create an account with GitHub.
- Create an org namespace, such as @team.
- Reserve a skill package name, such as @team/review-helper.
- Create or import a local skill folder.
- Stage, preview, and validate the files that will become public.
- Generate a 5-minute publish token in the dashboard.
- Push the staged files from the CLI.
- Open the public package page and verify the install command.