What is actually in the SKILL.md
A skill is only as good as its instructions, so we simply describe them here. The file opens with a frontmatter that states when Claude should pick up the skill. Not just the obvious terms like 5 whys, five whys, root cause, RCA, root cause analysis, problem analysis, fishbone diagram, Ishikawa, kaizen analysis, post mortem, incident analysis and complaint analysis, but also frustrations: we have already fixed this three times and it keeps coming back, we only put out fires, everyone points at each other, the client is complaining about the same thing again, we keep missing our deadline, the fix worked for a week. Anyone who says something like that to Claude while the skill is loaded gets it automatically.
Next comes a chapter on the theory: Toyoda and Ohno, the three layers of technical, process and system, and four variants the skill may use when the context calls for it. The branching chain for when a layer has more than one valid cause. The combination with the Ishikawa diagram for when nobody yet knows where the problem sits. Five whys plus how, where after the root cause you run the chain back upward asking how you guard against each layer. And the lean startup variant from Eric Ries, where per layer you make an investment proportional to how serious the problem is.
At its core is a list of seven things the skill always does. It rewrites the problem into a factual, measurable sentence with place, time and scale before any why gets asked. It asks the five questions one at a time and answers them based on what you have supplied, not on assumption. It marks per layer how certain the answer is. It visibly splits the chain into branches as soon as a layer has more than one valid cause, and follows the branch with the greatest impact through.
It names the root cause in one sentence, phrased as a system or process. It delivers the quick fix and the structural measure separately, each with an owner and a deadline. And it closes with a verification step.
Before anything gets analysed, the skill runs through a mandatory input checklist of six points: the problem in your own words, when it occurs and how often, who or what suffers from it, what has already been tried and why that did not help, which facts or figures are available, and what you can and cannot change about budget, mandate and influence on other departments. It only asks about what is missing and then stops asking. If you do not know something, it carries on and marks that layer as unproven. So you do not get a form, at most two or three targeted questions.
A striking number of rules are about language. Plain British English, addressing the reader directly as you, no dashes in running text, AI written in capitals, no lists of exactly three items, concrete over abstract, a figure over an adjective, and short sentences alternating with long ones. There is even a list of words and turns of phrase that are banned because they smell of AI. And there is a writing rule that is substantive rather than cosmetic: write causes passively where that removes the question of blame. If you want to understand how rules like that end up in a skill file, writing a SKILL.md NL explains the structure step by step.
The output is fixed into seven blocks in a set order: problem statement, the chain of whys, root cause, quick fix, structural measure, verification, and what you still need to find out. The file also contains a separate review mode for existing analyses, a list of seven things the skill never does, and a source list of five titles. The last two get their own section further down this page.