What is actually in the SKILL.md
A skill is only as good as its instructions, so we simply describe them here. The zip is 4.5 KB and contains one folder, ai-cynefin-decision-maker, with one file inside it: SKILL.md, 1,446 words, version 1.0.0, MIT licence. No scripts, no integrations, no assets. It is a text file that tells Claude how to think about an issue.
The file opens with a frontmatter that states when the skill should trigger. Not only on the word cynefin or the name Snowden, but also on ordinary sentences: which approach fits here, how should I approach this, is this complex or just complicated, what type of problem is this. The frontmatter also explicitly names chaotic crisis situations, transformation projects and innovation questions, plus the situation where someone gets stuck by applying the wrong approach to the wrong type of problem. Say something like that to Claude while the skill is loaded, and it triggers automatically.
After that comes the role description: senior strategist trained in Dave Snowden's cynefin framework, with Cognitive Edge, IBM Research and the Cynefin Centre named as its origin. Then follows the theoretical basis with the five domains, each with the status of cause and effect, the matching decision method and an example.
The working method has five steps, each with its own heading in the file. Step 1 is clarifying the problem: with vague input the skill asks at most three clarifying questions, otherwise it moves straight on. Step 2 is determining the domain using five diagnostic questions, with the note that a problem can have parts in different domains and that you then have to split it up.
Step 3 is the domain specific approach, and that is the table you see in FIG.02 above: a decision method, a decider, tools and the typical risk for each domain. Step 4 is three to five concrete next steps that fit the domain. Step 5 is the boundary warning: where this can tip over, and the two movements the file names specifically are a Complex problem potentially deteriorating towards Chaotic, and a working Complicated solution that migrates towards Clear over time.
The output is fixed in five blocks: classification with domain and two sentences of diagnosis, fitting approach with decision method, decider and tools, concrete steps, domain pitfalls, and boundary warning. Below that are two fully worked examples, culture change and a data breach, both with the complete output attached. Then follows the list of five things the skill does not do, and finally the source list with five titles.
What is not in it is just as relevant. There is no prioritisation method, no calculation model, no project plan template and no implementation advice. You get a classification and a working method, nothing more. What you do after that is your own work, and if you are looking for structure there, the MECE Problem Structure Coach is the logical next step, because it does the splitting step 2 asks for neatly and without overlap.