Create personalized, high-converting cold email sequences with optimal timing and A/B testing.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncold-email-sequence-generatorExecute the skills CLI command in your project's root directory to begin installation:
Fetches cold-email-sequence-generator from onewave-ai/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate cold-email-sequence-generator. Access via /cold-email-sequence-generator in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
78
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
78
stars
Create personalized, high-converting cold email sequences with optimal timing and A/B testing.
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.
Sequence Types:
Personalization Levels:
Key Features:
Email 1: The Introduction
Email 2: The Value Proof
Email 3: The Different Angle
Email 4: The Social Proof
Email 5: The Resource Share
Email 6: The Direct Ask
Email 7: The Breakup
# 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."
**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
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
sports-betting-analyzer
38onewave-ai/claude-skills
Productivitysame repotechnical-writer
9onewave-ai/claude-skills
Productivitysame repoqq-email
9shadowcz007/skills
AI/MLtag: emailbrand-name-generator
23shipshitdev/library
Productivitytag: generatorexcalidraw-diagram-generator
8github/awesome-copilot
Productivitytag: generatordify-dsl-generator
8wwwzhouhui/skills_collection
Productivitytag: generatorReviews
4.6★★★★★64 reviews- OOmar Zhang★★★★★Dec 28, 2024
Useful defaults in cold-email-sequence-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- NNaina Flores★★★★★Dec 24, 2024
I recommend cold-email-sequence-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- MMichael Martinez★★★★★Dec 16, 2024
Useful defaults in cold-email-sequence-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- DDhruvi Jain★★★★★Dec 12, 2024
Useful defaults in cold-email-sequence-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- MMichael Robinson★★★★★Dec 8, 2024
Registry listing for cold-email-sequence-generator matched our evaluation — installs cleanly and behaves as described in the markdown.
- KKofi Abbas★★★★★Nov 27, 2024
Keeps context tight: cold-email-sequence-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.
- LLuis Thomas★★★★★Nov 19, 2024
cold-email-sequence-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.
- OOmar Liu★★★★★Nov 15, 2024
Solid pick for teams standardizing on skills: cold-email-sequence-generator is focused, and the summary matches what you get after install.
- NNaina Anderson★★★★★Nov 7, 2024
cold-email-sequence-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.
- OOshnikdeep★★★★★Nov 3, 2024
cold-email-sequence-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 64
1 / 7Discussion
Comments — not star reviews- No comments yet — start the thread.