skill-builder

---

name: skill-builder description: Used when the user wants to create a new Skill, or when an EVOLUTION.md proposal auto-generates a new Skill. Creates a structurally consistent new Skill following the framework's modular conventions. version: 1.0.0 updated: 2026-05-26 requires: []

[Task] Create a new Skill that conforms to framework conventions based on the user's described needs or an EVOLUTION.md fourth-layer proposal. Ensure the new Skill shares the same structure, unified style, and plug-and-play modularity as existing Skills.

[Not For] - Modifying existing Skills -> edit the SKILL.md directly instead - Evolving rules from feedback patterns -> use /evolution-engine instead - Recording feedback about a Skill -> use /feedback-writer instead

[Dependency Check] Required: None (this Skill does not depend on external files)

Optional:
- Related records in ../../feedback/ -> if from an EVOLUTION.md proposal, read the original feedback to understand the need's background

[First Principles] → references/first-principles.md 核心：Template First / Reference Existing / Minimum Necessary / Web-First。

[Output Style] → references/output-style.md Tone: Architect explaining a blueprint — structured, precise, prescriptive.

[File Structure] skill-builder/ ├── SKILL.md # Main Skill definition (this file) ├── templates/ │ └── skill-template.md # Skeleton template for new Skills └── references/ ├── first-principles.md ├── output-style.md ├── workflow.md ├── dimension-checklist.md └── anti-rationalization.md

[Dimension Checklist] See references/dimension-checklist.md for the full dimension checklist.

Must-have dimensions:
- **Decidable Triggers**: description specifies when to use AND when not
- **Workflow Executability**: each step specifies concrete action
- **Gotchas from Practice**: ≥3 specific failure points with guidance
- **Boundary Clarity**: [Not For] section with explicit exclusions
- **Dependency Check**: required deps have failure guidance

[Anti-Rationalization Checklist] → references/anti-rationalization.md 遇 skipping template / skipping reference / TBD placeholders 时读取。

[Gotchas] Skipping template: "I know the structure well enough" — read the template anyway. Every time you skip, you'll miss something: a section heading, a required field, or the consistent format. Not cross-referencing existing Skills: Writing in a different style from the rest of the codebase. Always read 1-2 existing Skills before creating a new one. Consistency matters for maintainability. Empty sections: "To be filled later" is technical debt. If a section isn't needed, don't include it. If it IS needed, fill it now. Empty sections in a Skill cause confusion when the Skill is invoked. Missing Gotchas: You're building a Skill that WILL accumulate failure points. If you don't leave a [Gotchas] section, where will those lessons go? Nowhere — they'll be repeated. Skipping Skill eval: Shipping without triggers.json / cases.json — you won't know if description misfires or outputs regress. Run pnpm skill-eval after every meaningful SKILL.md change.

[Quality Rubric] 16-item, 32-point scoring system. Ship threshold: ≥ 24 with no critical item scoring 0.