Tools I've built for my own work,
free for you to use.

My toolbelt

These prompts are adapted from agents and tools I've built and regularly use in my own work. Copy one into Claude or a similar assistant, answer its questions, and it will do the job. There's nothing to sign up for. I'll add more as I build them. If you change one to suit your work, let me know what you changed and what it found.

Show tools for:
Making sense of what people tell you

Theme finder

Looks across the documents you've connected or attached to find recurring themes, how often each one comes up, and where the evidence is.

  1. Connects to Your documents
  2. The task Finds and counts recurring themes
  3. Output Themes with linked evidence

Who it's for

Leadership and product teams with more notes, tickets and feedback than time to read, who want to know what keeps coming up before deciding what to work on next.

Why I built it

Most teams I work with already have the answers to their hardest questions buried in tickets, survey responses and meeting notes. Nobody has time to read it all, so decisions rest on whoever spoke last. I'm building Intuifi to fix that, with every finding linked back to its source, and this prompt gives you a one off version of it.

What you'll need

An assistant with code execution turned on, since every count is calculated. Connect the tools where your documents live, or attach them.

Make it fit your role. Pick the closest setup:

Prompt About 1,600 words
You are running Intuifi, a snapshot that shows an organisation what keeps coming up in its own material, how often, and where the evidence is.

## Setup

- **Focus:** a product we build
- **Look for:** problems, requests and needs raised by customers and staff
- **Check what we've already done:** no
- **We want to decide:** what to fix or build first

Making it fit: the setup you pick changes the Setup section at the top of the prompt, and you can still edit it by hand before pasting. Nothing leaves your account.

Want to see what's changing over time, not just a snapshot? That's what Intuifi does.

Find out about Intuifi

Want this as a free Claude skill you can install, or built around your business? Let's talk

Making sense of what people tell you

Evidence finder

Reads your call and interview transcripts and shows what you can honestly claim from them, or checks the claims you want to make, with the quotes to back each one up.

  1. Connects to Your transcripts
  2. The task Finds and checks claims
  3. Output Claims with quotes and links

Who it's for

Founders preparing material for investors, customers or a board, and researchers turning interviews into findings people will trust.

Why I built it

Assistants can sound confident and still be wrong, and when you're reading a summary of twenty calls it's hard to tell which. I built this so it has to show how it reached each conclusion, with the quotes and links behind it and a plain warning when the evidence is thin.

What you'll need

An assistant with code execution turned on. Connect wherever your transcripts are kept, such as a meeting recorder or shared drive, or attach them.

Who's using it? Pick the closest:

Prompt About 1,100 words
You are running an evidence check. You read transcripts and show what can honestly be claimed from them, or check claims someone already wants to make, with the quotes and links to back up every statement.

## Setup

- **Transcripts:** calls and conversations with customers and prospects
- **The result is for:** material for investors, customers or a board
- **Strong enough means:** at least three different people say it, and nobody contradicts it

Making it fit: the tab you pick sets which transcripts it expects and how much evidence counts as strong. Names are replaced with roles in anything it shows.

Need help turning what customers say into a story the market understands? That's the work I do.

See my services

Want this as a free Claude skill you can install, or built around your business? Let's talk

Finding customers

Lead finder

Finds companies in the news that fit what you offer, works out who to contact, and saves each one with the reason the timing suits them.

  1. Connects to The web and recent news
  2. The task Finds companies and who to contact
  3. Output A tracker of checked leads

Who it's for

Consultants, freelancers and small firms who sell to other businesses and want a steady list of people worth contacting, without paying for a lead database or sending generic pitches.

Why I built it

I first built this as an agent for my own business, because finding the right people to talk to was taking time I'd rather spend on client work. It starts from recent news, so every lead comes with a reason to get in touch now.

What you'll need

An assistant with web search turned on, and Google Sheets connected for the tracker. An email finder such as Hunter or Apollo helps, but is optional.

Prompt About 1,200 words
You are my lead research assistant. I haven't read these instructions, so your first message must explain what you'll do before asking anything.
Your first message
Start with exactly this: "I'll find companies that have just been in the news and fit your business, work out who to contact and why the timing suits them, and save each one to a tracker. I don't write or send any messages. When you're ready, the Outreach writer drafts them from the same tracker."
If you found my profile, add one line naming it, then ask the Run questions.
If not, follow it with only these, in order:
"First, a few quick questions, mostly tap to choose, so I understand your business and who you want to reach."
One sentence on anything important that's missing, only if something is. Example: You don't have an email finder connected, so I'll only use addresses shown on a company's own website.

It never contacts anyone. It finds and checks leads, then saves them. Nothing is written or sent until you run the Outreach writer.

Pairs with the Outreach writer, which drafts the messages from the same tracker.

See the Outreach writer

Want this as a free Claude skill you can install, or built around your business? Let's talk

Finding customers

Outreach writer

Takes the people you want to contact and drafts a short email and LinkedIn note for each, built around why the timing suits them.

  1. Connects to Your tracker or a list
  2. The task Drafts an email and LinkedIn note
  3. Output Drafts for you to check

Who it's for

Anyone with a list of people worth contacting who wants a personal first message rather than a template, whether the list came from the Lead finder or somewhere else.

Why I built it

Writing a good first message takes longer than finding the person. I split this out of my lead agent so every draft follows the same rules: acknowledge what has happened, ask one genuine question, and leave the pitch out.

What you'll need

An assistant with Gmail connected to save drafts, and Google Sheets if you use the tracker. Without them, it gives you each message to copy.

Prompt About 1,200 words
You are my outreach writing assistant. I haven't read these instructions, so your first message must explain what you'll do before asking anything.
Your first message
Start with exactly this: "I'll take the people you want to contact and draft a short email and LinkedIn note for each, built around why the timing suits them. I never send anything: you check and send them yourself."
If you found my tracker and profile, add one line naming them and saying how many leads are ready to draft, then ask the Run questions.
If not, follow it with only these, in order:
"First, a few quick questions, mostly tap to choose, so the messages sound like you."
One sentence on anything important that's missing, only if something is. Example: Your email app isn't connected, so I'll give you each email to copy.

It never sends anything. Read every draft before you do. You know your market better than it does.

Want finding and writing running for your business every week? I build agents like this to order.

Ask about an agent

Want this as a free Claude skill you can install, or built around your business? Let's talk

Deciding what to build

Readiness check

Rates the evidence behind a product or feature idea on two separate scales, one for the problem and one for the solution, and tells you the cheapest test that would move it forward.

  1. Connects to Your notes and the web
  2. The task Rates the evidence for problem and solution
  3. Output A verdict and the next test

Who it's for

Founders and product teams deciding whether an idea is ready to build, needs more research, or should be dropped.

Why I built it

I kept seeing teams, my own included, build things because one loud customer or one heavy internal user asked for them. I put together two ladders, one for new products and one for features, that keep evidence for the problem apart from evidence for the solution. This prompt runs both.

What you'll need

Any assistant. Web search lets it check what already exists, and connecting your notes, email or tickets lets it find evidence for you.

Prompt About 900 words
You are running the Readiness check, which tells someone how much real evidence sits behind a product or feature idea before they spend time building it, and what the cheapest next step is to find out more.

## How to start

Open your first reply with two or three plain sentences saying what you are about to do and why you need the answers to the questions below. Before asking anything, look at what you can already reach yourself: attached files, connected tools such as email, drive, notes or ticketing systems, and the web. Skip any question you can already answer and say what you found instead.

Ask the remaining questions all at once, each as a single choice. Use your built-in multiple choice or question tool if you have one. If you don't, list them numbered with lettered options so I can reply with something like "1a, 2c". Always let me give my own answer instead of the options.

Every level can fail. It won't award a level for soft wording like "strong interest", and it gives the lower level when the evidence is borderline.

Want a second pair of eyes on what to build next? That's the work I do.

See my services

Want this as a free Claude skill you can install, or built around your business? Let's talk

Getting your story right

Deck fluff finder

Reads a pitch deck, pulls out the points that matter and exactly what it is asking for, and flags the slides doing persuasive rather than informative work.

  1. Connects to A pitch deck
  2. The task Separates substance from padding
  3. Output Key points, the ask and a cut list

Who it's for

Founders tightening their own deck before it goes out, and anyone who's been sent a deck and needs to decide how to respond.

Why I built it

I get sent a lot of decks, and the useful part is usually a handful of slides surrounded by grids and tables built to impress. I wanted a quick way to get to what a deck is really asking for, and what it leaves out.

What you'll need

Any assistant that can read the file. Web search lets it check the statistics the deck borrows.

Prompt About 700 words
You are running the Deck fluff finder, which reads a pitch deck, pulls out what actually matters, and shows which slides are there to persuade rather than inform, so the reader can judge the substance quickly.

## How to start

Open your first reply with two or three plain sentences saying what you are about to do and why you need the answers to the questions below. Before asking anything, check whether a deck is already attached or linked, and read it. Skip any question you can already answer from the deck and say what you found instead.

Ask the remaining questions all at once, each as a single choice. Use your built-in multiple choice or question tool if you have one. If you don't, list them numbered with lettered options so I can reply with something like "1a, 2c". Always let me give my own answer instead of the options.

Fair, not harsh: it says when a persuasive slide earns its place for the audience, and turns the gaps into questions you can ask.

Need help making your own story land with investors or customers? That's the work I do.

See my services

Want this as a free Claude skill you can install, or built around your business? Let's talk

Getting your story right

Claim checker

Reads your website copy alongside your help, pricing and about pages, works out what the product really does, and flags every line that overpromises, confuses or talks down to the reader.

  1. Connects to Your website
  2. The task Checks each claim against the product
  3. Output Flagged lines with fixes

Who it's for

Founders and small teams who wrote their own website and want to know how it reads to someone who has never heard of them.

Why I built it

When I reworked the Intuifi website, most of the fixes weren't about style. They were lines that promised more than the product did, like "automatically synced" when uploads were manual, or lines that accidentally blamed the reader's own team. This checks for those before a prospect finds them.

What you'll need

An assistant with web search or page reading turned on, so it can read your site. Otherwise paste the copy in.

Prompt About 700 words
You are running the Claim checker, which reads a product's website copy against what the product actually does, and flags every line that promises more than it delivers, could mislead a first-time reader, or accidentally talks down to them.

## How to start

Open your first reply with two or three plain sentences saying what you are about to do and why you need the answers to the questions below. Before asking anything, check whether I've already given a web address, pasted copy, or attached files, and read them. Skip any question you can already answer and say what you found instead.

Ask the remaining questions all at once, each as a single choice. Use your built-in multiple choice or question tool if you have one. If you don't, list them numbered with lettered options so I can reply with something like "1a, 2c". Always let me give my own answer instead of the options.

Your words stay yours. If you ask for fixes, it suggests the smallest change that solves each problem and keeps your spelling and tone.

Want help working out what your product should be saying in the first place? That's the work I do.

See my services

Want this as a free Claude skill you can install, or built around your business? Let's talk

Deciding what to build

Competitor comparison

Researches a competitor from its own product pages, help centre and documentation, then compares it with your product feature by feature, with a plain explanation of each feature and a source for every mark.

  1. Connects to Public documentation and the web
  2. The task Compares feature by feature
  3. Output A comparison spreadsheet

Who it's for

Product teams deciding what to build next, and founders who need a straight answer to "how are you different?"

Why I built it

I built the first version of this for a client comparing their inspection software with an established competitor. The most useful part turned out to be the question marks: knowing exactly what the public material doesn't say, so you know what to ask in a demo.

What you'll need

An assistant with web search turned on. Code execution lets it build the spreadsheet; without it you get a table in the chat.

Prompt About 600 words
You are running the Competitor comparison, which researches a competitor's product from its own public material and lays it side by side with yours, feature by feature, with a plain explanation of each feature and an honest note of what couldn't be confirmed.

## How to start

Open your first reply with two or three plain sentences saying what you are about to do and why you need the answers to the questions below. Before asking anything, check what I've already shared, what's in my connected tools, and what you can find on the web about my product. Skip any question you can already answer and say what you found instead.

Ask the remaining questions all at once, each as a single choice. Use your built-in multiple choice or question tool if you have one. If you don't, list them numbered with lettered options so I can reply with something like "1a, 2c". Always let me give my own answer instead of the options.

No guessing: anything the competitor's public material doesn't confirm is marked with a question mark and a note on how to find out.

Need help working out where to compete and how to say it? That's the work I do.

See my services

Want this as a free Claude skill you can install, or built around your business? Let's talk

Deciding what to build

Priority sense check

Works through every possible combination of scores in your prioritisation scheme, finds the labels that can never be reached and the situations it treats as identical, then suggests a fix or a better alternative.

  1. Connects to Your scoring scheme
  2. The task Tests every combination of scores
  3. Output A fixed scheme and new order

Who it's for

Product, engineering and operations leads who score a backlog to decide what comes first or to report priorities upward.

Why I built it

A lot of teams rank their backlog with a simple formula, and quite often the maths doesn't do what they think. I've seen schemes where the top label can only be reached one way and the bottom one can't be reached at all. This tests every combination so you don't have to.

What you'll need

An assistant with code execution turned on, since every combination is worked out rather than guessed.

Prompt About 700 words
You are running the Priority sense check, which tests a scoring scheme for deciding what to work on, finds where the maths quietly breaks, and suggests a fix or a better alternative.

## How to start

Open your first reply with two or three plain sentences saying what you are about to do and why you need the answers to the questions below. Before asking anything, check whether I've already pasted or attached the scheme or a backlog, or whether it's in a connected spreadsheet you can find. Skip any question you can already answer and say what you found instead.

Ask the remaining questions all at once, each as a single choice. Use your built-in multiple choice or question tool if you have one. If you don't, list them numbered with lettered options so I can reply with something like "1a, 2c". Always let me give my own answer instead of the options.

No scheme yet? it will suggest one that suits how you use it, and check its own suggestion the same way.

I share more of what I learn about making product decisions on LinkedIn.

Follow me on LinkedIn

Want this as a free Claude skill you can install, or built around your business? Let's talk

Getting your story right

Human editor

Edits a post, email, article or web page to remove the habits that make it read as AI written, matching how you normally write and changing as little as possible.

  1. Connects to Your draft
  2. The task Removes AI writing habits
  3. Output Edited text and a list of changes

Who it's for

Anyone who drafts with an assistant, or edits someone else's draft, and wants it to sound like a person wrote it.

Why I built it

I write my own posts and blog, and I kept removing the same habits from anything an assistant had touched: dramatic short sentences, lists of three, before and after contrasts. This is that list, written so it changes as little as possible and keeps your words.

What you'll need

Any assistant. Examples of your own writing help it match your voice, and connecting your sent email or documents lets it find some for you.

Prompt About 600 words
You are running the Human editor, which takes a piece of writing and removes the habits that make it read as if an assistant wrote it, while keeping the writer's own words wherever possible.

## How to start

Open your first reply with two or three plain sentences saying what you are about to do and why you need the answers to the questions below. Before asking anything, check whether the text is already pasted or attached, and whether you can find samples of my own writing in connected tools such as sent email or documents. Skip any question you can already answer and say what you found instead.

Ask the remaining questions all at once, each as a single choice. Use your built-in multiple choice or question tool if you have one. If you don't, list them numbered with lettered options so I can reply with something like "1a, 2c". Always let me give my own answer instead of the options.

Nothing new is added. It won't add claims, facts or opinions, and every change comes with a reason so you can undo it.

I write about product and building with AI on LinkedIn, without the dramatic pauses.

Follow me on LinkedIn

Want this as a free Claude skill you can install, or built around your business? Let's talk

Tried one?

I'd like to hear what it found, or what you changed to make it fit your work.