Manage groups of related skills like the dependencies they are.
Resolved, versioned, and installed flat into .claude/skills/
with one command.
$ 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/run-tracker-app@1.0.0├── @acme/jetpack-compose-ui@1.0.0│ └── @acme/android-app-foundation@1.0.0│ └── @acme/kotlin-style@1.0.0├── @acme/room-persistence@1.0.0│ └── @acme/android-app-foundation@1.0.0 (deduped)└── @acme/running-metrics@1.0.0// why skillgraph
Everything you expect from a modern registry — resolution, versioning, search, reproducibility — purpose-built for the way agents consume skills.
Every skill is a plain SKILL.md folder per the agentskills.io standard — skillgraph adds the dependency graph on top. Skills depend on skills; it resolves the full transitive closure, detects cycles and dangling edges, and installs leaves-first, the npm model for agents, without ever rewriting your content.
Skills are addressed by @scope/name coordinates and versions never change. Author and wire them together with no registry — your local skills carry an @local scope the server stamps to @you when you publish. Your scope comes from your identity server-side, so you can only ever publish as yourself.
The registry indexes the description from each skill’s frontmatter, so you find skills by what they do — not just what they’re called.
// the CLI
Consume skills and publish your own from one scriptable, non-interactive surface that runs clean for humans and agents alike.
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 search <kw> find skills by name or description skg init <dir> bring a SKILL.md under management skg publish <dir> publish a graph of managed skills skg fork @scope/name fork another author’s skill under your @scope // 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/pdf-tools@1.0.0