What is actually in the SKILL.md
A skill is only as good as its instructions, so we simply describe them here. The file runs to 3,133 words and consists of ten chapters: the theory, what the skill always does, a mandatory input checklist, the writing rules, the output structure, a worked example, when to use which variant, how to review existing work, what the skill never does, and the sources.
It opens with frontmatter stating when Claude should pick up the skill. Not just for the explicit terms like first principles thinking, first principles, thinking from the ground up, surfacing assumptions, assumption mapping, riskiest assumption and breaking down a cost structure. Also for questions that have nothing to do with a framework: does my business plan hold up, what am I missing, why is this so expensive, can this be fundamentally different.
And for exasperated remarks you would sooner hear in a canteen than in a strategy session: everyone in the industry works this way so we do too, we copied this from a competitor, my investor asks why this works and I do not have a good answer, our price is based on what everyone else charges.
Right below that sits the role description, and it is unusually strict for an AI instruction: the skill confirms nothing out of politeness, hunts for the assumption the whole plan rests on that nobody has checked because everyone in the industry shares it, and never makes up figures, market data or research findings.
The core is a list of eight fixed actions. It rewrites the goal into a measurable sentence with a deadline and strips out the solution if one is already hidden inside it. It strips the plan down and separates laws of nature and mathematical facts from contractual facts and from conventions. It surfaces eight to twelve assumptions, spread across the customer, the market, execution, technology, money and regulation, each as a falsifiable claim. It scores every assumption on probability and impact, from 1 to 5, and records the evidence strength.
After that it gets sharper. It flags the highest-scoring ones as primary risks, usually two to four. For each risk it delivers a redesign step you can carry out this week plus the cheapest test. It rebuilds the plan from what remained and states for each step whether it departs from the original plan and why. And it closes with the risks you consciously accept, so that there is a choice in place of a blind spot.
Before anything happens, the skill runs through a mandatory input checklist of seven points: the plan in your own words, the deadline by which it has to succeed, what is at stake in money, time, reputation or business, where the plan came from, the hard constraints, what you already know for certain and what that is based on, and what has already been tried in this direction. It only asks about what is missing and then stops asking, so you do not get a form, just a handful of targeted questions at most.
The output is fixed into eight blocks in a set order: the goal sharpened, broken down into three lists, the assumptions, the score table, the primary risks, the redesign per risk, the plan rebuilt in five to eight steps, and consciously accepted. The file also contains a worked case study about an online course, six situations where you pick which variant, a review mode with six checks for an existing plan or an existing risk analysis, seven things the skill never does, and six sources. If you want to see how a file like this is technically put together, from frontmatter to refusal list, writing a SKILL.md NL explains that step by step.
A striking number of rules are about language, and they are not all cosmetic. Clear Dutch, addressed as you, no dashes in running text, AI in capitals, no lists of exactly three, concrete over abstract, a figure over an adjective. But the last writing rule is substantive and maybe the most important in the whole file: word every assumption so that it could turn out to be wrong. That one rule decides whether the rest of the analysis is about anything at all.