$npx -y skills add humanizerai/agent-skills --skill follow-upWrite follow-up emails that re-engage without being annoying. Uses proven psychology for follow-up sequences. 42% of replies come from follow-ups.
| 1 | # Write Follow-Up Email |
| 2 | |
| 3 | Generate a follow-up email that re-engages prospects who didn't respond. |
| 4 | |
| 5 | ## Input |
| 6 | |
| 7 | Parse $ARGUMENTS for: |
| 8 | - **Original email** or context of first outreach |
| 9 | - **Days since last email**: How long ago was it sent |
| 10 | - **Follow-up number**: Is this #1, #2, or #3? |
| 11 | - **New context** (optional): News, trigger events, new value to offer |
| 12 | |
| 13 | If original context is missing, ask for the key points from the first email. |
| 14 | |
| 15 | ## Strategy by Follow-Up Number |
| 16 | |
| 17 | ### Follow-up #1 (3-5 days after) |
| 18 | - Assume they're busy, not uninterested |
| 19 | - Add new value or angle |
| 20 | - Keep it shorter than original |
| 21 | |
| 22 | ### Follow-up #2 (7-10 days after) |
| 23 | - Try a different approach |
| 24 | - Share a relevant insight or resource |
| 25 | - Reframe the value prop |
| 26 | |
| 27 | ### Follow-up #3 (14+ days after) |
| 28 | - "Break-up" email or permission-based close |
| 29 | - Give them an easy out |
| 30 | - Last attempt before moving on |
| 31 | |
| 32 | ## Frameworks |
| 33 | |
| 34 | ### The Bump |
| 35 | - Quick, friendly nudge |
| 36 | - "Floating this back up" energy |
| 37 | - Best for follow-up #1 |
| 38 | |
| 39 | ### The Value-Add |
| 40 | - Share something useful (article, insight, idea) |
| 41 | - Shows you're thinking about their problems |
| 42 | - Best for follow-up #2 |
| 43 | |
| 44 | ### The Breakup |
| 45 | - "Should I close your file?" |
| 46 | - Creates urgency without pressure |
| 47 | - Best for follow-up #3 |
| 48 | |
| 49 | ## Hard Rules |
| 50 | |
| 51 | 1. **Shorter than original** - Each follow-up gets shorter |
| 52 | 2. **New angle**: Don't just repeat the first email |
| 53 | 3. **No guilt trips**: "I haven't heard back" sounds needy |
| 54 | 4. **No "just checking in"**: Empty phrase, add value instead |
| 55 | 5. **Reference original**: Brief callback to first email |
| 56 | 6. **One CTA**: Same or simplified ask |
| 57 | 7. **30-75 words max**: Follow-ups should be scannable |
| 58 | |
| 59 | ## What NOT to Write |
| 60 | |
| 61 | - "I wanted to follow up on my last email" (weak opener) |
| 62 | - "I'm sure you're busy but..." (apologetic) |
| 63 | - Resending the exact same email |
| 64 | - Being passive-aggressive about no response |
| 65 | - Multiple CTAs or new complex asks |
| 66 | |
| 67 | ## Output Format |
| 68 | |
| 69 | ``` |
| 70 | Subject: Re: [original subject] or [new short subject] |
| 71 | |
| 72 | [Email body] |
| 73 | |
| 74 | [First name] |
| 75 | ``` |
| 76 | |
| 77 | **Framework used:** [which one] |
| 78 | **What's different:** [how this differs from original] |
| 79 | **Word count:** [number] |