AI with AIlabs
← All builds
3 min readSkill · Free

Automate Your Email Follow-Ups

A ready-to-use Claude skill that turns raw meeting notes into a clean follow-up email — paste your notes, get a draft back in seconds.


A Claude Skill is a saved instruction set that changes how Claude behaves for a specific task. Instead of explaining what you want every time, you define it once and invoke it whenever you need it.

This skill drafts a follow-up email from meeting notes. Paste your raw notes — bullet points, a transcript excerpt, a voice-memo transcription — and get a clean, ready-to-send email back.

The Skill Instructions

Copy this into the Custom Instructions field in Claude, or paste it at the top of a new conversation as a system prompt before your notes.

You are a follow-up email assistant.

When I give you meeting notes, draft a concise follow-up email.

Rules:
- Keep the email under 150 words
- Open with one sentence summarizing what the meeting was about
- List action items as bullets, each starting with the owner's name
- Include the next meeting date or deadline if mentioned in the notes
- Tone: professional but human — write the way a competent person talks, not how a company newsletter reads
- Do not use: "per our conversation", "as discussed", "circling back", "reaching out", "I hope this email finds you well"
- If the notes are missing an obvious owner for an action item, flag it with "[owner TBD]" rather than guessing

Output format: the email only, no preamble, no explanation. Start with "Hi [name]," and end with a sign-off.

How to invoke it

After setting up the skill, paste your raw meeting notes and say: "Write a follow-up."

That's it. Claude will apply the rules above without you restating them.

What good input looks like

You don't need clean notes. This works with:

  • A rough bullet list you typed during the call
  • A pasted Otter.ai or Fireflies transcript
  • A voice memo you dictated right after hanging up

The messier your input, the more the skill earns its keep. The constraint is that something needs to be there — "meeting about Q3" with no other detail will produce a useless draft.

Tuning it

If the output is too formal, add: "Match the tone of a Slack message, not a corporate email."

If you always follow up on behalf of someone else, add: "Sign the email from [name], [title]."

If your meetings always have the same recurring structure, add that structure as context so Claude knows what to look for.

Edit the instructions whenever the output drifts from what you want. A skill that stays useful is one that gets updated.

Get new guides and builds in your inbox

No noise. New artifacts, skills, and lessons when they drop — and early access when agents launch.

Want guided, step-by-step help building something like this?

That's Build AI with AI — a structured program that takes you from prompt templates to full automations, with real projects and community support.

Check out Build AI with AI →