Start with a job you do well and often.
A skill for a job you are bad at teaches the AI to be bad at it. Pick something you do well, do often, and could explain to a new hire in ten minutes. Writing the follow-up text after a customer conversation. Screening an applicant. Turning a meeting into three action items.
- You do it at least weekly.
- You could explain it to someone new in ten minutes.
- You can name what a bad version looks like.
Five parts, under 250 words.
Write the steps the way you would say them out loud to a new hire, in order. Write the rules from your mistakes: every rule is something that went wrong once. Put one real example at the bottom. The example teaches more than the steps.
Run it three times before you trust it.
- An easy case.
Clean inputs, obvious answer. It should be right the first time.
- A messy case.
Missing information, a contradiction, an edge. The skill should ask, not guess.
- A case where the right answer is no.
Where the job should not be done at all. The skill should say so.
If it fails a test, fix the skill file, not the prompt. Then run all three again.
Why most skills fail.
- Too long.
A skill over a page gets skimmed by the AI the same way a long handbook gets skimmed by a person. Cut it.
- No rules.
Steps without rules produce confident, wrong output. The rules are where your judgment lives.
- No example.
One real example of the job done right is worth ten sentences describing it.
Your skill has fourteen steps and no rules. Cut it to six steps, add the three things that have gone wrong before, and paste in one good example.
Fill in the five parts.
Write it the way you would say it to a new hire. Entries stay on this page and are not sent anywhere.
Let the AI write it from watching you.
Do the job once in the chat, out loud, then run this.
I just did a job in this conversation the way I always do it. Write a skill file from what you observed. 1. Purpose in one sentence. 2. Inputs: what I provided, and what you should ask for if it is missing next time. 3. Steps: the order I actually worked in, numbered, no adjectives. 4. Rules: anything I corrected, avoided, or refused to do. Write each as never or always. 5. Format: what my final output looked like, with a word limit. 6. Example: the output from this conversation, cleaned of any private details. Keep the whole file under 250 words. Mark anything you inferred rather than saw with [confirm].
One prompt. Paste it into Claude. It builds the whole thing for your business.
The Pro pack is a build prompt with blanks for your context: your product, your medium, your team. Fill them in, answer its questions, and it produces the complete system in your words. The PDF explains the method so you can judge the output. The anatomy of a skill that holds up, five fully written operator skills, the testing rubric, versioning rules, and two prompts to draft and stress-test your own.
- The build prompt: paste it into Claude, fill in the blanks, and it builds the whole system for your business
- The seven-part anatomy of a skill: name, trigger, input, output, steps, guardrails, examples
- Five complete skills: interview scorecard, weekly numbers, onboarding checklist builder, incident write-up, pricing page audit
- The testing rubric and the three-input rule
- Versioning: how to change a skill without breaking what depends on it
- Two prompts: skill drafter, skill red-team
Delivered as a zip: the build prompt as a text file, the PDF, and every prompt and template as plain text. One payment, yours to keep.