Not just at the obvious terms like make an excel formula, sumifs, vlookup, create a pivot table or google sheets formula, but also at phrases people actually use: my formula gives #N/A, what does #VALUE! mean, it says too few arguments have been entered, excel will not accept my comma, I have a formula from a video but it does not work, it works on the first row but not once I drag it down, I spend half a day on this every month, I am scared to change anything in this file.
Say something like that to Claude while the skill is loaded and it picks it up automatically. The same frontmatter also lists the cases where the skill should specifically not start, and beneath that sits the licence: MIT, version 1.0.0.
Next comes the core: twelve fixed actions. To begin with it asks what the sheet actually looks like, with sheet names, exact column headers and column letters, and the first and last row with data. It asks the version, because that decides which functions may be used. It asks which separator the formula bar uses and which language the function names are shown in. It rephrases the question first into a sentence you can check, and only then does a formula follow.
That formula it delivers twice, English and Dutch, never mixed. It explains it argument by argument, in the order they appear. It explains separately which references are locked and what happens when you drag the formula. It names the pitfalls specific to this particular sheet. It judges whether a PivotTable or Power Query would need less upkeep. It gives a check you run yourself. It runs the self-check. And it lists every assumption separately at the bottom.
Before those actions start, the skill runs through a mandatory input checklist of ten points: sheet name and column headers with column letter, the first and last row or the name of the table, the Excel version or Google Sheets, the separator in the formula bar, the language of the function names on screen, exactly what needs to come out, where the answer goes and whether the formula gets dragged, what sits in the awkward cells, whether amounts include or exclude VAT and whether there are credit lines mixed in, and how often this comes back. That last point looks like a detail but is not: one-off work calls for a formula, work that recurs every month calls for Power Query.
If something is missing, the skill asks for at most three things at once and then carries on with the assumption stated in the answer.
The output has a fixed structure of ten blocks. What I understand about your sheet. The formula in English. The same formula in Dutch. Explanation per part. References and dragging. Pitfalls in this sheet. PivotTable or Power Query. Check in thirty seconds. Self-check. Assumptions. That order is not arbitrary: the formula comes first so you can paste it straight away, and the explanation sits below it for the moment you want to know why it works. The Assumptions block always closes it, so it stays visible what the answer rests on.
The file also contains two fully worked examples with the user's input and the complete output underneath, written out in all ten blocks. The first is revenue per client per quarter at a fictional plumbing and heating firm, including the VAT warning and the note that client names spelled just slightly differently count as separate clients. The second is a VLOOKUP that gives #N/A at a fictional online shop on Excel 2019, where the answer ends up being INDEX with MATCH because XLOOKUP does not exist there. Both companies are invented and labelled as an example, and no amounts appear that could be read as real.
Lastly a block of writing rules, a list of what the skill never does, a list of cases where a PivotTable or Power Query is the better choice, and the sources. Learning to set up this kind of instruction file yourself is also possible, and that process is laid out step by step in writing a SKILL.md NL.