What's actually in the SKILL.md
A skill is only as good as its instructions, so we simply describe them here. That file opens with a frontmatter that determines when Claude picks up the skill: for theory questions like SCQA and Minto, for practical questions like delivering bad news, building support, a proposal to management and getting urgency across, and for the frustrations from DOC.01. It also states explicitly what it's not for: SEO blog articles built on search intent, ad copy where the hook matters more than the lead-in, and narrative texts where the tension needs to build instead.
Then comes the theory: the four parts with their definitions, the link to the Pyramid Principle with the MECE rule, the four order variants that Minto herself describes, and the shortened SCR form for short messages.
Then the method: seven steps the skill always takes. It first establishes who the reader is, what they already know and what they need to do after reading. It fills in the four parts separately and shows them on their own, before any running text appears. It tests the situation for agreement and the complication for authenticity. It spells out the question literally and uses it as a filter for everything that follows. It builds two to four arguments under the answer following the pyramid and tests them for MECE. And it writes the whole thing out in the requested format, with an alternative order included if the situation calls for it.
Before anything is written, the skill runs through a mandatory seven-point checklist: your message or raw notes, the reader and what they already know, what you want from the reader, what has changed or gone wrong, the format and the length, the relationship between you and the reader, and what argues against your proposal. It only asks about what's missing, in a single round, and then continues with a marked assumption. So you don't get a form, at most a few targeted questions.
The output always has the same seven blocks, in the same order: reader and goal, SCQA at a glance, the test on the four parts, the pyramid under the answer, the written-out piece, an alternative order, and a closing block with what isn't backed up and which objection is still open. That last block is typical of the file: the skill names the weak spots in its own piece before your reader does. In the example from FIG.01, that's the missing argument for two days instead of one, and the unanswered objection that pitches have also been won online.
A striking number of rules are about language: clear, direct British English, no dashes in running text, short sentences alternated with long ones, concrete over abstract, figures over adjectives, and a ban list of hollow phrasing. There is also a separate six-step review mode for existing work, more on that in the FAQ. At the bottom are three source references, all traceable to Barbara Minto and the consulting practice at McKinsey. If you want to learn to write an instruction file like this yourself: the structure is exactly what we explain in writing SKILL.md files NL.