scaffold-skilllisted

# scaffold-skill A skill encodes ideas and patterns, not specific prescriptions. Everything below is a default with an intent behind it; deviate when you can state what following it would cost the skill at hand. Don't copy an example's shape verbatim into a skill it doesn't fit just to follow. ## Scaffolding This skill scaffolds and writes the first version of a skill. It does not ship the final one. Build it talking with the user: the calls that shape the skill (what it encodes, who fires it, how it splits) are theirs, ask instead of assuming. And expect and ask the user to come back and trim. A skill gets good when its owner cuts it down to what they actually mean, so hand off the draft with a note on what you'd cut first. ## Doctrine ### Encode the delta, not the manual Rely on the model's world knowledge. A skill carries the practices, gotchas, and conventions the model wouldn't apply on its own, usually from user's experience and observed gotchas. Enumerating a tool's features duplicates pretraining and rots as the tool moves. ### Examples, and overfitting A lot of skill guidance, especially early ones focused too much on mentioning examples. Model world knowledge is usually underestimated: an example of something in pretraining (how to commit, how to open a PR) teaches nothing, and anchors the agent to one instance; the skill overfits to today's case and rots. It's a delicate balance. An example is good when: - **Output must be consistent across runs.** The sk