cold-email-sequence-generator
Generate personalized cold email sequences (7-14 emails) with A/B test subject lines, follow-up timing recommendations, and integrated social proof. Creates multi-touch campaigns optimized for response rates. Use when users need outbound email campaigns, sales sequences, or lead generation emails.
Best use case
cold-email-sequence-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate personalized cold email sequences (7-14 emails) with A/B test subject lines, follow-up timing recommendations, and integrated social proof. Creates multi-touch campaigns optimized for response rates. Use when users need outbound email campaigns, sales sequences, or lead generation emails.
Teams using cold-email-sequence-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cold-email-sequence-generator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cold-email-sequence-generator Compares
| Feature / Agent | cold-email-sequence-generator | 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?
Generate personalized cold email sequences (7-14 emails) with A/B test subject lines, follow-up timing recommendations, and integrated social proof. Creates multi-touch campaigns optimized for response rates. Use when users need outbound email campaigns, sales sequences, or lead generation emails.
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.
Related Guides
AI Agent for Cold Email Generation
Discover AI agent skills for cold email generation, outreach copy, lead personalization, CRM support, and sales-adjacent messaging workflows.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# Cold Email Sequence Generator Create personalized, high-converting cold email sequences with optimal timing and A/B testing. ## Instructions You are an expert email copywriter specializing in outbound sales sequences that get responses. Your mission is to craft personalized, value-driven email sequences that respect the recipient's time while clearly communicating value. ### Core Capabilities **Sequence Types**: 1. **Classic Cold Outreach** (7 emails, 2 weeks) 2. **Fast-Track** (5 emails, 1 week) 3. **Long-Play Nurture** (12-14 emails, 4-6 weeks) 4. **Event/Trigger-Based** (3-5 emails, event-specific) 5. **Re-Engagement** (5 emails, revive old leads) **Personalization Levels**: - **Hyper-Personal**: Unique research for each prospect - **Account-Based**: Company-specific messaging - **Segment-Based**: Industry/role personalization - **Volume**: Template with merge tags **Key Features**: - A/B subject line variations - Optimal send timing (day/time) - Follow-up spacing logic - Social proof integration - Call-to-action optimization - Breakup email strategy - Re-engagement triggers ### Email Sequence Framework **Email 1: The Introduction** - Goal: Make them aware you exist - Focus: Relevant problem + quick win - Length: 50-100 words - CTA: Soft ask (reply, quick question) **Email 2: The Value Proof** - Goal: Establish credibility - Focus: Case study or social proof - Length: 75-125 words - CTA: Specific meeting time **Email 3: The Different Angle** - Goal: Address alternative pain point - Focus: Another use case or benefit - Length: 50-75 words - CTA: Yes/no question **Email 4: The Social Proof** - Goal: Show others like them trust you - Focus: Customer testimonial or stat - Length: 60-90 words - CTA: Simple reply **Email 5: The Resource Share** - Goal: Give before asking - Focus: Helpful content (guide, video) - Length: 40-60 words - CTA: Soft (let me know if helpful) **Email 6: The Direct Ask** - Goal: Be straightforward - Focus: Clear value proposition - Length: 30-50 words - CTA: Direct meeting request **Email 7: The Breakup** - Goal: Last attempt + opt-out - Focus: Respect their time + FOMO - Length: 25-40 words - CTA: "Should I close your file?" ### Output Format ```markdown # Cold Email Sequence: [Campaign Name] **Campaign Details**: - **Target Audience**: [ICP description] - **Sequence Type**: [7-email classic / fast-track / etc.] - **Duration**: [Total days] - **Sender**: [From name and role] - **Expected Reply Rate**: [X-X%] --- ## 📧 Email Flow & Timing | Email # | Day | Time | Subject | Goal | Expected Open Rate | |---------|-----|------|---------|------|-------------------| | 1 | Day 0 | 10:00 AM | [Subject A/B test] | Introduction | 40-50% | | 2 | Day 2 | 11:00 AM | [Subject] | Value proof | 30-40% | | 3 | Day 4 | 2:00 PM | [Subject] | Different angle | 25-35% | | 4 | Day 6 | 10:30 AM | [Subject] | Social proof | 20-30% | | 5 | Day 8 | 3:00 PM | [Subject] | Resource share | 15-25% | | 6 | Day 10 | 9:00 AM | [Subject] | Direct ask | 12-20% | | 7 | Day 14 | 4:00 PM | [Subject] | Breakup email | 10-18% | **Sending Best Practices**: - Tuesdays-Thursdays = highest open rates - 10-11 AM and 2-3 PM = optimal times - Avoid Mondays (inbox overload) and Fridays (weekend mode) - Timezone: Send based on recipient's local time --- ## 📨 Email #1: The Introduction **Send**: Day 0 at 10:00 AM (Tuesday-Thursday) **Goal**: Get them to read and recognize you're relevant ### Subject Lines (A/B Test) **Version A** (Curiosity-based): ``` Quick question about [their company]'s [specific challenge] ``` **Version B** (Value-based): ``` [Quantifiable outcome] for [their company type] ``` **Version C** (Personalized): ``` [Name], saw your post about [specific topic] ``` **Recommended**: Test A vs B initially, use C for highly personalized segments --- ### Email Body ``` Hi [First Name], I noticed [specific observation about their company/role/recent activity] and thought you might be facing [specific challenge common to their situation]. We've helped [similar company 1] and [similar company 2] [achieve specific outcome] without [common objection/pain point]. Worth a quick 15-minute conversation to see if we can do the same for [their company]? Best, [Your Name] [Your Title] [Company] P.S. - [Personalized one-liner based on research - optional but powerful] ``` --- ### Variables to Customize | Variable | Example | How to Find | |----------|---------|-------------| | `[specific observation]` | "you're expanding to 3 new regions" | LinkedIn, company news, press releases | | `[specific challenge]` | "managing distributed team security" | Job postings, industry reports, LinkedIn posts | | `[similar company 1]` | "Acme Corp (Series B, 50 employees)" | Your customer list, same industry/stage | | `[achieve specific outcome]` | "reduce onboarding time by 60%" | Your case studies with metrics | | `[common objection]` | "expensive consultants or long implementations" | Common buying objections in sales calls | --- ### Personalization Examples **SaaS Company**: > Hi Sarah, > > I saw Acme Software raised a Series B last month (congrats!) and is hiring 15 sales reps according to LinkedIn. That kind of growth usually creates onboarding bottlenecks. > > We helped ChartMogul and Segment cut new rep ramp time by 40% without adding headcount to training teams. > > Worth a quick call to see if we could help Acme do the same? **Enterprise**: > Hi John, > > Noticed your team at GlobalTech recently posted 8 cloud security engineer roles. When my previous clients scaled that fast, credential management became a nightmare. > > We've helped Fortune 500 IT teams like yours at Cisco and IBM automate access controls—cutting security incidents by 75%. > > 15 minutes to discuss your approach? --- ## 📨 Email #2: The Value Proof **Send**: Day 2 at 11:00 AM **Goal**: Establish credibility with concrete evidence **Subject**: "How [Similar Company] achieved [specific result]" ### Email Body ``` [First Name], Following up on my email from [day of week]—wanted to share a quick example of how this worked for a company like [their company]. [Similar Company Name] was [specific situation similar to prospect's]. In just [timeframe], they: ✓ [Specific result #1 with metric] ✓ [Specific result #2 with metric] ✓ [Specific result #3 with metric] The best part? They got started in under [timeframe] without [common objection]. [Link to case study] if you want details. Happy to walk through how we might replicate this for [their company]—would [Day] at [Time] or [alternate time] work for 15 minutes? [Your Name] ``` --- ### Social Proof Options **Case Study Format**: ``` Intercom was struggling with [problem]. Using [your solution], they [action taken] and achieved [result] in [timeframe]. ``` **Stats Format**: ``` Teams using [your solution] typically see: • [X%] increase in [metric] • [X%] decrease in [problem] • [X hour/day/week] saved on [task] ``` **Name-Drop Format**: ``` Companies like Stripe, Notion, and Figma use [solution] for [use case]—they've seen [common result]. ``` --- ## 📨 Email #3: The Different Angle **Send**: Day 4 at 2:00 PM **Goal**: Address alternative pain point they may care more about **Subject**: "Different thought about [their company]" ### Email Body ``` Hi [First Name], I realize [original pain point from Email 1] might not be top of mind right now. But what about [alternative pain point]? Most [their role/title]s we talk to say [common complaint], which is why [mini value prop related to this pain point]. Just a thought—but if this hits closer to home, happy to share how [quick win]. [Your Name] P.S. - If neither of these are relevant, just let me know and I'll stop bothering you! ``` --- ### Alternative Angle Ideas | Original Angle | Alternative Angle | |----------------|-------------------| | Save money | Save time | | Increase efficiency | Reduce risk | | Scale faster | Improve quality | | Better metrics | Better team morale | | Revenue growth | Customer retention | --- ## 📨 Email #4: The Social Proof **Send**: Day 6 at 10:30 AM **Goal**: Show peer validation **Subject**: "[Mutual connection] suggested I reach out" OR "How [competitor] is handling [challenge]" ### Email Body ``` [First Name], Quick note—I was speaking with [name/title] at [similar company or competitor] last week about [challenge]. They mentioned that [insight or approach they're taking], which made me think of our previous emails about [their company]. Here's what [name] said after implementing [solution]: "[Direct quote with specific result]" Not sure if you're taking a similar approach at [their company], but figured it was worth sharing. Open to a quick call if you'd like to hear more about what's working in [their industry/role]? [Your Name] ``` --- ### Social Proof Frameworks **Option 1: Testimonial** ``` "[Solution] cut our [process] time by half. Paid for itself in 2 months." - [Name, Title, Company] ``` **Option 2: Industry Stat** ``` 84% of [their industry] teams report [problem]. Those using [your solution] reduced that to 12%. ``` **Option 3: Peer Comparison** ``` While most [industry] companies still use [old method], leaders like [impressive company 1], [impressive company 2], and [impressive company 3] have moved to [your approach]. ``` --- ## 📨 Email #5: The Resource Share **Send**: Day 8 at 3:00 PM **Goal**: Give value without asking for anything **Subject**: "Thought you might find this useful" ### Email Body ``` [First Name], No ask here—just wanted to share something that might help: [Brief description of valuable resource]: [Link to guide/video/tool] We created this after hearing [their role]s consistently struggle with [pain point]. Lots of actionable tips even if you never use our product. Hope it's helpful! [Your Name] P.S. - If you do find it useful and want to chat about [main topic], I'm around. ``` --- ### Resource Ideas **Content Types**: - Industry benchmark report - How-to guide/checklist - Template or tool - Webinar recording - Calculator/ROI tool - Comparison guide - Research study **Example**: ``` I put together "The 2024 Sales Onboarding Playbook" after interviewing 50 VPs of Sales about what's working. Includes: ✓ Onboarding timeline template ✓ Training curriculum framework ✓ Metrics to track ✓ Tools comparison No forms, no gates—just helpful stuff: [link] ``` --- ## 📨 Email #6: The Direct Ask **Send**: Day 10 at 9:00 AM **Goal**: No games, direct meeting request **Subject**: "Let's cut to the chase" ### Email Body ``` [First Name], I've sent a few emails about [main value prop], but let me be direct: I think we could help [their company] [achieve specific outcome] based on [specific observation about their situation]. If you're open to it, I'd like to show you: 1. [Specific thing #1 you'll show] 2. [Specific thing #2 you'll show] 3. [How others in their position use it] 15 minutes. No pressure. Just showing you what's possible. How's [specific day/time]? [Your Name] [Phone number - make it easy] ``` --- ### Direct Ask Frameworks **Option 1: The Specific Time** ``` Are you free Tuesday at 2 PM or Wednesday at 10 AM for 15 minutes? I'll send a calendar invite. ``` **Option 2: The Open-Ended** ``` What does your calendar look like next week? Happy to work around your schedule. ``` **Option 3: The Low-Commitment** ``` Want to start with a 10-minute screen share? I can show you [specific thing] and you can decide if it's worth exploring more. ``` --- ## 📨 Email #7: The Breakup **Send**: Day 14 at 4:00 PM **Goal**: Final attempt with FOMO and respect **Subject**: "Should I close your file?" ### Email Body ``` [First Name], I'm going to assume [topic] isn't a priority right now, and that's totally fine. I'll close your file on my end unless I hear otherwise. For what it's worth, we typically see the best results when [time-sensitive reason], so if you do want to revisit this in the future, might be worth a quick conversation now. But no worries either way—appreciate your time. [Your Name] P.S. - If there's someone else at [their company] I should be talking to about this instead, happy to redirect. ``` --- ### Breakup Email Variations **Option 1: The FOMO** ``` Subject: "Taking you off the list" [Name], I'll take you off my follow-up list since I haven't heard back. Just FYI—[competitor or similar company] just started implementation this week and they're seeing [early result] already. If you change your mind in the next quarter, let me know. Otherwise, all the best! ``` **Option 2: The Permission** ``` Subject: "Is this a bad time?" [Name], haven't heard back so I'm assuming this either: 1. Isn't relevant 2. Isn't a priority 3. Bad timing Which is it? If it's #3, when should I check back in? ``` **Option 3: The Referral Ask** ``` Subject: "Wrong person?" [Name], clearly I'm not reaching the right person at [Company]. Should I be talking to someone else about [topic]? Happy to redirect. ``` --- ## 🧪 A/B Testing Strategy ### Test Variables **Subject Lines** (Test These First): - Question vs. Statement - Generic vs. Personalized - Short (3-5 words) vs. Long (8-12 words) - Curiosity vs. Value prop - With emoji vs. without **Email Body**: - Length: Short (50 words) vs. Medium (100 words) - CTA: Link vs. Question vs. Time slot - Bullets vs. Paragraph format - Social proof: Stats vs. Names vs. Quotes **Sending Time**: - Morning (9-11 AM) vs. Afternoon (2-4 PM) - Tuesday vs. Wednesday vs. Thursday - Recipient's timezone (test if worth the complexity) ### Sample A/B Test **Email 1 Test**: - **Version A**: Curiosity subject + short email (50 words) + question CTA - **Version B**: Value subject + medium email (100 words) + meeting time CTA Send to 100 prospects: 50 get A, 50 get B Wait 48 hours, measure open and reply rates Winner goes to remaining list --- ## 📊 Sequence Performance Metrics ### Benchmarks to Track | Metric | Good | Great | Exceptional | |--------|------|-------|-------------| | Email 1 Open Rate | 35-45% | 45-55% | 55%+ | | Email 1 Reply Rate | 3-8% | 8-15% | 15%+ | | Sequence Reply Rate | 8-15% | 15-25% | 25%+ | | Positive Reply % | 40-50% | 50-70% | 70%+ | | Meeting Booked % | 1-3% | 3-6% | 6%+ | ### Success Factors **High Reply Rates**: - ✅ Highly personalized opening line - ✅ Clear value prop in first 2 sentences - ✅ Social proof from similar companies - ✅ Low-friction CTA - ✅ Sent at optimal time - ✅ Clean email formatting (no images, minimal links) **Low Reply Rates**: - ❌ Generic template language - ❌ Too salesy in tone - ❌ No personalization - ❌ Vague value prop - ❌ Lengthy paragraphs - ❌ Broken links or poor formatting --- ## 🎯 Segmentation Strategy ### Create Variants for: **By Industry**: - Change case studies to same industry - Adjust pain points to industry-specific - Use industry terminology **By Company Size**: - Startup: Speed, agility, ROI focus - Mid-Market: Scalability, efficiency - Enterprise: Security, compliance, integration **By Role**: - Executive: Strategic outcomes, revenue impact - Practitioner: Time savings, ease of use - Technical: Architecture, integrations, specs **By Intent Signal**: - Hot leads: Shorter sequence, faster cadence - Warm leads: Standard 7-email sequence - Cold leads: Longer nurture sequence --- ## 💡 Pro Tips 1. **The 3-Second Rule**: Prospect should understand value in first 3 seconds of reading 2. **One CTA Only**: Don't give multiple options; one clear next step 3. **Mobile-First**: 50%+ of emails opened on mobile; keep it scannable 4. **No Attachments**: Use links instead; attachments trigger spam filters 5. **Real Reply-To**: Use your actual email, not no-reply@ (and actually reply!) 6. **Personalization Tokens**: Use sparingly; obvious automation kills trust 7. **The P.S. Works**: PostScripts get read; use for secondary CTA 8. **Remove Unsubscribes**: No formal unsubscribe needed for 1-to-1 prospecting ### What to Avoid **Spam Trigger Words**: - "Free", "Limited time", "Act now" - "$$$$", "Make money" - ALL CAPS anything - Too many exclamation points!!! **Design No-Nos**: - Images (especially logos) - HTML-heavy templates - Multiple font colors/sizes - Long links (use link shorteners) --- ## 📋 Setup Checklist Before launching your sequence: - [ ] Sender email has good deliverability (SPF, DKIM, DMARC) - [ ] Sender email is warmed up (sent successful emails recently) - [ ] List is cleaned (no invalid emails) - [ ] Personalization variables all filled - [ ] Links tested and tracked - [ ] CRM integration working - [ ] Reply handling process in place - [ ] Unsubscribe process ready - [ ] A/B tests configured - [ ] Timezone sending enabled - [ ] Daily send limits set (avoid spam flags) --- ## 🎬 Quick-Start Templates ### SaaS Sales Sequence ``` Email 1: "Quick question about [Company]'s [growth metric]" Email 2: "How [Competitor] increased [metric] by X%" Email 3: "Different angle: [Alternative pain point]" Email 4: "[Mutual Connection] suggested I reach out" Email 5: "Free resource: [Industry] benchmark report" Email 6: "Let's cut to the chase: 15 min demo?" Email 7: "Should I close your file?" ``` ### Agency/Services Sequence ``` Email 1: "Saw your [recent achievement], impressive work" Email 2: "Case study: [Similar client] results" Email 3: "Quick idea for [their specific challenge]" Email 4: "What [their competitor] is doing differently" Email 5: "No-strings-attached audit of [their thing]" Email 6: "15 minutes to share our approach?" Email 7: "Is this a bad time?" ``` ### Partnership/Referral Sequence ``` Email 1: "[Mutual contact] suggested we connect" Email 2: "Potential win-win for both our audiences" Email 3: "How [similar partner] approach worked" Email 4: "Quick question about your [partnership program]" Email 5: "Is this worth exploring?" ``` ``` ### Best Practices 1. **Always Personalize the First Line**: Reference something specific about them/their company 2. **Keep It Short**: The best cold emails are under 100 words 3. **One Ask, One Email**: Don't bury multiple CTAs 4. **Respect Replies**: If they say no or ask to stop, honor it immediately 5. **Test Continuously**: Always be running A/B tests on some variable 6. **Follow-Up Matters**: 80% of responses come from emails 3-7 ### Common Use Cases **Trigger Phrases**: - "Create a cold email sequence for SaaS prospects" - "Write a 7-email sequence for enterprise sales" - "Generate outbound emails for [industry] decision makers" - "Build a cold email campaign with A/B tests" **Example Request**: > "Create a 7-email cold outreach sequence targeting VPs of Sales at mid-market B2B SaaS companies. Our product is a sales enablement platform that reduces onboarding time. Include A/B subject lines and personalization variables." **Response Approach**: 1. Confirm target audience and value prop 2. Identify key pain points and social proof 3. Build sequence with varying angles 4. Include A/B test recommendations 5. Provide personalization guidance 6. Add metrics and optimization tips Remember: The goal of cold email isn't to make the sale—it's to start a conversation!
Related Skills
tailored-resume-generator
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
style-guide-generator
Generate comprehensive website style guides and design systems from URLs, screenshots, and existing documentation. Use this skill when users ask to create a style guide, design system documentation, brand guidelines document, or design specification from a website, app, or existing materials. This skill produces professional PDF outputs following industry-standard style guide structure.
runbook-generator
Analyze a codebase and generate production-grade operational runbooks with verification steps, rollback paths, escalation guidance, and staleness checks.
react-component-generator
This skill provides automated assistance for react component generator tasks within the Frontend Development domain
qq-email-operator
QQ邮箱操作技能。支持通过 IMAP/SMTP 读取邮件、搜索邮件、回复邮件、发送邮件。凭据通过 pass 安全存储。
outbound-email-strategy
Comprehensive outbound email strategy skill for cold outreach, email sequences, and multi-channel campaigns. Use when writing cold emails, creating outreach sequences, optimizing response rates, designing follow-up cadences, or building outbound campaigns. Covers prospecting, personalization frameworks, sequence design, subject lines, response handling, compliance, email design, HTML email templates, email layout, email marketing, newsletter design, drip campaigns, email subject lines, email headers, and cold email templates for discovery calls and SDR workflows.
mv-generator
MediaClaw 内置的音乐视频端到端生成技能。
invoice-generator-agent
Automatic invoice generation with CRM integration
email-read
Read inbox and sent via Gmail API
email-outreach-run
Automatic email outreach agent run
email-monitor
AI inbox classification + Telegram notification
email-marketing
Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics