skill-fylisted

# skill-fy A skill encodes ideas and patterns, sometimes prescriptions if the user explicitly asked for this. Everything below is a default with an intent behind; You're allowed to deviate only after stating why it would be better than the default. Don't copy an example's shape verbatim into a skill it doesn't fit just to follow. **Two modes:** 1. **Scaffold** and write the first version of a new skill. 2. **Skill-fy** an existing skill: audit it against the doctrine below, trace how an agent reads it, transform it on approval. Both hand off a draft unless asked otherwise. Build it talking with the user, expect the user to hand edit parts, A skill gets good when its owner cuts it down to what they actually mean. # How to use THIS Skill The skill uses progressive disclosure: each mode routes to a `references/` file holding the procedure. Read the matching one **before** planning or acting, not after. SKILL.md alone is not enough. Load the **writing-for-agents** skill tool first when it is installed. It carries the theory this skill relies on. ## Router **Scaffold a new skill, or add a reference page to one** -> [`references/scaffold.md`](references/scaffold.md) Intake, invocation decision, layout, the skeletons, frontmatter, build order (description last), reference-page shapes (commands, inventory, on-failure), the trace before handoff. **Skill-fy an existing skill** (audit + transform) -> [`references/skill-fy.md`](references/skill-fy.md) Inventory, the trace (one