Playbook · Getting Started with AI

Build your first
Claude Skill.

A plain-language guide for non-technical professionals. Told through one real case study — turning messy meeting notes into clean action items, the same way every time, in seconds rather than hours. No code. No prompt-writing tricks. If you can describe how you'd want a task done, you can build a Skill.

// Who it's for
Professionals new to AI
// Time investment
~20 min setup, 1 min per use
// You'll need
A Claude.ai account · free works
// You'll walk away with
One working Skill
01 —

The story.

The pain

// A familiar week

Five meetings on Tuesday. Five transcripts. Five action lists no one's written yet.

A common week. Every call you take produces a transcript — Zoom drops it in your inbox, Teams puts it in the chat, your AI notetaker emails it before you've left the room. The transcript itself isn't the problem. The problem is what it isn't: a summary anyone can act on.

So you sit down on Friday afternoon and process five of them back to back. Scroll, skim, copy, reformat, guess at owners, decide whether "we should probably look at that" counts as a risk. Each one takes twenty minutes. Each one ends up shaped slightly differently. By Monday morning, half the actions are already stale.

Not a missing-tool problem. A same-task-done-differently-every-time problem. You know what good looks like. You just keep rebuilding the structure in your head before any work gets done.

That's the shape of a problem a Skill solves. Once you can describe what "good" looks like, you can teach it once. After that, Claude does the heavy lifting and you do the editing.

02 —

What a Skill actually is.

Two ways to use Claude. The difference between them is the entire point of this playbook.

// Without a Skill

A chat each time.

Paste your notes. Explain what you want — structure, tone, what to flag, what to leave out. Every time. The output's usually fine. But you've just spent ten minutes explaining yourself before any work got done. And next Friday, you'll do it again.

// With a Skill

A recipe, written once.

A Skill is a short set of instructions you save to Claude — what the task is, how you like it done, what to watch for, what good looks like. Next time you paste notes, Claude already knows. You stop explaining yourself. The output arrives in your format. Immediately.

// A useful comparison
A Skill is the recipe card on your kitchen wall. It doesn't cook for you. But every time you make the dish, you don't have to remember how — and the dish comes out the same each time, regardless of who's holding the spoon.
03 —

The framework.

5 phases

Every Skill — yours, mine, anyone's — follows the same five moves. Each one is short. None require technical knowledge.

01
Spot
5 min
Notice a task you do over and over, in roughly the same way each time. That's your candidate.
02
Shape
10 min
Write down what "good" looks like. Structure, tone, watch-outs. Two or three examples help most.
03
Build
10 min
Install the skill-creator. Have a conversation. Download the result. Install it.
04
Use
1 min/use
Call your Skill by name. Paste your notes. Get the structured output. That's it.
05
Refine
Ongoing
Use it. Notice what it gets wrong. Add a line. Use it again. Skills improve in use, not in theory.
04 —

Spot a task that repeats.

Phase 1 · ~5 min
01
Spot · Phase 1
Find the repeat.
~5 min

Skills only pay back on tasks you do more than once. The simplest way to find one: look at last week and ask, "What did I do more than three times that I had to think through each time?"

  1. 01
    Scan last week.
    What tasks came up repeatedly? Status updates, meeting summaries, briefing notes, replies to recurring stakeholder questions, weekly emails. Anything where you've thought "I do this every week and I never get faster at it."
  2. 02
    Apply the three signals.
    (1) You do it weekly or more. (2) You have an opinion about how it should look. (3) You start from scratch each time. All three? Strong candidate.
  3. 03
    Pick one.
    Don't try to skill-ify your whole job at once. Pick the task that annoys you the most. Build that one. The pattern will travel.
// My pick
Meeting notes won on all three counts. Five-plus meetings a week, an opinionated format (Decisions / Actions / Risks / Parking lot), and every time I sat down to write the summary I was rebuilding the structure in my head. A Skill begging to be built.
05 —

Shape your house rules.

Phase 2 · ~10 min
02
Shape · Phase 2
Write what good looks like.
~10 min

The part most beginners skip — and the part that decides whether your Skill is genuinely useful or just OK. Spend ten minutes describing "good" in plain English, before you touch Claude.

  1. 01
    Describe the shape of a good output.
    Headings, sections, length. For meeting notes: four headings — Decisions, Actions, Risks, Parking lot. Decisions first because they're scarcest. Parking lot last because it's the easiest to lose.
  2. 02
    Lock the format of the small things.
    Actions are where Skills earn their keep. Every action follows the same shape: verb-first, owner in [brackets], due date — or "TBD" if it's genuinely not yet set.
  3. 03
    Write down what to flag.
    Skills get powerful when they police themselves. Tell Claude what shouldn't pass: any action without an owner, any decision without a clear "who'll do it next," any risk without an escalation path.
  4. 04
    Give it two or three examples.
    Examples beat explanations. Find two summaries you wrote that you were happy with. Claude will study their shape and mirror it.
// Case study · what I wrote down
Meeting → Action Items · house rules.
  • Four headings, always: Decisions · Actions · Risks · Parking lot.
  • Action format: verb-first, owner in [brackets], due date — never invent dates; use "TBD" with a flag if missing.
  • Decisions: one line each, with the rationale in a half-sentence if it's contested.
  • Tone: plain. No "we touched on" or "circle back." Direct language only.
  • Flag aggressively: any action without an owner, any decision without a "next step" owner, anything that smells like a risk but was raised casually.
  • Length: never longer than the original notes. If you can't say it tighter, leave it out.
// Watch for
The temptation to over-specify. If your house rules run to two pages, your Skill will feel rigid and Claude will struggle to apply it. Six to ten clear rules will outperform thirty muddy ones every time.
·

Same notes. Different worlds.

A quick illustration of what the house rules buy you. Both outputs from the same scrappy raw notes. The difference is the Skill.

// Before · plain chat

A fine summary.

In today's meeting, the team discussed several items. Sam mentioned that the demo cadence needs review and suggested moving to Thursdays. The team broadly agreed. Priya raised a concern about Q2 priorities and the dashboard work. There was discussion about pausing it. A few action items came up including following up with finance and updating the team page. Overall a productive session with several items to take forward.
Writing it: 12 min · Re-reading next week: 4 min to find the actions.
// After · with the Skill

A working summary.

DECISIONS · Move sprint demo to Thursday afternoons, effective next sprint. [Owner: M.Chen] · Pause dashboard redesign pending Q2 priorities review. ACTIONS · [Sam] Draft revised demo cadence and circulate by Fri 8 Mar. · [Priya] Set up Q2 prioritisation forum — TBD ⚠ date missing. · [Liam] Update team page with new meeting times by EOD today. RISKS · Dashboard pause may delay Q1 reporting commitment to finance — escalate? PARKING LOT · Quarterly all-hands timing (returned to next planning).
Writing it: 45 sec · Already flagged the missing date.
06 —

Install, build, save.

Phase 3 · ~10 min
03
Build · Phase 3
Three moves: install, build, save.
~10 min

No code. No file editing. Three moves, in order: install the skill-creator (one-time setup), have a conversation with it to develop your Skill, then save the result back to your account.

Setup · one-time
First three steps. Done once.
From your second Skill onwards, you'll start at step 4.
1
Open Claude.ai and sign in.
A free account works. Skills are available on every plan — free through Enterprise.
2
Turn on Code execution.
Settings → Capabilities → Code execution and file creation
Skills run on top of this feature. Flick the toggle on. Stays on across sessions.
3
Install the skill-creator plugin.
Customize → Skills → Browse directory
The skill-creator is itself a Skill — one Anthropic built to help you build others. Browse the directory, find skill-creator, click Install. Once installed, toggle it on in your Skills list.
Build · the conversation
A chat, not a form.
Answer like you would in any conversation. The clearer you are, the sharper the Skill.
4
Start a new chat.
From the home screen, click "New chat." Have the house rules from Phase 2 and your two example summaries ready to paste.
5
Trigger the skill-creator with this prompt.
Paste the prompt below. Replace the bracketed text with your own house rules and examples. The phrase "Use the skill-creator" is what tells Claude to load it and start the interview.
// Paste this · adapt the bracketed parts
Use the skill-creator to help me build a Skill. I want a Skill that takes my messy meeting notes and turns them into a structured action list. Here are my house rules: [paste the six rules you wrote in Phase 2] And here are two examples of summaries I've written that I was happy with: [paste example 1] [paste example 2] Please interview me on anything else you need, then generate the Skill.
6
Walk through the interview.
The skill-creator will ask follow-ups — when should the Skill apply, what format should outputs take, what edge cases to handle, what to do when information's missing. Answer in plain language. Expect five to ten questions.
7
Review the draft.
When the interview wraps, the skill-creator drafts your Skill — a short markdown file with metadata, when-to-use, and instructions. Read it. If anything's missing, say "add a rule that…" in the chat. It'll edit and re-package. Iterate a couple of times.
Save · install your new Skill
Get it out of the chat. Into your account.
One last step: download the file, upload it back. Then it's available in every new chat.
8
Download the .skill file.
Ask the skill-creator: "Package this and give me the .skill file to download." It'll run its packaging script and give you a download link. Save it somewhere you can find — Downloads is fine.
9
Install it in your Skills.
Customize → Skills → + → Upload
Open the Skills page, click +, choose Upload, select the .skill file you downloaded. Toggle it on. It's now available in every new chat.
// A small but useful detail
The most important field in the Skill is its description — the one-sentence summary of when it should apply. Claude uses this to decide which Skill to reach for. Make it specific: not "for meetings" but "for turning raw meeting notes or a transcript into a structured action list with decisions, actions, risks, and parking lot."
07 —

How you'll actually use it.

Phase 4 · 1 min per use

The Skill's installed. From here on, you stop talking to the skill-creator and start talking to your Skill directly. Best practice: call it by name. The auto-detect path works too — it's just less reliable. Here's how each one feels.

// Best practice

Call it by name.

In any new chat, name the Skill explicitly. Removes the guesswork. Claude has many Skills it could reach for — naming yours skips the auto-detection step and goes straight to your rules.

Use my meeting-notes skill on this: [paste raw notes]
// Fallback

Let Claude auto-detect.

If your description field is sharp ("for turning raw meeting notes into a structured action list"), Claude will reach for it on its own when you paste notes. Works well — but a vague description means it sometimes misses.

Here are notes from a meeting today — can you write them up? [paste raw notes]
// Why call by name
Two reasons. Certainty — you know which Skill is running. Speed — Claude doesn't pause to figure out whether your prompt matches a Skill. At five uses a week, the seconds add up. And the day you build a second Skill, by-name invocation stops being optional — auto-detect can't disambiguate between two close descriptions.
What a typical use looks like.
  1. Open a new chat. The Skill is already loaded — you don't need to invoke the skill-creator again. Ever.
  2. Name your Skill. Type Use my meeting-notes skill on this followed by the notes. One line.
  3. Paste your raw notes. Transcript, scratch text from your phone, screenshot of a whiteboard photo, paste from Notion — whatever you have.
  4. Get the structured output. Claude applies your house rules, returns the formatted summary in seconds.
  5. Light edit. Usually 30–60 seconds of touch-up — typos, a name that came through wrong, a phrasing tweak.
  6. Send. Five minutes start to finish. That's the unlock.
// Pro tip · naming your Skill
The name field in your Skill (set during the build phase) is what you call it by — keep it short, lowercase, hyphenated. meeting-notes. weekly-status. brief-prep. Easier to type, easier to remember, easier to share with a colleague who wants to install it.
You stop explaining yourself. That's the entire point.
08 —

Use it. Improve it. Repeat.

Phase 5 · Ongoing
05
Refine · Phase 5
Skills improve in use, not in theory.
Ongoing

The first version of your Skill will be roughly 80% right. The remaining 20% surfaces when you use it. Don't predict every edge case — let real work expose them, then add one line each time. After three or four cycles, you'll have something genuinely good.

  1. 01
    Use it this week.
    Run the Skill on five real meetings. Don't perfect anything yet. Notice what you keep editing in the output.
  2. 02
    Add a line at a time.
    When you find yourself making the same correction twice, that's the next line in the Skill. Open the Skill, add a sentence, save. No re-building needed.
  3. 03
    Resist over-engineering.
    A good Skill stays under two pages. If yours is growing, ask whether you're solving for two different tasks. If so, make a second Skill rather than a longer one.

// Three weeks of real improvements

Week 01
The fabricated date.
// Noticed
Claude assigned plausible-looking due dates to actions that didn't have one in the source notes. Looked confident. Was wrong.
// Added rule
"Never invent dates. If a date isn't in the notes, write TBD and flag it with ⚠."
Week 02
The buried risk.
// Noticed
A risk raised casually mid-meeting — "we might have a problem with finance" — was tucked into Parking lot instead of Risks.
// Added rule
"Treat 'might', 'risk', 'concern', 'worried' as Risk candidates. Promote unless context contradicts."
Week 03
The vague owner.
// Noticed
Actions assigned to "the team" or "comms" — too fuzzy to actually pick up next week. Predictably nothing happened.
// Added rule
"If an owner is a team not a person, flag and ask 'who specifically?' at the end."
09 —

Four ways first Skills disappoint.

Most disappointment with Skills traces back to one of these four. None are hard to fix — they're just hard to spot if no one points them out.

// Pitfall 01

The vague description.

"For meetings" tells Claude almost nothing. The Skill never activates when you want it to, and activates when you don't.

The fix Be specific about the trigger. "For turning raw meeting notes or a transcript into a structured action list" leaves no room for ambiguity.
// Pitfall 02

The kitchen sink.

You try to handle every meeting type — stand-ups, board reviews, 1:1s, retros — in one Skill. The output becomes generic. None of the formats are right.

The fix One Skill per shape of task. A retro Skill is a different beast from a board summary Skill. Make two.
// Pitfall 03

No examples.

You describe what you want but never show it. Claude guesses at "good." Output drifts toward generic professional formatting that isn't yours.

The fix Always include two or three examples of outputs you were happy with. Examples teach faster than rules.
// Pitfall 04

Set and forget.

You build the Skill, it's mostly good, you never refine it. Six months later, it's still missing the obvious patches you would have made in week one.

The fix Edit your Skill once a week for the first month. After that, only when you notice the same correction twice.
10 —

By the end of today.

17 items

Tick all seventeen before your next morning coffee and you have a working Skill that'll keep paying back every week. Anything missing is friction you'll feel by the second use.

0 / 17 complete

// What this opens up

Your first Skill is the hardest one you'll ever build.

Not because it's complicated — it isn't — but because the muscle of "I could just teach Claude this" is new. Once you have one working, the next ten get easier. Most professionals who try this end up with five to ten Skills inside a month: status reports, briefing notes, interview prep, weekly emails.

The biggest unlock isn't time saved on any one task. It's stopping the small act of re-explaining yourself — to Claude, to your team, to your future self — twenty times a week. That adds up.