The five skills
Each block below is a complete skill file. Copy one, save it as a reusable Claude skill, and build the job you repeat most first. Installing it takes about five minutes and there are two ways to do it — both in the next section.
The description line is what makes it fire. Claude only holds each skill's name and description in mind until something matches — that is why you can have dozens installed without slowing anything down. It also means a vague description is a skill that never triggers. Every one below says what it does and when to use it, on purpose. (Anthropic's Agent Skills docs, checked 09/09/2026.)
CLIENT CALLS
Build this firstTranscript in. Decisions, tasks, owners and a follow-up email out.
--- name: client-calls description: Turn a client call transcript into decisions, tasks with owners, and a follow-up email. Use whenever I paste a call transcript or notes from a meeting. --- # Client calls When I give you a transcript: 1. Decisions. What was actually settled. Only things that were decided, not things that were discussed. 2. Tasks. One line each, with an owner (me or the client) and a due date if one was said out loud. 3. Open questions. Anything left hanging that has to be answered before work can start. 4. Follow-up email. Short and warm, written to the client. Lead with what we decided, then their tasks, then mine. No preamble, no recap of the small talk. If an owner or a date was never said, write "not stated". Do not guess one.
What it does. Turns a forty-five minute call into the four things you actually needed from it, and writes the follow-up while the call is still fresh. The "not stated" rule is doing quiet work — without it you get invented deadlines that feel authoritative enough to end up in your calendar.
What it does not do. It cannot fetch the transcript. You still paste it in, or connect a recorder yourself. And it only knows what was said out loud — the thing you agreed to in your head on the call is not in the file, so it will not appear in the tasks.
CONTENT ENGINE
For content weeksOne long video into five angles, five Reel scripts and a filming list.
--- name: content-engine description: Turn one long video transcript into five short-form angles, Reel scripts and a filming list. Use when I paste a long transcript or a long-form script. --- # Content engine From one long transcript, give me: 1. Five angles. Five different arguments that are genuinely in this video. Five whole ideas, not five ways of phrasing the same one. 2. A Reel script per angle. Hook in the first line, then the point, then one specific example from the transcript. Spoken language, no headings, under 45 seconds read aloud. 3. A filming list. What I actually have to get on camera, grouped so I can shoot the lot in one sitting. Use my own words from the transcript wherever they are better than yours. Do not invent examples I did not give you.
What it does. Gets five distinct pieces out of something you already recorded, then tells you what to film in one batch instead of five separate setups. The "do not invent examples" line is the difference between your stories and generic ones with your name on them.
What it does not do. It will not tell you which angle will perform — it has no idea what your audience responds to. And five is a target, not a promise: a thin transcript gives you two strong angles and three stretches. Cut the stretches rather than filming them.
BRAND BRAIN
The one that fixes voiceReads your voice guide and quotes real examples before it writes a word.
--- name: brand-brain description: Read my voice guide and quote real examples from it before writing anything as me. Use whenever I ask for copy, captions, emails or posts written in my voice. --- # Brand brain Before you write a single line as me: 1. Read my voice guide and my sample posts. 2. Quote three real lines from the samples that match the job in front of you, and say in one sentence why each one works. 3. Then write, matching the rhythm of those three lines. Rules: - Australian English. - Short punchy sentences, then a longer one for breath. Never three tidy items in a row. - If you cannot find a real example that matches this job, say so and ask me for one. Do not guess at the voice.
What it does. The quoting step is the whole trick. Made to find and quote three real lines first, it has to actually read your writing instead of generating its idea of "your voice" from your industry. The output changes noticeably, and you can see why it changed.
What it does not do. It has no voice guide unless you give it one. A skill is instructions, not a folder of your writing — so you either paste the samples in, or point it at a file it can read. Skip that and step 2 becomes it quoting itself, which is worse than not having the skill.
MONEY CHECK
MonthlyOrders against payments. Mismatches flagged, subscriptions listed.
--- name: money-check description: Compare an orders export against a payments export, flag mismatches and list active subscriptions. Use when I give you sales and payment data to reconcile. --- # Money check Given an orders list and a payments list: 1. Match them on amount, date and customer. 2. Flag every mismatch. An order with no payment, a payment with no order, or an amount that does not line up. One line each, showing both numbers. 3. List active subscriptions. What recurs, how much, how often, and when it next charges. 4. Tell me what you could not match and why, BEFORE you give me any totals. Never round. Never fill a gap with an estimate. If a field is missing from the data, say the field is missing.
What it does. Catches the order that never got paid and the subscription you forgot you were still on, in a couple of minutes instead of an afternoon of squinting at two spreadsheets. Putting the unmatched items before the totals stops a tidy-looking number hiding a hole.
What it does not do. This is not bookkeeping and it is definitely not tax advice. It is a mismatch finder across two lists you handed it. It knows nothing about refunds, chargebacks, or anything that never made it into the export — so check every flag against the real account before you act on it or chase anyone.
MONDAY CEO
Every MondayReads your calendar, tasks and email, hands back three decisions.
--- name: monday-ceo description: Read my calendar, tasks and inbox and return the three decisions only I can make this week. Use on a Monday, or whenever I ask what actually needs me. --- # Monday CEO Read my calendar for the week ahead, my task list and my unread email. Then give me: 1. Three decisions only I can make. Not tasks. Decisions, where someone is waiting on my answer and nobody else can give it. 2. What is genuinely time-sensitive this week, with the date it stops being possible. 3. What I should hand off or delete, and who to. Three decisions maximum. If there are more than three, pick the three with the biggest consequences and tell me what you left out.
What it does. Separates the three things that actually need you from the pile that only feels like it does. The hard cap is the useful part — a list of eleven priorities is not a list of priorities, and it will happily give you eleven if you let it.
What it does not do. It cannot see your calendar or your inbox on its own. You have to connect them — a connector on claude.ai, or a tool in Claude Code — or paste the week in by hand. Without that it will produce three confident, entirely fictional decisions, which is the worst possible version of this skill.
Why they are this short
A skill is not a mega-prompt. It is the note you would leave a competent new team member about how this particular job gets done here — the steps, the house rules, the thing that always goes wrong. Anything longer stops being read properly, by them and by Claude.
How to install one
Two surfaces, two routes. Pick the one you already use — there is no wrong answer and you can do the other one later.
In Claude Code: paste it and ask it to save the skill
Copy the block, paste it in, and say "save this as a skill". Claude Code writes the file into your skills folder itself and already knows where that lives on your machine — Mac, Windows or Linux, you do not need to find the folder or type a single path.
On claude.ai: upload it as a zip in Settings
Custom skills are uploaded as a zip file under Settings, in Features. Easiest route: paste the block into a chat, ask Claude to package it as a skill zip, download what it hands back, then upload that. It is a Pro, Max, Team or Enterprise feature and needs file creation switched on.
Test it with a real job, not a test job
Do not ask "are you using the skill?". Give it an actual transcript, an actual export, an actual week. You are checking whether the description matched your normal way of asking — and if it did not fire, that is the fix: rewrite the description to sound like how you actually ask.
Edit it after the first real run
The first version is always slightly wrong, because you only find the missing house rule when you see the output. Add the rule, save, move on. These take about ten minutes each and roughly three of those are this step.
They do not sync between the two
A skill you upload to claude.ai is not available in Claude Code, and one you save in Claude Code is not available on claude.ai. Anthropic's docs say it plainly: custom skills do not sync across surfaces. If you work in both, install it in both — it is the same file, so it is a copy-paste, not a rebuild. (Checked 09/09/2026.)
Which one to build first
Build one today, not five. The one you would have done by hand this week anyway — that is the one that proves the whole idea, and the other four take ten minutes each once you have seen it work. Find your week below.
"I am on calls all week and the notes never get written"
CLIENT CALLSThe follow-up email is the bit that costs you clients — not because you never send it, but because you send it Thursday and it has lost its edges. This one has the highest ratio of relief to effort of the five, which is why it is first.
"I film plenty and post almost none of it"
CONTENT ENGINEYou have hours of good material and no time to sit and pull it apart. Run one existing video through and you get next week's filming list off something you already recorded. Batch what it hands you.
"Everything it writes sounds like everyone else"
BRAND BRAINBuild this one before any of the writing ones and every piece of copy after it gets better. Worth doing properly — feed it your best twenty posts, not three you found quickly, because it can only quote what you gave it.
"I have no idea what is actually coming out of my account"
MONEY CHECKOnce a month, not once a week. Most people find the unpaid order on the first run and a subscription they thought they cancelled on the second. Check anything it flags against the real account before you chase it.
"I finish the week busy and cannot say what I decided"
MONDAY CEOBuild this one last, because it needs your calendar and inbox connected to be worth anything. Once they are, it is the one you will run most — nine minutes on a Monday and you know the three things that genuinely need you.
What a skill will not do
Being straight with you about the edges, because half the disappointment with skills comes from expecting the wrong thing from them.
A skill is instructions, not access
This is the one that catches people. MONDAY CEO cannot read your calendar, MONEY CHECK cannot open your Stripe account, and CLIENT CALLS cannot go and find the transcript. The file tells Claude how to do the job once it has the data — connecting the data is a separate step, and until you do it you will get a beautifully structured answer made entirely of guesses. Connect first, then judge the skill.
A few other honest limits:
- It makes Claude consistent, not smarter. The gain is that the job comes out the same way every time, including the bits you always forget to ask for. It is not a better model. It is the same model with your standards written down.
- A vague description is a skill that never fires. Claude matches your request against the description, so it has to say what the job is and when to use it. "Helps with content" will sit there forever. Every description above is written the long way for that reason.
- Only install skills you wrote or trust. Anthropic's own guidance is to treat a skill like installing software — it can tell Claude to run code and use your tools. Read anything you download from a stranger before you install it. (Checked 09/09/2026.)
- The first version will be slightly wrong. Every one of the five above is on its third or fourth edit. Ship it, use it on something real, then add the rule you did not know you needed.
Where these came from
These are five stripped-back versions of skills I run every week, not five invented for a carousel. MONEY CHECK is the one I built most reluctantly and the one that has paid for itself most obviously — the first run found an invoice from February that had never been paid.
Ready to go deeper?
Prompts clear a bad day. Systems stop the bad day turning up every week.
Wright Mode Membership
Join a community of women using AI to take real work off their plate. Live calls, copy-paste prompts and workflows, and ongoing support.
Claude Masterclass
Learn to use Claude like a pro — from prompting fundamentals to building real workflows that save hours every week.
Claude Code Masterclass
Go beyond the chat box. Build automations, process data and create tools with Claude Code — no developer experience needed.