Short answer
Use AIPM instead of skills.sh when you want a named version you can pin. Skills.sh is a directory with its own install command. AIPM is a registry that installs the same skill for Claude Code, Codex, and Cursor and records the version in the project. Use whichever has the skill you trust.
| Skills.sh | AIPM | |
|---|---|---|
| What it is | A directory plus an install command | A registry plus versioned installs |
| Version you get | Whatever the repo serves when you install | The version you name, such as @1.2.0 |
| Tools | Many agents, including Claude Code | Claude Code, Codex, and Cursor |
| Team repeat | Re-run the install command | Commit aipm.package.json and run aipm install |
Words used in this guide
- AIPM: a tool that installs and updates reusable AI instructions.
- Package: a named group of files that people can install and update together.
- Workflow: a set of steps used to finish a task.
- Repository or repo: a project folder whose changes are saved and tracked.
- Git: a tool that records file changes so people can review or undo them.
- CLI: a tool that you use by typing commands in a terminal.
What this means
Where they overlap
Both products help developers discover reusable Agent Skills instead of rebuilding the same instructions for every project. Both lead users from a public skill page to an installation workflow.
How AIPM is different
AIPM treats a skill as a named package with a publisher, version, manifest, install command, integrity value, source details, and target list. It can install files for supported tools and keep the selected package version clear. How pinning and updates compare across Git, Claude Code plugins, the Claude app and AIPM: how to share Claude skills with your team.
How to choose
Use the directory that contains the skill you trust. AIPM is useful when your team wants package names, explicit versions, publisher ownership, project-local installation for Claude Code or Codex (Cursor loads both skill folders), and a workflow for publishing updates. Other catalogs (including Skills.sh and SkillMD) may list overlapping or different skills—always check the source and license before installing.
What AIPM is not claiming
AIPM does not claim a larger catalog than Skills.sh or identical safety scanning to every competitor. The honest differentiator is package-manager semantics: named scopes, pinned versions, integrity metadata, and target-aware installs into your repo.
Simple steps
- Search both directories for the job you need.
- Read the skill source and license.
- Check which AI tools the skill supports.
- Compare the install command and version information.
- Test the skill in a non-critical project before team-wide use.
Where to go next
If you want to try this in a real project, start with how to use AIPM and the command reference. If you want to share your own workflow, read the publishing guide.
FAQ
Is AIPM a skills.sh alternative?
Yes, for teams that want a registry plus CLI with pinned versions and Claude Code or Codex install targets (Cursor loads skills from both folders). If you only need to browse and run a directory install command, Skills.sh may already fit. Choose based on the skill source you trust and the install workflow you need.
Is AIPM connected to Skills.sh?
No. They are separate products and directories with separate publishing and installation workflows.
Can the same public skill appear in both directories?
Yes, when its license and publisher allow it. Always follow the original source and avoid publishing someone else's work without clear attribution and permission.