Numbered steps, one to three sentences each. Built so a new hire could follow them.
Output standard is locked, knowledge files exist. Now you write the playbook: what Claude does, in what order, with what.
Numbered steps. Each step one to three sentences. Each step answers three questions:
Write the way you would explain it to a new hire on day three. Plain language, real verbs, no abstractions. "Read the knowledge file, pick three patterns, use them in the outline" beats any clever prompt-engineering line.
"Be creative", "make it compelling", "use your judgment". Claude cannot act on these. Replace with: "Pick three of five options from the list", "Keep it under 120 words", "Pattern after example_2.md".
Always give criteria. Not: "Choose the best framework." But: "Choose the framework where the prospect's main pain matches the first column. If two match, take the one with the shorter explanation."
Continue with skill-creator. Step 4: write instructions. Use the knowledge files. Build SKILL.md with: - proper frontmatter (name, description) - numbered steps, 1–3 sentences each - each step answers: what, with what input, what output - vague verbs replaced with concrete criteria - decisions include selection criteria Save it next to the knowledge files.
If you cannot hand it to a new hire and have them produce the right output by following it, the skill is not ready yet. Tighten the steps until they could.