Skip to prompts

Prompt library

Copy it. Change the brackets.

65 prompts from the sessions. The number on the slide is the number here. Paste into Claude, ChatGPT or Grok, then replace anything in brackets.

  1. 01 Copy
  2. 02 Paste
  3. 03 Replace the brackets

S1 – S12 · in slide order

In the session

The prompts from the slides, in the order you meet them. If you missed one in the room, it's here.

S1

Check that files work

First thing. If a document comes back, Skills will work too.

Make me a Word document with one line in it: "File creation works."

No file? File creation and code execution is switched off. On a Team plan, only an Owner can turn it on.

S2

Write my instructions by interviewing me

Stuck on the blank page. Talking is easier than writing.

Interview me one question at a time so you can write my Instructions for Claude: my role, who I write to, my tone, and what I never say. Five questions, then write it in under 200 words.

S3

The five-line instructions template

Fill in the brackets, then paste it into Instructions for Claude in your settings.

I am [ROLE] at [COMPANY], a [WHAT THE COMPANY DOES] serving [WHO YOU SERVE].
I write mostly to [AUDIENCES].
My tone is [THREE ADJECTIVES]. I never [WHAT YOU NEVER DO OR SAY].
When you draft for me: [LENGTH, STRUCTURE, AUSTRALIAN SPELLING].
When you're unsure: [ASK ME / FLAG IT / MAKE A CALL AND SAY SO].

S4

Teach it your voice

Right after your instructions. Use sentences you actually sent.

Here are a few sentences I wrote recently: [PASTE THREE TO FIVE SENTENCES]. Describe my tone in four adjectives, then rewrite this in my voice: [TEXT TO REWRITE].

To keep it, create a Style from the same sentences.

S5

Tomorrow, prepared

Once your calendar is connected. This is a task prompt.

What's on my calendar tomorrow, and what should I prepare for each one?

S6

The week, thought through

Straight after S5. This one asks it to think, not fetch.

Looking at my week, which of these meetings could have been an email, and which one am I underprepared for?

ThenList the emails and events you used.

S7

Tell your Project where the work lives

One line in your Project instructions. It stops Claude guessing which file you mean.

[TOPIC] documents are in [FOLDER]. Client emails come from [DOMAIN]. The current version is always the one marked [HOW YOU NAME FILES].

S8

The lazy-prompt test

Run it inside your Project, then in a normal chat. The gap is the point.

Draft the usual [UPDATE / REPORT / EMAIL] for this week.

S9

Write my Skill by interviewing me

For a task you do the same way every time. Keep the first one small.

Interview me about how I do [TASK]. Three questions: what I start from, the steps, and the mistakes to avoid. Then write it as a Skill with a one-line description of when to use it, and give me the folder as a ZIP.

Upload it in Customize → Skills → + → Create skill → Upload a skill. The description decides when the Skill runs, so make it say exactly when.

S10

Your real task

The one you named before the session. Use your Project, your Skill and your own files.

Using my [SKILL / PROJECT], do [THE TASK YOU NAMED] for [REAL CLIENT OR MATTER]. Mark anything you couldn't find as [NOT IN FILES] rather than filling it in.

S11

Fix the last answer

The first answer is rarely the one. Say what was wrong instead of starting again.

Close. It's [TOO FORMAL / TOO LONG], it misses [THE POINT], and it should lead with [THE RECOMMENDATION]. Fix those and keep the rest.

S12

Find your next Skill

In a fortnight. Whatever comes back is your next Skill or Project.

What have I asked you to do more than twice this month that follows the same shape each time?

1 – 25 · same numbers as your booklet

Prompts by job

Pick the job, copy the prompt, change the brackets. The tip at the end of each group fixes the most common way it goes wrong.

Email & correspondence1–5

1

The difficult reply

Here's an email I need to answer. The relationship matters and I don't want to concede [THE THING]. Draft a reply that's warm but doesn't move on that point, under 150 words. Tell me what you think they're actually asking for underneath the wording.

2

Messy notes into a client update

Turn these notes into a client update email. Lead with where things stand, then what I need from them, then dates. No preamble, no "I hope this finds you well". Flag anything in my notes that's too vague to send.

ThenGive me a two-line version I can send as a text instead.

3

The chase that isn't nagging

I asked [WHO] for [WHAT] on [DATE] and haven't heard back. Draft a follow-up that makes it easy for them to reply, gives a reason the timing matters, and doesn't sound irritated. Three sentences.

4

Long thread, short answer

Read this thread. Tell me in five bullets: what was agreed, what's still open, who owes what, what's changed since the start, and the one thing needing a decision from me. Don't summarise the pleasantries.

5

Saying no without losing them

I need to decline [THE WORK / THE REQUEST] because [REASON]. Draft a reply that's clear it's a no, keeps the door open, and offers one genuinely useful thing instead. Short. Don't over-explain, because that's what makes a no sound guilty.

When it doesn't sound like you

That's not my voice. It's too [FORMAL / CHATTY]. Here's how I actually write: [TWO LINES].

Say so, and paste two lines of something you actually sent. It corrects in one go.

Meetings & preparation6–10

6

Brief me before this one

Look at my calendar for [WHEN]. For each meeting: who's attending, what it's likely about based on my emails with them, and one thing I should have ready. Put it in a table. Flag any I look underprepared for.

7

The week in one look

Looking at my week, which of these meetings could have been an email, which one am I least prepared for, and where have I double-booked myself in effect if not literally? Be blunt.

A thinking prompt, not a task prompt. Most people only ever ask the first kind.

8

Agenda from a vague brief

Build a 30-minute agenda for a meeting about [TOPIC] with [WHO]. Timebox each item, put the decision we actually need first, and give me the one question that will make the meeting worth having.

9

Notes into actions

Turn these notes into: a short summary, a list of actions with an owner and a date each, and a follow-up email to the group. Where an owner or a date is missing, say so rather than inventing one.

10

Meeting someone for the first time

I'm meeting [NAME] from [ORGANISATION] on [WHEN]. Check what we've exchanged already, then give me: what they likely want, what I should know before I walk in, and two questions worth asking. Say what you couldn't find.

Before anything high-stakes

Argue against this. What's the strongest objection, and what would I struggle to answer?

Two minutes here is worth more than another read-through.

Reading & analysis11–15

11

What am I actually looking at

Read this document. Give me: what it is in one line, the five things that would matter to [WHO], anything unusual compared to a standard one of these, and three questions I should ask before signing off. Quote the clause or paragraph for anything you flag.

12

What changed

Compare these two versions. Only tell me the substantive differences, and ignore formatting and renumbering. For each: what changed, and whether it's better or worse for us. Table, most significant first.

13

Find the risk

Read this as someone whose job is to find what goes wrong. What's the exposure, what's ambiguous enough to be argued either way, and what's missing that should be here? Rank by how much it would cost us if it went badly.

14

Check my thinking

Here's my reasoning on [THE QUESTION]. Where is it weak? What am I assuming without saying? What would someone who disagreed say first? Don't be encouraging. I want the holes.

15

Every date and obligation, in one table

Pull out every date, deadline, notice period and ongoing obligation in this document. Columns: what, who it falls on, when, and the clause. Anything conditional, put the trigger in its own column. Don't infer dates that aren't stated.

Always, on anything that matters

Quote the exact line you're relying on.

Then read the quote. It's the fastest way to catch a confident answer the document doesn't support.

Drafting & content16–20

16

The first draft

Draft [WHAT] for [WHO]. Here's the material and the outcome I want. Use my voice, not corporate register. Give me a version at 400 words and a version at 150, and I'll tell you which direction to go from there.

Choosing between two drafts is faster than editing one.

17

One thing, four places

Take this and give me: a LinkedIn post, a short client email, three sentences for a newsletter, and a paragraph for the website. Same substance, right register for each. Don't repeat the same opening line four times.

18

Explain it to someone who isn't us

Rewrite this for a smart client with no background in [FIELD]. Keep every material point, lose the jargon, and don't dumb down the substance. If a term has to stay, define it in a half-sentence in place.

19

Options, not one answer

Give me six subject lines for this: two plain, two specific about the outcome, two with a bit of edge. One line each on which audience each one suits.

20

The scope section

Draft the scope and deliverables for [THE ENGAGEMENT] from these notes. Be concrete about what's included, and add a short "not included" list, because that's the part that prevents the argument later. Flag anything I've left ambiguous.

The edit that saves the most time

Cut this by a third without losing anything material. Tell me what you cut.

Better than writing shorter first, and it shows you what wasn't earning its place.

Admin & operations21–25

21

Mess into a checklist

Here's how we currently do [PROCESS], described badly. Turn it into a numbered checklist someone could follow in their first week. Mark the steps where things usually go wrong, and flag anything I've left out.

ThenTurn that checklist into a Skill so it runs the same way every time.

22

Monday triage

Look at my inbox and calendar. What needs me this week and what only looks like it does? Three lists: do it, delegate it, let it go. Say why for anything in the third list.

23

Unstructured into a table

Pull the key details out of these [DOCUMENTS / EMAILS] into one table with these columns: [COLUMNS]. Leave a cell blank rather than guessing, and list anything you couldn't find underneath.

24

Write down what's only in someone's head

Interview me about how we handle [THING], one question at a time, and keep going until you've got enough to write it down properly. Then draft the procedure.

25

A template out of three past examples

Here are three [DOCUMENTS] we've sent before. Work out what's constant and what changes each time, then give me a template with the variable parts marked. Tell me where the three disagreed with each other.

The one to run in a fortnight

What have I asked you to do more than twice this month?

Everything on that list is a Project or a Skill you haven't built yet.

pick yours

For your industry

A few that only make sense in your line of work. Choose your industry to narrow the list.

The fortnightly updateProfessional services

For a client matter or engagement that runs for weeks.

Draft the fortnightly update to [CLIENT] on [MATTER / ENGAGEMENT] from these notes. Where things stand, what we need from them, and the next dates. Under 200 words. Flag anything in my notes that isn't settled enough to tell a client.

File note from a callProfessional services

Straight after the call, while you still remember it.

Turn my notes from the call with [WHO] on [DATE] into a file note: who attended, what was discussed, what was agreed, and actions with owners. Mark anything I said I'd check as an open item. Don't add advice I didn't give.

Precedent into a first draftProfessional services

When you'd normally copy last time's document and edit.

Here's our precedent [DOCUMENT] and the facts for this one. Produce a first draft with every changed or uncertain part marked [CHECK]. List the precedent clauses you didn't use and why.

The fee estimate narrativeProfessional services

When the number needs words around it.

Here's the scope and my hours estimate. Write the fee estimate narrative for [CLIENT]: what's included, what isn't, the assumptions the number depends on, and what would change it. Plain English.

Last week's trading, in plain wordsRetail

Monday morning, with the sales export open.

Here's last week's sales export by store. Give me the top and bottom three stores against the week before, any category that moved more than 10%, and three questions I should ask store managers. Don't guess at causes. List what would explain each one.

Head-office brief into a store briefRetail

When a promo lands and stores need it on one page.

Turn this head-office brief into a one-page store brief: what's on, the dates, what staff say to customers, what changes on the floor, and what to check before opening. Plain English, readable on a phone.

The complaint replyRetail

For a complaint you want to settle in one reply.

Draft a reply to this customer complaint. Name the specific problem, say what we'll do and by when, and keep it under 120 words with no defensive language. Our returns policy is [POLICY], so don't promise anything outside it.

The supplier follow-upRetail

When an order or fix is late.

Draft a follow-up to [SUPPLIER] about [ORDER / ISSUE]. State what was agreed, what hasn't happened, the date we need it by and why. Firm, polite, four sentences.

Notes into an aftercare sheetHealth & clinics

For your most common treatment. De-identified notes only.

Rewrite our aftercare notes for [TREATMENT] as a patient sheet: six dot points in plain language, then a short "call us if" section. Use only what's in our notes and don't add any clinical claims.

The patient FAQHealth & clinics

From the questions reception answers every day.

Here are the questions reception answers most often. Write a patient FAQ with one plain-language answer each, under 60 words, and mark any answer a clinician should check as [CLINICIAN CHECK].

The third rescheduleHealth & clinics

Warm, short, and holds the policy.

Draft a reply to a patient asking to reschedule for the third time. Warm and short, offer two times, and mention our cancellation policy: [POLICY]. No names or details beyond what's here.

Supplier chain into a decisionHealth & clinics

When a supplier thread has gone on too long.

Turn this supplier email chain into five lines and tell me the decision I need to make, with the deadline if there is one.

The follow-up after a pitch meetingAgencies & creative

Inside 24 hours, while they're still warm.

I just met [CLIENT] about [BRIEF]. Draft the follow-up: one line on what they need, two examples from our work that fit (from the files only), and one clear next step. Mark anything you couldn't find as [NOT IN FILES].

Brief into a production checklistAgencies & creative

Before anyone books anything.

Turn this client brief into a production checklist: deliverables, formats and sizes, dates, approvals, and who signs off. List the questions the brief doesn't answer.

The monthly client reportAgencies & creative

Exports in, first draft out.

Here are this month's numbers and notes for [CLIENT]. Draft the report in our usual shape: highlights, what worked, what didn't, next month. Every figure must come from what I gave you. Mark gaps as [MISSING].

Hooks for a campaignAgencies & creative

When you need options to react to.

Give me five hooks for [CAMPAIGN] on [PLATFORM], in our voice. No claims we can't back up. One line on which audience each one suits.

pick your stack

Your connected tools

Questions you'd normally go digging for. Each tool still runs on your own login, so Claude sees only what you can already see.

Gmail

  • What came in overnight that actually needs me?
  • Find the thread where we agreed the [X] date and quote it.
  • Draft a reply to the latest one from [NAME]. Don't send it.

Gmail asks before it sends, replies or forwards. Leave that on.

Google Calendar

  • What's on tomorrow, and what should I prepare for each one?
  • Where's my first free 90-minute block this week?
  • Which meetings recur but haven't produced a decision?

Google Drive

  • Find the most recent version of [DOCUMENT] and tell me what changed.
  • Summarise everything in the [FOLDER] folder on [TOPIC].
  • Which of these is the one that was actually signed?

Drive asks before it shares, moves or bins a file. Leave that on.

Slack

  • What did I miss in [CHANNEL] while I was out?
  • Has anyone already answered this before I ask it?

before you act on an answer

Before you trust it

It gets things wrong, and it sounds sure when it does. Add one of these to anything that matters. Your name still goes on the work.

Make it show the line

If it can't produce the line, it isn't in there.

Quote the exact line you're relying on.

Make it show its sources

Then open one. It can pick up an old thread and treat it as the latest.

List the emails and files you used.

Stop it filling gaps

Without this, it fills a gap with something plausible.

Leave it blank rather than guessing, and list what you couldn't find.

Stop it agreeing with you

The way you ask shapes the answer more than most people expect.

Argue the other side as well as you argued that one.

Check it's current

Rates, rules and who holds a role change after its knowledge was set.

Search for the current version of this before you answer, and tell me the date of your source.