spm. skill and plugin manager
A package manager for AI-agent skills. Install a skill once, and it lands wherever every coding agent on your machine looks for it. Teams publish their own catalog so everyone works from the same set.
npm install -g @hiadamhere/spm
No .NET required. Also via Homebrew (brew install hiadamhere/spm/spm), Scoop (scoop install spm), winget (winget install hiadamhere.spm), a standalone binary, or the .NET tool dotnet tool install -g spm. Then run spm --help, or just spm for an interactive REPL.
Coverage
One install, every agent
Every agent that follows the open agent-skills conventions, installed the same way: one shared copy, links everywhere else.
| Where the skill lands | Project scope | Global scope |
|---|---|---|
Shared copy — read directly by every agent that follows the .agents/skills convention | .agents/skills/ | ~/.agents/skills/ |
| Every other selected agent — a link to the shared copy (junction on Windows, no admin; a copy if linking fails) | the agent's own skills/ folder in the project | the agent's own user-level skills/ folder |
The full list — keys, folders, which agents read the shared copy — is in docs/agents.md, or run spm agents to see it with detection status. Detected agents are pre-checked on the interactive checklist; pick a set non-interactively with --agents key1,key2.
Workflow
Two ways to get skills
One-off
Install one now
Point spm at any GitHub repo with skills. It shallow-clones to a temp folder, deploys, and discards the clone — no subscription, no clutter.
spm install anthropics/skills
spm install anthropics/skills/pdf
Ongoing
Subscribe to a library
Add a repo as a catalog to reuse its skills by bare name — they show up in list, and search ranks them by intent (word-order-, stem-, and typo-tolerant).
spm catalog add mine you/skills
spm catalog sync
spm install some-skill
Getting started
Start from a catalog
A catalog is a catalog.json index of skill repositories. Import one, and every repo it lists becomes a subscription.
Curated
The featured index
One command subscribes to spm's curated list of public skill repositories. The index lives as catalog.json in the spm repo, so it updates without a new release.
spm catalog import
spm catalog sync
spm list
For teams
Your own catalog
Write your own catalog.json listing your team's skill repos — private ones included — and host it anywhere your developers can reach. One import line in the onboarding doc, and everyone shares the same skills. Give it a lower priority number than the featured index and your version of a skill name wins.
spm catalog import https://intra/catalog.json
spm catalog add platform you/agent-skills --priority 10
Hands-off
Teach your agents spm
spm ships its own skill, so your agents search and install skills for you instead of you doing it by hand.
spm install spm --global
The skill covers when to reach for spm, every command, and whether to use the CLI or spm's MCP tools.
With it loaded, an agent that hits “is there a skill for X?” runs spm search, shows you the
candidates, and installs the one you pick. The featured catalog provides it, and the first interactive launch
offers to install it for you.
Maintenance
Keep deployments healthy
Skills spread across many folders, so spm can explain what it finds and tidy up — conservatively.
spm doctor # read-only diagnosis
spm cleanup # preview the fixes
spm cleanup --apply # perform them
doctor reports skills whose files went missing, agents left without a copy, broken links,
layouts from older spm versions, and stale clones or leftovers. cleanup only touches what spm can prove
it owns: folders it removes go to a quarantine directory first, and anything untracked is reported and left alone.
Automation
Run spm as an MCP server
An agent can find and install skills itself — no hand-wiring.
spm mcp serve
Point any MCP client at it: spm exposes search, list, info, install,
agents, doctor and the catalog_* commands as tools. Read-only ones are annotated safe;
destructive ones such as uninstall and cleanup are flagged so agents ask first.