Real dependency resolution
Skills depend on skills. skillgraph resolves the full transitive closure, detects cycles and dangling edges, and installs leaves-first — the npm model, for agents.
Manage groups of related skills like the dependencies they are —
resolved, versioned, and installed flat into .claude/skills/
with one command. No account needed to install; sign in only to publish.
$ skg search tracker@acme/run-tracker-app 1.0.0 Step-count run tracker — ties the graph together$ skg install @acme/run-tracker-appinstalled @acme/run-tracker-app (7 skills) into .claude/skills/$ skg ls@acme/[email protected]├── @acme/[email protected]│ └── @acme/[email protected]│ └── @acme/[email protected]├── @acme/[email protected]│ └── @acme/[email protected] (deduped)└── @acme/[email protected] // why skillgraph
Everything you expect from a modern registry — resolution, versioning, search, reproducibility — purpose-built for the way agents consume skills.
Skills depend on skills. skillgraph resolves the full transitive closure, detects cycles and dangling edges, and installs leaves-first — the npm model, for agents.
Every skill is a plain SKILL.md folder per the agentskills.io standard. skillgraph is strictly additive — it never rewrites your content or nests folders.
Skills are addressed by @scope/name coordinates. Your scope is stamped from your identity server-side — you can only ever publish as yourself. Versions never change.
The registry indexes the description from each skill’s frontmatter, so you find skills by what they do — not just what they’re called.
Skills land flat in .claude/skills/. Hand-written or private skills already there are left untouched — install only ever manages what it installed.
A manifest of intent and a lockfile of the resolved graph live at your project root. Commit them and anyone rebuilds the exact same skills — like npm ci.
// the CLI
Search and install with no account at all — sign in only when you want to publish your own. A scriptable, non-interactive surface that runs clean for humans and agents alike.
skg search <kw> find skills by name or description skg install @scope/name resolve the closure into .claude/skills/ skg ls print the installed dependency tree skg ls @scope/name inspect a coordinate before installing skg init <dir> bring a SKILL.md under management skg publish <dir> publish a graph of managed skills skg whoami show the @scope you publish under skg login sign in with GitHub, store an API key skg logout remove the stored key // get started
Install, and you’re installing skills in seconds — no setup. Log in to publish your own. Works for humans at a terminal and agents in a loop.
# install the CLI$ npm i -g skillgraph# find & install a skill — zero config$ skg install @acme/pdf-tools# sign in with GitHub & publish your own$ skg login$ skg publish ./skillspublished @you/[email protected]