Fetches cold-email-sequence-generator from onewave-ai/claude-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/cold-email-sequence-generator
Restart Cursor to activate cold-email-sequence-generator. Access via /cold-email-sequence-generator in your agent's command palette.
⚠
Security Notice
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.
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:
Classic Cold Outreach (7 emails, 2 weeks)
Fast-Track (5 emails, 1 week)
Long-Play Nurture (12-14 emails, 4-6 weeks)
Event/Trigger-Based (3-5 emails, event-specific)
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
# 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
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
