Reusable setup
Install the same skill into any project that needs it. Stop copying prompts by hand across repos.
About
Many projects now depend on prompts, skill files, editor rules, and AI tool setup. AIPM makes those files searchable, versioned, and installable with a clear name and version number.
Install the same skill into any project that needs it. Stop copying prompts by hand across repos.
Publish updates as new versions so teams can review changes before adopting them.
Install into Cursor, Claude, and more tools as AIPM grows. Each target gets the right file format.
Software teams have npm for code packages, Terraform for infrastructure, and Docker for containers. But AI setup has no standard. Teams copy prompts from chat, paste rules by hand, and forget which version is current. That works for one person, but it breaks when a team grows or when projects multiply.
AIPM gives AI skills the same install workflow that code packages have. You find a skill in the registry, run an install command, and AIPM writes the right files into your project. The skill has a name, a version, a publisher, and a source link so you can review it before trusting it.
AIPM is not an AI model, chat app, or prompt marketplace. It does not run your AI tools or host your conversations. It manages the files and instructions your AI tools use inside a project. The skills are project files that live with your code and can be reviewed like any other configuration.
Developers and teams who use AI tools in more than one project should use AIPM. It helps keep setup repeatable. Publishers who want to share workflows can create packages and distribute them through the registry. Organizations that want consistent AI behavior across projects can install the same skills everywhere.
Read the install guide to set up the CLI. Then follow the use guide to install your first skill. If you want to share your own workflow, read the publishing guide.