system-of-skillslisted
Install: claude install-skill X32Studio/best-practice-for-skills-system
# System of Skills — 系统工程方法论
## Why this exists · 为什么存在
Single-skill authoring is a solved problem. This skill handles the layer above: **how a collection of skills and multiple agents form a coherent system.**
Good work means: each skill maps to a unique (user × scenario) pair; triggering is unambiguous for any system state; changing one skill doesn't break another; the whole system can be empirically verified. **Good work does NOT mean:** grouping skills by topic similarity; building a skill because the set "feels incomplete"; or a trigger that needs a paragraph of prose to disambiguate.
## What failure looks like · 失败长什么样
Make the cost concrete before you start — the bill arrives in production, not in a design doc:
- **Trigger conflict** — You ship two skills that both fire on the same user turn. At 02:00 the agent picks the wrong one, emits the wrong handoff artifact, and the planner builds a plan on a misread intent. By morning the system has taken hundreds of actions on a false premise. The post-mortem names whoever let the triggers overlap.
- **Coverage gap** — Friday 17:00, under release pressure, the agent hits a real state no skill owns. It reaches for "probably fine / leave it for the next pass," improvises an answer, and the deploy ships. Monday the regression suite catches it — but the Friday deploy already reached users. Whoever left that matrix cell without an owner signed off on it.
- **Floating skill** — A skill that can't be traced to a Kernel principl