skillpm MCP server
Commit Nov 15, 2026Manages Agent Skills by using the npm registry to publish, install, version, and link modular AI agent capabilities.
Also known as sbroenne/skillpm
- Stars
- 14
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 15, 2026
- License
- MIT
What is skillpm MCP?
skillpm manages Agent Skills by using the npm registry to publish, install, version, and link modular AI agent capabilities.
Summary generated from the project's README
About skillpm MCP server
skillpm provides a way to manage modular AI agent capabilities by treating them as standard npm packages. It bridges the gap in the Agent Skills specification by offering a registry, installation commands, and dependency management through the npm ecosystem. Developers can use this tool to publish, install, version, and link skills using existing workflows like package.json and semver.
To use the server, you need Node.js 22.20.0 or later and npm. You can run commands via npx or install the CLI globally. While installing and syncing skills only requires npm, publishing a new skill requires the official Python skills-ref validator to be present on your PATH. The tool works locally within your workspace, scanning node_modules for packages containing a SKILL.md file and using the skills package to wire them into agent directories.
This approach allows for reproducible installs using package-lock.json and supports npm workspace monorepos. It is designed for developers who want to share reusable instructions, scripts, and resources with AI agents following the open Agent Skills standard.
What you can do with it
- 1Scaffold a new skillCreate a new package structure for an agent skill using the initialization command.
- 2Publish skills to npmUpload your agent skill packages to the npm registry so others can install them.
- 3Install and link capabilitiesDownload a skill and automatically wire it into the appropriate agent directories.
- 4Synchronize local skill changesUpdate the links in agent directories after making local edits or updating dependencies.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablesbroenne/skillpm is public and reachablegithub.com/sbroenne/skillpm ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/sbroenne/skillpm ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubskillpm — npm-native package manager for Agent Skills
The Agent Skills spec defines what a skill is, but not how to publish, install, version, or share it through npm. skillpm fills that gap.
skillpm keeps Agent Skills inside the normal npm model: package.json, node_modules, lockfiles, semver, and the npm registry.
For full project-wide agent configuration, use APM.
Quick start
Requires Node.js 22.20.0 or later and npm. Publishing also requires the
official Python skills-ref validator
on PATH; installing and syncing skills do not require Python.
# Install a skill (no global install needed)
npx skillpm install <skill-name>
# List installed skills
npx skillpm list
# Scaffold a new skill package
npx skillpm init
Or install the CLI globally:
npm install -g skillpm
Note: Skills are always workspace-local. This installs the
skillpmCLI — not skills.
How it works
When you run skillpm install <skill>:
- npm install — npm handles resolution, download, lockfile, and
node_modules/ - Scan — skillpm scans
node_modules/, including nested dependencies, for packages containingskills/*/SKILL.md - Link — for each skill found, skillpm calls
skillsto wire it into supported agent directories
That is the whole scope: package, install, publish, and link reusable skills.
The linking integration uses skills@1.7.0, verified against the upstream
release.
It normally copies skill content into .agents/skills/ and links agent-specific
directories to that canonical copy. These are not live links to node_modules:
run skillpm sync after npm update, npm ci, or local skill edits.
Agent discovery and installation paths remain the responsibility of skills;
skillpm does not install to every agent with --all.
package-lock.json remains authoritative for npm package versions. Any
skills-lock.json written by the upstream CLI describes agent installations,
not npm dependency resolution. Use npm to update npm-distributed skills, then
sync; do not substitute skills update for npm updates.
Linking failures now cause a nonzero exit. Packages with colliding SKILL.md
names are rejected before linking so nested versions cannot overwrite each other.
What skillpm adds
| The spec doesn't define... | skillpm adds... |
|---|---|
| A registry | Publish to npmjs.org with skillpm publish |
| An install command | skillpm install resolves the skill dependency tree |
| Dependency management | Standard package.json dependencies — npm handles semver, lockfiles, audit |
| Versioning | npm semver, package-lock.json, reproducible installs |
| Agent wiring | Links installed skills into agent directories via skills |
Commands
| Command | Description |
|---|---|
skillpm install [skill...] |
Install skill(s) + dependency tree, then wire them into agent dirs |
skillpm uninstall <skill...> |
Remove skill(s) |
skillpm list [--json] |
List installed skill packages |
skillpm init |
Scaffold a new skill package |
skillpm publish |
Publish to npmjs.org (validates the Agent Skills spec) |
skillpm sync |
Re-wire agent directories without reinstalling |
skillpm <npm-command> [args] |
Any other command is passed through to npm |
Aliases: i/add for install, rm/remove for uninstall, ls for list.
Monorepo / npm workspace support
If your repo is an npm workspace monorepo where each skill is a first-party package, npm installs them as symlinks inside node_modules/.
node_modules/
@org/
my-skill → ../../skills/my-skill
skillpm sync (and skillpm install) detects these symlinks and treats them as workspace packages, so contributors can regenerate linked skills after editing local packages.
Creating a skill
mkdir my-skill && cd my-skill
skillpm init
See the full Creating Skills guide for package structure, SKILL.md format, dependencies, and publishing.
What are Agent Skills?
Agent Skills are modular, reusable packages of instructions, scripts, and resources that AI agents can dynamically load to extend their capabilities. They follow an open standard adopted by Claude, Codex, Cursor, Gemini CLI, Augment, and others.
The portable format is a directory containing SKILL.md. The skills/<name>/
layout, npm keyword, and one-skill-per-package rule are skillpm conventions,
not requirements imposed by the open standard. Host-specific frontmatter and
tool permissions are not universally portable; see the specification.
For Git repositories, direct-download URLs, global installation, and other
non-npm sources, use the upstream skills CLI
or the host's own tooling. These are not new package sources for skillpm.
Where APM fits
- Use
skillpmfor reusable npm-distributed skills. - Use APM for full project agent configuration.
Development
npm install
npm run build
npm test
npm run lint
License
MIT
skillpm MCP questions
What does skillpm do that the Agent Skills spec does not?
While the spec defines what a skill is, skillpm provides the registry, installation commands, dependency management, versioning, and agent wiring.
Do I need Python to install or sync skills?
No, installing and syncing skills does not require Python, though publishing requires the official Python skills-ref validator on your PATH.
How do I update skills after running npm update?
You should use npm to update the skills and then run skillpm sync to re-wire the agent directories.
What are Agent Skills?
They are modular, reusable packages of instructions, scripts, and resources that AI agents load to extend their capabilities.