Follow Up
- 387 installs
- 38 repo stars
- Updated February 5, 2026
- humanizerai/agent-skills
follow-up is an agent skill that drafts short, psychology-backed follow-up emails in three sequence steps for developers who need to re-engage cold prospects without sounding pushy or repetitive.
About
follow-up is a user-invocable HumanizerAI agent skill in humanizerai/agent-skills for writing follow-up emails that re-engage prospects who ignored an initial outreach. The skill cites that 42% of replies come from follow-ups and structures three attempts: a 3–5 day Bump assuming busyness, a 7–10 day Value-Add with new insight, and a 14+ day Breakup granting an easy out. Hard rules cap messages at 30–75 words, forbid guilt trips and empty just-checking-in openers, and require a single CTA with a brief callback to the original email. Argument hints accept original context, days since sent, and follow-up number 1–3. Developers reach for it after product demos, support threads, or outbound sales when they want natural copy without manual template hunting. Output includes subject line, body, framework used, differentiation notes, and word count for quick review before sending.
- Humanized follow-up drafts
- Post-chat loop closure
- Re-engagement prompts
- Agent workflow hooks
- Tone-preserving templates
Follow Up by the numbers
- 387 all-time installs (skills.sh)
- +14 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #2,014 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/humanizerai/agent-skills --skill follow-upAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 387 |
|---|---|
| repo stars | ★ 38 |
| Last updated | February 5, 2026 |
| Repository | humanizerai/agent-skills ↗ |
How do you write a follow-up email that gets replies?
Draft and schedule human-sounding follow-ups after agent chats, demos, or support so threads close, leads re-engage, and tone stays natural without manual copy-paste.
Who is it for?
Developers and technical founders doing outbound sales or post-demo nurture who need concise, non-needy follow-ups on a 3–5, 7–10, and 14+ day cadence.
Skip if: Long-form marketing newsletters, automated drip platform configuration, or legal contract negotiation threads that need formal correspondence instead of short bumps.
When should I use this skill?
The developer needs a follow-up email after no reply, specifying original context, days since sent, and whether it is follow-up number 1, 2, or 3.
What you get
Three-step follow-up email drafts with subject lines, framework labels, word counts, and differentiation notes ready to send
- Follow-up email draft
- Subject line suggestion
- Framework and word-count notes
By the numbers
- Defines 3 follow-up sequence steps with distinct frameworks
- Enforces 30–75 word maximum per follow-up email
- Cites 42% of replies coming from follow-up messages
Files
Write Follow-Up Email
Generate a follow-up email that re-engages prospects who didn't respond.
Input
Parse $ARGUMENTS for:
- Original email or context of first outreach
- Days since last email: How long ago was it sent
- Follow-up number: Is this #1, #2, or #3?
- New context (optional): News, trigger events, new value to offer
If original context is missing, ask for the key points from the first email.
Strategy by Follow-Up Number
Follow-up #1 (3-5 days after)
- Assume they're busy, not uninterested
- Add new value or angle
- Keep it shorter than original
Follow-up #2 (7-10 days after)
- Try a different approach
- Share a relevant insight or resource
- Reframe the value prop
Follow-up #3 (14+ days after)
- "Break-up" email or permission-based close
- Give them an easy out
- Last attempt before moving on
Frameworks
The Bump
- Quick, friendly nudge
- "Floating this back up" energy
- Best for follow-up #1
The Value-Add
- Share something useful (article, insight, idea)
- Shows you're thinking about their problems
- Best for follow-up #2
The Breakup
- "Should I close your file?"
- Creates urgency without pressure
- Best for follow-up #3
Hard Rules
1. Shorter than original - Each follow-up gets shorter 2. New angle: Don't just repeat the first email 3. No guilt trips: "I haven't heard back" sounds needy 4. No "just checking in": Empty phrase, add value instead 5. Reference original: Brief callback to first email 6. One CTA: Same or simplified ask 7. 30-75 words max: Follow-ups should be scannable
What NOT to Write
- "I wanted to follow up on my last email" (weak opener)
- "I'm sure you're busy but..." (apologetic)
- Resending the exact same email
- Being passive-aggressive about no response
- Multiple CTAs or new complex asks
Output Format
Subject: Re: [original subject] or [new short subject]
[Email body]
[First name]Framework used: [which one] What's different: [how this differs from original] Word count: [number]
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Use follow-up for short sequenced re-engagement copy rather than full cold email generation skills that draft the first outreach.
FAQ
How many follow-ups does the follow-up skill support?
The follow-up skill defines three numbered follow-ups: #1 at 3–5 days using the Bump framework, #2 at 7–10 days with Value-Add insight, and #3 at 14+ days as a Breakup or permission-based close. Each must stay shorter than the original email.
What length limits does follow-up enforce?
The follow-up skill caps email bodies at 30–75 words, requires one CTA, forbids guilt trips and just-checking-in openers, and mandates a brief reference to the original outreach so messages stay scannable and value-focused.
What stat does follow-up cite about replies?
The follow-up skill frontmatter notes that 42% of replies come from follow-up messages, reinforcing why a short sequenced bump, value-add, or breakup email is worth sending after an initial outreach goes unanswered.