SkillMap
Local registry for routing agent skills.
- status
- local
A folder of agent skills stops being a product the moment the library is large enough to be wrong. The questions stop being “do I have a skill for this?” and become: which copy is canonical, where it came from, whether it changed locally, which skills overlap, and why a task routed here instead of there.
SkillMap is a local-first registry for that library. It scans approved skill roots, records identity, surfaces hygiene problems, applies reversible policy without rewriting source files, and routes a prompt with visible reasons. It does not need a cloud account to inventory or route, and it does not execute skill scripts as part of routing.
The useful loop is inventory, doctor, curate, apply, graph, evaluate. Policy lives beside the source tree, not inside it, so a routing decision can change without mutating the original skill. A recommendation should carry enough identity and policy context to inspect.
Access is local. This is a working system, not a hosted catalog. Package publication, OAuth, and public-user acceptance are separate states. Exact test counts stay off this page until they sit next to a current receipt.
What I learned: the interesting problem in agent skills is not generation. It is governance — identity, provenance, overlap, policy, and the right to say a capability is ready.
Related: How I Build, Claims and boundaries.