Skill Cabinet Go
Single static Go binary and MCP server for inspecting, auditing, weeding, and serving agent skills
Why This Was Built
Managing installed agent skills across multiple assistants (.agents, .claude, .codex, .cursor) with Node-based tools is slow to start, requires heavy runtime dependencies, and lacks terminal-native batch weeding and MCP integration.
The Architectural Answer
A high-speed, compiled Go binary and stdio MCP server that scans thousands of skill cards in half a second, safely consolidates duplicates, repairs broken shortcuts, and serves an embedded web desk with zero runtime requirements.
Upstreamed to subsy/skill-cabinet
8x scan speedup (7s → 0.83s), storage reality tracking, and link deduplication (PRs #4–#8 merged)
Key Features & Architecture
Technical Specifications
- Primary Languages
- GoTypeScriptReact
- Frameworks & Tooling
- embednet/http
- Architecture & Execution Model
- Single static binary, UPX compression (3.5MB), embedded React desk, and stdio MCP server
- Licensing Model
- MIT (permissive)
- Release & Lineage
- Active release cycle since 2026 · Maintained by @JadMadi
Frequently Asked Questions
Is Skill Cabinet Go a replacement for subsy/skill-cabinet?
No, it is a high-performance terminal companion and CLI/MCP counterpart to subsy's original Node reference implementation, designed for headless environments, automated scripting, and fast terminal workflows.
Does it require Node.js or external runtime dependencies?
No. It compiles to a single, static binary with the web UI fully embedded via go:embed.
What MCP tools does Skill Cabinet Go expose?
It provides get_cabinet_census, list_skills, get_skill, search_skills, and diagnose_cabinet for any MCP-compatible coding assistant.