follow-up
Write follow-up emails that re-engage without being annoying. Uses proven psychology for follow-up sequences. 42% of replies come from follow-ups.
Best use case
follow-up is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Write follow-up emails that re-engage without being annoying. Uses proven psychology for follow-up sequences. 42% of replies come from follow-ups.
Write follow-up emails that re-engage without being annoying. Uses proven psychology for follow-up sequences. 42% of replies come from follow-ups.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "follow-up" skill to help with this workflow task. Context: Write follow-up emails that re-engage without being annoying. Uses proven psychology for follow-up sequences. 42% of replies come from follow-ups.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/follow-up/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How follow-up Compares
| Feature / Agent | follow-up | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Write follow-up emails that re-engage without being annoying. Uses proven psychology for follow-up sequences. 42% of replies come from follow-ups.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
post-show-followup
Create post-trade-show follow-up email sequences, lead nurture campaigns, and meeting recap emails. Use this skill when the user needs to follow up with leads after a trade show, exhibition, expo, or conference — including tiered email sequences (hot/warm/cold), thank-you emails, meeting recap emails, badge-scan follow-ups, or any post-event outreach. Triggers on phrases like 'follow up after the show', 'post-show emails', 'write a thank you to people we met at [event]', 'we collected 200 leads at [show], help me write follow-up', 'the show just ended, now what', 'convert trade show leads into pipeline', 'trade show lead follow-up template', 'post-event email sequence', 'convert trade show leads', 'follow up with expo contacts', or 'I have a spreadsheet of contacts from the expo'. Also use this skill if the user mentions having just returned from a trade show and wants to do something with the contacts they collected.
azure-quotas
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: "check quotas", "service limits", "current usage", "request quota increase", "quota exceeded", "validate capacity", "regional availability", "provisioning limits", "vCPU limit", "how many vCPUs available in my subscription".
raindrop-io
Manage Raindrop.io bookmarks with AI assistance. Save and organize bookmarks, search your collection, manage reading lists, and organize research materials. Use when working with bookmarks, web research, reading lists, or when user mentions Raindrop.io.
zlibrary-to-notebooklm
自动从 Z-Library 下载书籍并上传到 Google NotebookLM。支持 PDF/EPUB 格式，自动转换，一键创建知识库。
discover-skills
当你发现当前可用的技能都不够合适（或用户明确要求你寻找技能）时使用。本技能会基于任务目标和约束，给出一份精简的候选技能清单，帮助你选出最适配当前任务的技能。
web-performance-seo
Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.
project-to-obsidian
将代码项目转换为 Obsidian 知识库。当用户提到 obsidian、项目文档、知识库、分析项目、转换项目 时激活。 【激活后必须执行】： 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入规则（默认到 00_Inbox/AI/、追加式、统一 Schema） 3. 执行 STEP 0: 使用 AskUserQuestion 询问用户确认 4. 用户确认后才开始 STEP 1 项目扫描 5. 严格按 STEP 0 → 1 → 2 → 3 → 4 顺序执行 【禁止行为】： - 禁止不读 SKILL.md 就开始分析项目 - 禁止跳过 STEP 0 用户确认 - 禁止直接在 30_Resources 创建（先到 00_Inbox/AI/） - 禁止自作主张决定输出位置
obsidian-helper
Obsidian 智能笔记助手。当用户提到 obsidian、日记、笔记、知识库、capture、review 时激活。 【激活后必须执行】： 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入三条硬规矩（00_Inbox/AI/、追加式、白名单字段） 3. 按 STEP 0 → STEP 1 → ... 顺序执行 4. 不要跳过任何步骤，不要自作主张 【禁止行为】： - 禁止不读 SKILL.md 就开始工作 - 禁止跳过用户确认步骤 - 禁止在非 00_Inbox/AI/ 位置创建新笔记（除非用户明确指定）
internationalizing-websites
Adds multi-language support to Next.js websites with proper SEO configuration including hreflang tags, localized sitemaps, and language-specific content. Use when adding new languages, setting up i18n, optimizing for international SEO, or when user mentions localization, translation, multi-language, or specific languages like Japanese, Korean, Chinese.
google-official-seo-guide
Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation
github-release-assistant
Generate bilingual GitHub release documentation (README.md + README.zh.md) from repo metadata and user input, and guide release prep with git add/commit/push. Use when the user asks to write or polish README files, create bilingual docs, prepare a GitHub release, or mentions release assistant/README generation.
doc-sync-tool
自动同步项目中的 Agents.md、claude.md 和 gemini.md 文件，保持内容一致性。支持自动监听和手动触发。