EvilPrime98/claude-spm

Claude sees every skill in ~/.claude/skills in every repo, so the more you collect, the more noise it carries into projects that don't need it. With spm it sees only the skills this project declares, and everyone who clones the repo gets the same set.
| | Without spm | With spm |
| Skills Claude sees | All of ~/.claude/skills, in every project | Only the ones listed in the project's spm.json |
| A teammate clones | Has to guess which skills to install | Runs spm install and gets the declared set |
| Where they come from | Copied by hand | One or more GitHub repos, recorded in spm.json |
bash
npm install -g claude-spm
cd my-project
spm init owner/repo # hides your global skills in this project
spm install graphify # Claude now sees graphify, and nothing else
Isolation works by marking your global skills "off" in .claude/settings.json (skillOverrides). Entries you wrote yourself are left alone, and only the ones spm turned off are removed again. Turn it off with spm init --no-isolate.
Skills are prompts that Claude acts on, so install them from repos you trust. spm update re-copies whatever the repo's HEAD is today; it does not pin a commit yet.
## How it works
It works like npm: spm.json (project root, committed) is your package.json, and .claude/ is your nodemodules (generated, git-ignorable). Delete .claude/ and run spm install to recreate it.
Skills are discovered broadly: any skills/ /SKILL.md at any depth (and skill folders at the repo root) is available. If two share a name, the shallowest wins. A repo (or subfolder) that has a SKILL.md at its root is a single-skill repo: it is installed as one skill, named by the name in its front matter, or else by the repo name. The repo can also point at a subfolder: owner/repo/subdir or a GitHub .../tree/ / URL (useful for monorepos like cursor/plugins/pstack). git must be installed; private repos work through your normal git credentials.
## Install
bash
npm install -g claude-spm
This provides the spm command.
## Quick start
bash
cd my-project
spm init owner/repo # add the skills repo to the pool (optionally owner/repo#ref)
spm repo add other/repo # optional: add more repos to the pool
spm available # list skills in the pool
spm install graphify # copy a skill into ./.claude/skills
spm list # show skills installed in this project
## Commands
| Command | Description |
| spm init [owner/repo] | Create spm.json and .claude/skills, hide global skills |
| spm repo add | Add a repo to the pool |
| spm repo rm | Remove a repo from the pool (--force if skills use it) |
| spm repo list | Show the pool (alias: ls) |
| spm install | Add skills to spm.json and copy them in (aliases: i, add) |
| spm install | Recreate .claude/skills from spm.json |
| spm uninstall | Remove skills from the project (aliases: rm, remove) |
| spm install : | Review and install a skill from a market, pinned to a commit |
| spm update [skill...] | Re-copy installed skills from the repo (--latest moves market skills) |
| spm list | Skills installed in this project (alias: ls) |
| spm available [filter] | Skills available in the pool |
| spm search | Search the skill markets (--market to pick one) |