What is really in the SKILL.md
A skill is only as good as its instructions, so we simply describe them here. The file opens with frontmatter: a name, version 1.0.0, the MIT licence and a long description that determines when Claude picks up the skill. That description is remarkably broad. Alongside the obvious triggers PESTEL, PESTLE, macro analysis, environmental analysis, external analysis and market analysis, it also contains ordinary sentences that people really say: what is happening in the market, should I enter this market, what is changing in the world for my business, what are the external risks. STEEP and DESTEP are in there too.
And it also contains situations rather than words: internationalisation plans, a market entry, a product launch in a new region, a five year plan, preparing for a board meeting, an investment decision, due diligence for an acquisition, building the case for a business case, and a strategic reorientation.
After that comes the philosophy, and it is short and concrete. Francis Aguilar published Scanning the Business Environment from Harvard Business School in 1967 and introduced the ETPS framework in it: economic, technical, political, social. Only in the 1980s did Gerry Johnson and Kevan Scholes expand that in Exploring Corporate Strategy into PESTEL, adding the ecological and legal dimensions, because environmental and legal factors were increasingly tipping the scales in strategic choices. The core of the model is summed up in the file in one sentence: strategy is never made in a vacuum.
The heart of the file is the four step method. Step one is the scope: the skill keeps asking until it knows four things, namely the subject, the geographic scope, the time horizon and the purpose of the analysis. If it does not get a clear answer to that, it makes reasonable assumptions and states them explicitly in the output.
Step two is the scan itself: the six dimensions in the fixed order P, E, S, T, E, L, each with its own list of angles to consider. Political has seven, the five other dimensions have eight each, so 47 checkpoints together. They are concrete: for legal it names by name GDPR, the DSA, the AI Act, MiCA and NIS2, plus employment law, competition law, product liability, intellectual property, tax rules, consumer protection and legislation that is still on its way.
Step three is the weighting. A minimum of three and a maximum of seven factors per dimension, and five fields per factor: the factor stated briefly and factually, the impact as positive, negative or neutral, the probability as high, medium or low, the time horizon as now, one to two years or three to five years, and a short rationale for why that factor matters for this subject. Step four is the synthesis: the top three opportunities in order of impact times probability, the top three threats in the same order, three to five strategic recommendations and finally the section What you do not know, with the assumptions, the data gaps and the signals you still need to validate yourself.
After that comes a fully written out output template with all the headings and fields, so the layout does not shift between two analyses, and the fictional padel-hall example in Tilburg, with all premises explicitly marked as unverified assumptions. The file closes with six tone rules and five refusals. The tone rules: write in a business like and factual way, use concrete figures and sources or otherwise label something as an assumption, do not gloss over unwelcome conclusions, avoid jargon or explain it briefly, no emoji, and do not put everything into bullet points. If you want to learn to write an instruction file like this yourself, the method is set out in writing a SKILL.md NL.