Claude Skills for Beginners

Introduction. The Two-Hour Problem

Overview

Every week contains hours that disappear into repeating tasks nobody pays for, and the obvious fixes only rearrange the week. The problem is not spotting those hours; it is that reclaiming them appears to demand technical skill, spare time, or trust you do not have.

Somewhere in the week sits a block of hours that no one has claimed: Sunday night, the hour after closing, messages answered from bed, Friday lost to invoices. The routine answering, confirmations, follow-ups, formatting and summaries repeat forever. Those hours are recoverable, even for a busy, non-technical owner.

The claim is simple and you can test it: if you can draft instructions for a new hire, you can teach AI to handle repeating tasks this week, matching your tone and rules. Training takes about twenty minutes per task, and the approach fits on an index card. By the end of Chapter 2, you will have done it once on real work. AI will not run the business or replace judgment.

The Method

It is for work containing anything done more than twice, and doesn't require technical skills. Chapters 1 to 3 teach Skill-building and the five questions. Chapters 4 and 5 cover task choice and documents. Chapters 6 to 8 cover fixing, chaining and safety. Chapter 9 covers paid work. Chapter 10 holds fifteen templates.

Tools change. The method rests on five parts of any delegation: the job, the facts, the rules, the voice, and the boundaries. That holds up because it is a fact about delegation, not about software. People have trained employees with written instructions for as long as work has existed. Maria runs a cleaning company in Manchester, and her Sunday nights once looked familiar.

Key Takeaways

• Inventory the week for the hours nobody has claimed, the late-night replies and after-close admin, and treat them as recoverable rather than fixed.
• Choose one task you performed more than twice and write the instructions you would hand a new hire; that draft is the raw material, and it doesn't require technical skills.
• Budget roughly twenty minutes for the first attempt and aim to finish a single real task, not to build a system.
• Reduce the instructions to job, facts, rules, voice and boundaries on an index card, so a change of software costs you nothing.
• Review the result as you would a junior colleague's work: it absorbs the routine, but decisions and judgment stay with you.

Chapter 1. Meet Your New Employee

Overview

Every week brings the same tasks back, and every attempt to hand them off starts with explaining them again from scratch. The work is routine, yet the instructions never stay put.

A Page That Becomes an Employee

Maria runs a small cleaning company in Manchester. Every Sunday she once spent two hours turning phone messages into a schedule for four cleaners; now it takes four minutes. She neither hired help nor learned code. She wrote one page of plain instructions once and gave it to Claude. Each week she pastes messages and receives a schedule in her format, with rules such as not booking one client before ten applied. That page is a Skill: stored written instructions an AI follows every time. Think of a recipe card that cannot be lost, or a staff member trained once. Without it, each session resembles a new temp told the same preferences again. A Skill lets you hand over the task, not the briefing.

The Test and the Trap

A Skill is not programming: if you can write a note to a new assistant, you can write one. It is not a prompt typed once and lost; it is named, saved and reusable. It is not only for tech firms. If a task recurs more than twice and you can describe it in writing, a Skill can handle it. The common mistake is building one giant Skill to run everything. Work needs boundaries. "Answer customer emails in my voice" is a job; "do my admin" is a wish. Start with small, sharp roles, then teach them to collaborate.

Ordinary Proof

The pattern shows up in unglamorous work:

• A Leeds driving instructor turns lesson notes into parent progress reports that once consumed her Sunday.
• A two-man landscaping firm drafts quotes from a price sheet, relieving the partner who hates paperwork.
• An accountant who dismissed AI converts client emails into file notes in his practice's twenty-year format.

None is glamorous. Each is repeated, describable and quietly disliked.

Ray fixes garage doors near Phoenix. At fifty-eight, with two vans and a flip phone until 2022, he called himself allergic to logins. His daughter built his first Skill during Sunday lunch from his sent messages and twenty minutes of grumbling. It handled the after-job summary he hated. Ray records a forty-second voice memo, pastes the transcript, and gets a clean summary in his blunt style. He named it Donna and still denies using AI. Within a fortnight it disappeared into routine. Six months on he counts forty minutes a day recovered, fewer complaints, and referrals from a home-warranty company that never chases his paperwork. Clear routines and strong opinions matter more than technical confidence.

Before the First Hire

Before hiring, write down three tasks repeated this week and last week; those are your first job descriptions. A paid Claude plan is generally required. Treat AI chat like email: ordinary business material is fine, passwords and piles of private data are not. Plain notes suffice; your sent messages supply your voice. Repetition can go; judgment, relationships and decisions stay with you.

Key Takeaways

• List three tasks you repeated this week and last week; each one you can spell out in writing is your first job description.
• Give each Skill one narrow job rather than a single catch-all meant to cover your whole workload.
• Save and name the instructions so the same task runs again next month without you explaining it a second time.
• Paste in your own sent messages so the output sounds like you, and keep passwords and piles of private data out of the chat.
• Retain judgment, relationships and decisions yourself; what you pass on is the repeatable work you would rather not do again.

Chapter 2. Your First Skill in 20 Minutes

Overview

Every business answers the same questions repeatedly, and the owner's voice, prices, and rules live only in their head. The problem is getting all of that into something that can write a reply a customer would actually receive.

The slow-reply problem

A photographer named Dana was losing bookings, not because her photos were weak but because her replies were slow. Brides email five photographers on a Tuesday morning and the first two answers usually win; Dana wrote back at night, tired, in three short lines. She now answers in under a minute, in her own voice, with prices and a calendar link, from one Skill built in an evening.

The Skill drafts customer replies: paste the message and Claude writes a complete answer in your tone, on your facts, under your rules. It comes first because almost every business repeats the same answers, and the payoff lands the same day.

Collect three things first

Ten minutes of preparation, most of it copying:

1. Two real replies you sent recently and liked, lifted from your sent folder. Real ones teach your voice better than anything written for the occasion.
2. Your facts: prices or a range, what is included, availability, booking steps, five to ten lines in all.
3. Your rules, the always and the never: never promise a date before checking the calendar, and always ask where the customer found you.

Build it

1. Find Skills under Settings, then Capabilities or Skills, and start a new one.
2. Name it plainly: Customer Reply Skill.
3. Paste the recipe card, replacing the bracketed parts with your own details.
4. Save.

The recipe card has six parts: name, job, facts, rules, voice shown through two real replies, and where the job ends. That last line carries the most weight: never invent prices or dates, and write [CHECK THIS] wherever you must supply the answer yourself.

Test, then fix a line at a time

Run a real enquiry through it and read slowly: does it sound like you, are the facts right, did it respect your rules? Dana's first draft was too formal, so she added one instruction, to write the way she talks to a friend who is also a client, and by her third test she sent a reply to a real bride untouched. About eighty percent right first time is normal.

When something is off, do not rewrite the Skill. Find the missing rule and add one line.

• Long replies: cap them at 120 words.
• Invented facts: strengthen the [CHECK THIS] rule.
• Missed question: answer every question, in the customer's order.

Every Skill in the book, the fifteen templates in Chapter 10 and the client work in Chapter 9 included, runs on the same build loop: prepare real material, write plain instructions, test with real work, fix one line at a time.

Three messages worth testing

• Easy: the enquiry that comes five times a week, obvious questions in obvious order. Failing it means a gap in your facts.
• Hard: several questions stacked, one beyond your facts. It should answer each in order and mark [CHECK THIS] rather than invent a policy.
• Weird: the vague message, the broken-English one, the complaint wearing a question. It should stay polite, inside your rules, and flag what it cannot know.

Twenty minutes, timed

Karen, who runs a dog-grooming salon in Ohio, built hers on a Tuesday night. Six minutes went to digging two examples out of a chaotic sent folder. Typing her facts, she noticed the laminated menu by the till omitted the matted-coat surcharge she explains on the phone five times a week: the Skill was auditing her business before it had run once. Her first draft came back, in her words, "eighty percent me, and politer than I am on a Tuesday," with the salon's name wrong and a Saturday offered. Two lines fixed both, and her third test went to a real customer untouched.

Dana saves about four hours a week now; a plumber's simpler enquiries go out unedited nine times in ten.

Key Takeaways

• Build a customer reply Skill before any other, because the first answer to an enquiry usually wins the job, and slow evenings spent writing three tired lines are losing work you already earned.
• Spend ten minutes gathering real material before you open the builder: two replies you actually sent and liked, your prices and booking steps, and your always and never rules. Made-up examples teach the Skill nothing about your voice.
• Make the recipe card's last line a hard stop that forbids invented prices and dates and requires a [CHECK THIS] marker wherever you must supply the answer, since that single line prevents the worst failures.
• Test on three real messages, one routine, one with stacked questions, one strange or complaining, and repair faults by adding a line rather than rewriting the Skill.
• Carry the same loop into everything you build afterward: real material, plain instructions, live test, one correction at a time.

Chapter 3. The Five Questions Every Skill Must Answer

Overview

Instructions that look complete can still produce confident, wrong output, and adding more words or better wording rarely closes the gap. The failure feels unpredictable, which makes it hard to know what to change. Something is missing, but what?

Tomasz, who owns eleven rental flats in Leeds, built a Tenant Message Skill in an evening with one instruction: reply to tenants professionally and sort out their problems. Tested on a broken boiler, it promised an engineer within 24 hours. Tomasz has no engineer on call. Boiler work goes to Gas-Safe Dave, who comes when he can. The reply was polished and wrong because nothing mentioned Dave. Forty minutes of better instructions fixed it.

The five questions

A working Skill answers five questions:

1. The job: what exactly is the task?
2. The facts: prices, availability, policies, the paperwork.
3. The rules: the always-and-never lines.
4. The voice: real examples rather than adjectives.
5. Where the job ends: never invent, write [CHECK THIS].

A broken Skill lacks at least one of them. A pricing error points to thin facts, a wrong tone to thin voice, an undeliverable promise to absent boundaries. The failure marks the blank in the instructions.

The stranger test

Before saving, ask whether a smart stranger new to the business could do the job from the page alone. Claude is that stranger every time. Dave is unknown to it. It does not know Mrs. Patel dislikes early bookings, and it cannot see the calendar, prices, or your patience. Knowledge that stays in your head is invisible to the Skill. Write as if hiring a stranger for their first day, not issuing a prompt.

Four rules that do most of the work

• Use never and always, not try to. “Keep replies under 120 words” works; “try to keep it short” allows failure. Soft words such as professionally, appropriately, ideally, and where possible let wrong answers in.
• Show rather than describe. Two real emails taught voice better than adjectives. Paste last week's schedule and require that exact layout; one real example is worth more than five descriptive lines.
• Write for exceptions. Recall the 2am tenant, the bride asking for a discount, the customer seeking a refund outside the window. Add one line each, such as not naming a discount figure and saying you will call personally.
• Say what to do when unsure. Without it, the Skill guesses confidently in your name, which produced Tomasz's phantom engineer. [CHECK THIS] belongs in every Skill.

Overwriting and the repair

Elena runs a bookkeeping practice in New Jersey. Her client-email Skill ran four pages: history, service philosophy, three paragraphs on accuracy, a software tour, and the real rules buried on page three. It read stiffly and kept citing her twenty years of experience in replies about invoice deadlines. The Skill gave weight to what she emphasized, and she had emphasized credentials. Deleting everything that did not change a reply left one page holding the job, a pointer to the facts, nine rules, two examples, and the boundaries. The stiffness vanished. Give a stranger what they need on day one, not a retirement speech; they need to know invoices go out Thursdays, not why you care.

One skeleton, different businesses

• Maria's cleaning Schedule Skill uses four cleaners, their hours, regular clients, and addresses. It never books Mrs. Patel before 10am, pairs new cleaners with Ana, keeps Friday afternoon for deep cleans, and flags regular-slot changes.
• Dana's wedding Reply Skill uses packages, prices, travel policy, and a calendar link. It answers questions in order, asks where customers found her, avoids discounts in first messages, never confirms a date, and flags anything outside the facts.
• Steve's plumbing Enquiry Skill uses the attached price list. It always gives a range and the next free slot category, keeps a short friendly voice with one example, refuses diagnoses from photos, and flags gas work beyond servicing for a callback.

Three trades, one skeleton.

Key Takeaways

• Treat every wrong output as a pointer to the missing ingredient: an incorrect price means thin facts, a mismatched tone means weak examples, an undeliverable promise means absent boundaries.
• Before saving, read the page as a new hire with no context and note every question you would need to ask; each question marks knowledge still trapped in your head.
• Replace soft qualifiers with hard limits and paste real samples instead of describing the desired tone, since vague guidance lets a wrong answer pass.
• Write explicit lines for the awkward requests and a fallback that halts guessing, because a confident invention in your name is worse than a flagged gap.
• Cut anything that does not change a reply, including credentials and philosophy; extra material shifts the Skill's emphasis and makes it sound like a brochure.