skill-splitterlisted

# skill-splitter — SKILL.md Governance-Semantic Split > A SKILL.md that does everything in one file is not simple — it is unscoped. > The goal is two files each smaller than the original, not one file and its appendix. ## Trigger Phrases | Phrase | Situation | |---|---| | "this skill is getting too long", "trim the skill", "split this SKILL.md" | Direct split request | | "context-doctor flagged this skill", "SKILL.md is bloated" | Post-diagnosis split | | "I can't see the key parts", "too much detail in the skill file" | Readability problem | | "separate the bash from the logic", "move the templates out" | Structural refactor request | | `/skill-splitter` | Explicit invocation | --- ## Core Principle — Governance-Semantic Criterion **The split criterion is NOT length. It is: when does this content need to be in memory?** | Layer | When needed | Examples | |---|---|---| | **SKILL.md (always-loaded)** | Every invocation — session boundaries, trigger recognition, step overview, decision tables | Triggers, principles, step names + criteria, key decision tables, Done When | | **SKILL_detail.md (on-demand)** | Only when executing a specific step | Bash scripts, format templates, edge cases, step-by-step execution detail | **Behavioral rules stay in SKILL.md** — if a rule governs *what counts* (e.g. "these patterns = closed"), it is behavioral logic and must be always-loaded regardless of length. **One test**: *"If a consumer agent had only SKILL.md, could they recognize th