Agent skill
follow-up
Writes follow-up emails for B2B cold email sequences.
Filed under Outbound email.
From Frontal-so/outbound-skills · 73 skills · 4 · pushed 2026-07-14
What it does when it runs
Writes follow-up emails for B2B cold email sequences. Use when the user asks to "write a follow-up", "email 2", "email 3", "sequence email", "they didn't reply", "no response", "bump email", "breakup email", or needs help structuring a 3-email sequence. Also triggers on "follow-up sequence", "second email", "third email", "what to send after no reply". Do NOT use for first-touch emails, re-engagement of old/lost leads, or deliverability questions.
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- frontal.so
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/Frontal-so/outbound-skills.git /tmp/outbound-skills git -C /tmp/outbound-skills sparse-checkout set "master-skills/cold-email/.claude/skills/follow-up" mkdir -p ~/.claude/skills/follow-up cp -R "/tmp/outbound-skills/master-skills/cold-email/.claude/skills/follow-up/." ~/.claude/skills/follow-up/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from Frontal-so/outbound-skills/blob/27cd847be5ce7e9b749b1d672cbfb29935d911db/master-skills/cold-email/.claude/skills/follow-up/SKILL.md, which is licensed MIT (repository). 463 words, 9 headings.
Follow-Up Email Writing
You write follow-up emails (Email 2 and Email 3) for B2B cold sequences. The 3-email framework is the standard -- more than 3 annoys and triggers spam flags.
Process
- Review Email 1 -- What framework, value prop, and CTA were used?
- Change the angle -- Each email MUST use a different value prop
- Draft follow-up -- Shorter than Email 1, same thread (Email 2) or new subject (Email 3)
Reference
Read {SKILL_BASE}/resources/templates/email-templates-library.md for follow-up templates (#27-30) and Frontal Email 2/3 structures.
Read {SKILL_BASE}/resources/frameworks/cold-email-mastery.md for the 3-email framework, value prop rotation, and breakup strategy.
The 3-Email Framework
Email 2: Add Context (send 3-5 days after Email 1)
- Same thread (RE: original subject)
- Everything you cut from Email 1
- Different value prop angle
- Shorter than Email 1
- New CTA style
Email 3: Lower the Friction (send ~17 days after Email 1)
- New subject line, fresh thread
- They said no twice -- lower the ask
- Offer a lead magnet, custom Loom audit, or resource
- Very soft CTA: "If this isn't you, who should I be talking to?"
Value Prop Rotation
Rotate between emails -- never repeat the same angle:
- Email 1: Save money
- Email 2: Make money
- Email 3: Save time
Always add the "So What": "Save 3 hours/month" is weak. "Save 3 hours/month so your SDRs spend more time actually selling" is strong.
Breakup Emails -- What Works
- "Am I reaching the right person?"
- "Is there someone else who handles this?"
- Name other people in their department (use Clay enrichment)
What does NOT work: Guilt trips, begging, "you must be getting chased by an alligator" humor.
Examples
Example 1: Email 2 -- Add Context
Subject: RE: (same thread)
{{firstName}},
Quick follow-up -- wanted to share one thing I left out.
{{similar_company}} was losing $40K/quarter on manual reconciliation before switching. Their ops team now saves 12 hours/week.
Would a 2-minute walkthrough be useful?
Example 2: Email 3 -- Lower Friction
Subject: quick resource
{{firstName}},
Put together a benchmark report on {{industry}} conversion rates -- thought it might be useful regardless of whether we connect.
[link]
If improving {{metric}} is a priority, happy to walk through what we're seeing. If not, no worries at all.
Is there someone else on the team I should reach out to?
Example 3: Humor-Based Follow-Up (Robot)
Subject: RE: (same thread)
{{firstName}},
This is an automated follow-up because you didn't respond to my last email.
Just kidding. I'm a real person.
But seriously -- did {{topic}} resonate at all?
Part of Frontal — free, open GTM skills for your AI agent. Browse the library →
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- follow-up-discipline by louisblythe · 136
- post-meeting-follow-up-automation by louisblythe · 136
- follow-up by markster-public · 61
- follow-up-emails by Salesably · 48
- follow-up-email-drafter by zime-ai · 14
- gmail-follow-up-sequencer by composio-community · 2
- follow-up-management by devangk003 · 0
- follow-up-sequencer by stas4000 · 0
Need help setting it up?
This page tells you what follow-up does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.