spm
Package manager for AI agent skills: install a skill once and it lands in Claude Code, Codex, Antigravity, Cursor, Copilot, Cline, Devin, Aider and 5 more — or share a team catalog so every developer installs the same set. Ships via npm, Homebrew, Scoop, standalone binary or .NET tool.
Install / Use
claude mcp add hiadamhere -- npx -y github:hiadamhere/spmIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of spm
spm scores 83/100 on our quality scale, 2987th of 4,698 Development & Engineering skills we index.
Its MCP Server is 14 KB long, well organised into 19 sections with 16 code examples: a thorough specification that gives an agent plenty to work with.
It has 3 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so spm is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-15. Automated pattern scan on 2026-11-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
spm compared with similar skills
All 4 of these similar skills score higher than spm; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| spm (this skill)by hiadamhere | 83 | 3 | 54d ago | MCP Server |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install spm?
- Run
claude mcp add hiadamhere -- npx -y github:hiadamhere/spm. The install tabs above show the steps for each supported agent. - Which AI agents does spm work with?
- It is written for Claude Code, Claude Desktop, Cursor, GitHub Copilot, Cline, OpenAI Codex, Aider and Devin, as a MCP Server file. Other agents that read the same format can often use it too.
- Is spm safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is spm still maintained?
- The repository was last updated about 2 months ago, so spm is actively maintained.
Skill content
View source on GitHub📦 spm — Skill and Plugin Manager
spm is a package manager for AI agent skills. It installs reusable skills from Git-based catalogs into every coding agent on your machine — one spm install, and the skill lands wherever your agents look for it:
spm follows the open agent-skills conventions, so one install reaches every agent that reads them: the
skill is copied once to the shared .agents/skills/<skill>/ folder (project) or
~/.agents/skills/<skill>/ (global), which every agent following that convention reads directly, and
every other selected agent gets a link to that copy (a junction on Windows, no admin needed; a full copy
if linking fails, or always with --copy). The full agent list with keys and folders is in
docs/agents.md; spm agents prints it with what is detected on your machine.
By default a skill installs to the shared .agents/skills/ copy plus every agent detected on your
machine — use the interactive checklist or the --agents flag to pick a different set. See
Choosing which agents.
For teams: skills come from catalogs — Git repos indexed by a catalog.json. Publish one for your
team (internal repos included) and a single spm catalog import <url> subscribes every developer to the
same set, with your catalog taking priority over the public index. See
Catalog indexes.
Install
npm — no .NET required:
npm install -g @hiadamhere/spm
# or run it without installing:
npx @hiadamhere/spm --help
Homebrew (macOS / Linux):
brew install hiadamhere/spm/spm
Scoop (Windows):
scoop bucket add spm https://github.com/hiadamhere/scoop-spm
scoop install spm
winget (Windows):
winget install hiadamhere.spm
Standalone binary — download the self-contained executable for your platform from the latest release (also no .NET required).
.NET tool — for .NET users (requires the .NET 10 SDK or runtime):
dotnet tool install -g spm
Verify any of them with spm --help, or run spm with no arguments for an interactive REPL.
Two ways to get skills
Install one now — point spm at any GitHub repo that has skills; nothing is kept around:
spm install anthropics/skills # pick one or more of the repo's skills
spm install anthropics/skills/pdf # install one directly
spm shallow-clones the repo to a temp folder, deploys the skill, and throws the clone away. No subscription, no clutter.
Subscribe to a library — when you'll reuse a set of skills, add it as a catalog; its skills then show up in list/search and install by bare name:
spm catalog add mine https://github.com/you/skills.git # or: spm catalog add mine you/skills
spm catalog sync # clone/pull subscribed catalogs
spm list # everything available, with descriptions
spm install some-skill # by name — no URL needed
Or import a curated index of repos in one go:
spm catalog import # spm's official featured catalog
spm catalog sync
Run spm with no arguments for an interactive REPL.
Teach your agents spm
spm ships its own skill, so your agents can search and install skills for you instead of you doing it by hand:
spm install spm --global # the `spm` skill: when to reach for spm, every command, MCP vs CLI
The featured catalog provides it, and the first interactive launch offers to install it after importing the
catalog. With the skill loaded, an agent that hits "is there a skill for X?" runs spm search, shows you the
candidates, and installs the one you pick — via the CLI, or via spm's MCP tools when the host has
spm mcp serve registered (the skill explains which to use when).
Choosing which agents
Every install writes the shared .agents/skills/ copy, which the "universal" agents read as-is (spm agents
marks them *). The remaining agents need their own folder, and you control which get one:
-
On a terminal, install shows a checklist of those agents — the ones detected on your machine are pre-checked (Claude Code when nothing is detected), and your last choice is remembered (space to toggle, enter to confirm).
-
Non-interactively / in scripts, pass
--agentswith comma-separated keys (seespm agentsor docs/agents.md):spm install pdf --agents claude-code,windsurf # these two, plus the shared .agents/skills copy spm install pdf --agents universal # the shared copy only spm agents # every key, with detection statusThe spm 0.3 keys (
claude,gemini,copilot,hermes) still work as aliases.
Combine with the scope flags below (--project / --global / --all) to control where as well as
which, and add --copy to copy the skill into each agent folder instead of linking.
install vs catalog — which do I use?
| | spm install org/repo | spm catalog add / import |
|---|---|---|
| For | grabbing a skill once | a library you'll reuse |
| Keeps a clone? | no (temp, discarded) | yes (a subscription) |
| Reference by | the repo each time | bare skill name |
| Updates | re-fetches the repo | pulls the catalog |
Both honor a repo's custom skills location — see Skill layout.
Discovering skills
spm listshows every skill across your catalogs, grouped by catalog, one line each with its description and install status.spm search <text>(aliasfind) ranks skills by relevance across names and descriptions — not just an exact substring. It's tolerant of word order, partial words/stems, and typos, sospm search "seo website"surfaces a skill described as "analyze a website's SEO and ranking factors."spm info <skill>(aliasshow) prints a detail view: catalog, description, install status/scope, version, and reference-file count.
Descriptions are read from each skill's SKILL.md YAML frontmatter (description:).
Skill layout
A skill is a folder with a SKILL.md (its name + description frontmatter) and optional references/:
my-skill/
├── SKILL.md
└── references/
By default spm looks for skills under skills/ at a repo's root. To keep them elsewhere, add a skills.json at the repo root — vendor-neutral, so any tool can adopt it:
{ "path": "packages/skills" }
path may also be a list: { "path": ["skills", "extra/skills"] }. This works for both install org/repo and subscribed catalogs.
Catalogs
A catalog is a subscription to a skills repo. Manage them with:
spm catalog add <name> <url|org/repo> [--priority N] [--local <path>]
spm catalog import [<catalog.json url | org/repo | official>]
spm catalog sync # clone/pull all subscribed catalogs
spm catalog list
spm catalog remove <name>
spm catalog root [<path>] # where clones are stored (or set SPM_HOME)
- Priority (lower wins) decides which catalog provides a skill when names collide.
--local <path>reuses a clone you already have (or clones there instead of the default root) — great for turning an existing checkout into a catalog.catalog removenever deletes a--localclone.- Private repos work through your existing git auth (SSH keys, credential manager).
- Clone location defaults to
~/.spm/catalogs/; move it per-catalog with--local, globally withspm catalog root <path>, or relocate everything with theSPM_HOMEenv var.
Catalog indexes (catalog.json)
spm catalog import subscribes to every repo listed in a catalog.json index — spm's official one by default, or any URL / org/repo you pass:
{
"name": "spm featured",
"description": "Curated agent skills",
"repos": [
{ "url": "https://github.com/anthropics/skills", "name": "anthropic" },
{ "url": "https://github.com/openai/skills", "path": "skills/.curated", "name": "openai" }
]
}
Each entry needs a url; optional path overrides that repo's skills folder (if it has no skills.json), and optional name/description are for nicer output.
Your own catalog. The index is just a file, so a team can publish its own: list your internal skill
repos in a catalog.json, host it anywhere your developers can reach (a raw Git URL, an org/repo, or a
local path), and one spm catalog import <url> subscribes everyone to the same set. Give a team catalog a
lower --priority number than the featured index and its version of a skill name wins when both provide it.
spm catalog import https://intranet.example/catalog.json
spm catalog add platform you/agent-skills --priority 10
Staying current without thinking about it
When you launch the interactive REPL (a bare spm) in a real terminal, spm offers two courtesies: on a
fresh install with no catalogs, to import the featured catalog and sync it; and when your catalogs were
last synced more than 7 days ago, to sync them now. Each is a question, not a gate — "Not now" is
remembered for a week, "Never ask again" turns it off (spm config prompts on|off toggles it back), and
setting SPM_NO_PROMPT=1 silences it entirely. Nothing is ever asked when spm runs with arguments, in
scripts or CI, with redirected input, or as an MCP server.
Scopes
- Inside a project (a folder with
.gitorpackage.json),spm install <skill>deploys to project-local agent folders. - Outside a project, it deploys globally for every detected agent.
--projectforces project-only;--globalforces global-only;--alldoes both.- To pick which agents receive the skill, see Choosing which agents above.
spm uninstall <skill>removes only that skill's files/sections, using the same scope rules. Runspm uninstallwith no name to pick a scope and then multi-select which installed skills to remove.
Updates
Skill versions are tracked by their source's Git commit SHA.
spm update my-skill # re-fetch this skill, refresh if it changed
spm update # pick which installed skills to update (or updates all non-interactively)
spm resurrect # review skills whose files went missing
An update refreshes only the deployments that still exist, reproducing the exact scope, agents, and project directory the skill was installed with — from anywhere. Skills installed straight from a repo (install org/repo) update by re-fetching their source; subscribed ones update by pulling the catalog.
If you've manually deleted a skill's files, update won't silently restore them — it marks the skill lost and leaves it alone. spm resurrect lists lost skills and lets you restore (reinstall where they were) or forget them. So: update keeps things current; resurrect brings back what you removed.
Health check and cleanup
spm doctor # read-only diagnosis of every tracked skill and spm folder
spm doctor --all # include the healthy ones
spm doctor --untracked # list the skill folders spm doesn't track (by default only counted)
spm cleanup # preview what cleanup would do — changes nothing
spm cleanup --apply # do it (asks first on a terminal; --yes skips the question)
doctor reports, per skill and scope: lost (nothing on disk), partial (an agent's folder is missing),
broken link, 0.3 layout (not yet migrated — spm update <skill> does it), copy, not link and
content differs (a real folder where a link was expected), plus untracked skill folders in your agents'
directories, staging leftovers from interrupted installs, stale catalog clones, and for
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
