email-sequence

coreyhaines31/marketingskills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/coreyhaines31/marketingskills --skill email-sequence
0 commentsdiscussion
summary

Design and optimize multi-email automated flows that nurture relationships and drive conversions.

  • Covers seven sequence types: welcome, lead nurture, re-engagement, onboarding, retention, billing, and campaign emails, each with timing, structure, and key email templates
  • Emphasizes one primary job per email, value-first messaging, and relevance-based segmentation to maximize engagement and conversion
  • Provides subject line patterns, preview text strategy, copy guidelines, and CTA best
skill.md

Email Sequence Design

You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before creating a sequence, understand:

  1. Sequence Type

    • Welcome/onboarding sequence
    • Lead nurture sequence
    • Re-engagement sequence
    • Post-purchase sequence
    • Event-based sequence
    • Educational sequence
    • Sales sequence
  2. Audience Context

    • Who are they?
    • What triggered them into this sequence?
    • What do they already know/believe?
    • What's their current relationship with you?
  3. Goals

    • Primary conversion goal
    • Relationship-building goals
    • Segmentation goals
    • What defines success?

Core Principles

1. One Email, One Job

  • Each email has one primary purpose
  • One main CTA per email
  • Don't try to do everything

2. Value Before Ask

  • Lead with usefulness
  • Build trust through content
  • Earn the right to sell

3. Relevance Over Volume

  • Fewer, better emails win
  • Segment for relevance
  • Quality > frequency

4. Clear Path Forward

  • Every email moves them somewhere
  • Links should do something useful
  • Make next steps obvious

Email Sequence Strategy

Sequence Length

  • Welcome: 3-7 emails
  • Lead nurture: 5-10 emails
  • Onboarding: 5-10 emails
  • Re-engagement: 3-5 emails

Depends on:

  • Sales cycle length
  • Product complexity
  • Relationship stage

Timing/Delays

  • Welcome email: Immediately
  • Early sequence: 1-2 days apart
  • Nurture: 2-4 days apart
  • Long-term: Weekly or bi-weekly

Consider:

  • B2B: Avoid weekends
  • B2C: Test weekends
  • Time zones: Send at local time

Subject Line Strategy

  • Clear > Clever
  • Specific > Vague
  • Benefit or curiosity-driven
  • 40-60 characters ideal
  • Test emoji (they're polarizing)

Patterns that work:

  • Question: "Still struggling with X?"
  • How-to: "How to [achieve outcome] in [timeframe]"
  • Number: "3 ways to [benefit]"
  • Direct: "[First name], your [thing] is ready"
  • Story tease: "The mistake I made with [topic]"

Preview Text

  • Extends the subject line
  • ~90-140 characters
  • Don't repeat subject line
  • Complete the thought or add intrigue

Sequence Types Overview

Welcome Sequence (Post-Signup)

Length: 5-7 emails over 12-14 days Goal: Activate, build trust, convert

Key emails:

  1. Welcome + deliver promised value (immediate)
  2. Quick win (day 1-2)
  3. Story/Why (day 3-4)
  4. Social proof (day 5-6)
  5. Overcome objection (day 7-8)
  6. Core feature highlight (day 9-11)
  7. Conversion (day 12-14)

Lead Nurture Sequence (Pre-Sale)

Length: 6-8 emails over 2-3 weeks Goal: Build trust, demonstrate expertise, convert

Key emails:

  1. Deliver lead magnet + intro (immediate)
  2. Expand on topic (day 2-3)
  3. Problem deep-dive (day 4-5)
  4. Solution framework (day 6-8)
  5. Case study (day 9-11)
  6. Differentiation (day 12-14)
  7. Objection handler (day 15-18)
  8. Direct offer (day 19-21)

Re-Engagement Sequence

Length: 3-4 emails over 2 weeks Trigger: 30-60 days of inactivity Goal: Win back or clean list

Key emails:

  1. Check-in (genuine concern)
  2. Value reminder (what's new)
  3. Incentive (special offer)
  4. Last chance (stay or unsubscribe)

Onboarding Sequence (Product Users)

Length: 5-7 emails over 14 days Goal: Activate, drive to aha moment, upgrade Note: Coordinate with in-app onboarding—email supports, doesn't duplicate

Key emails:

  1. Welcome + first step (immediate)
  2. Getting started help (day 1)
  3. Feature highlight (day 2-3)
  4. Success story (day 4-5)
  5. Check-in (day 7)
  6. Advanced tip (day 10-12)
  7. Upgrade/expand (day 14+)

For detailed templates: See references/sequence-templates.md


Email Types by Category

Onboarding Emails

  • New users series
  • New customers series
  • Key onboarding step reminders
  • New user invites

Retention Emails

  • Upgrade to paid
  • Upgrade to higher plan
  • Ask for review
  • Proactive support offers
  • Product usage reports
  • NPS survey
  • Referral program

Billing Emails

  • Switch to annual
  • Failed payment recovery
  • Cancellation survey
  • Upcoming renewal reminders

Usage Emails

  • Daily/weekly/monthly summaries
  • Key event notifications
  • Milestone celebrations

Win-Back Emails

  • Expired trials
  • Cancelled customers

Campaign Emails

  • Monthly roundup / newsletter
  • Seasonal promotions
  • Product updates
  • Industry news roundup
  • Pricing updates

For detailed email type reference: See references/email-types.md


Email Copy Guidelines

Structure

  1. Hook: First line grabs attention
  2. Context: Why this matters to them
  3. Value: The useful content
  4. CTA: What to do next
  5. Sign-off: Human, warm close

Formatting

  • Short paragraphs (1-3 sentences)
  • White space between sections
  • Bullet points for scanability
  • Bold for emphasis (sparingly)
  • Mobile-first (most read on phone)

Tone

  • Conversational, not formal
  • First-person (I/we) and second-person (you)
  • Active voice
  • Read it out loud—does it sound human?

Length

  • 50-125 words for transactional
  • 150-300 words for educational
  • 300-500 words for story-driven

CTA Guidelines

  • Buttons for primary actions
  • Links for secondary actions
  • One clear primary CTA per email
  • Button text: Action + outcome

For detailed copy, personalization, and testing guidelines: See references/copy-guidelines.md


Output Format

Sequence Overview

Sequence Name: [Name]
Trigger: [What starts the sequence]
Goal: [Primary conversion goal]
Length: [Number of emails]
Timing: [Delay between emails]
Exit Conditions: [When they leave the sequence]

For Each Email

Email [#]: [Name/Purpose]
Send: [Timing]
Subject: [Subject line]
Preview: [Preview text]
Body: [Full copy]
CTA: [Button text] → [Link destination]
Segment/Conditions: [If applicable]

Metrics Plan

What to measure and benchmarks


Task-Specific Questions

  1. What triggers entry to this sequence?
  2. What's the primary goal/conversion action?
  3. What do they already know about you?
  4. What other emails are they receiving?
  5. What's your current email performance?

Tool Integrations

For implementation, see the tools registry. Key email tools:

Tool Best For MCP Guide
Customer.io Behavior-based automation - customer-io.md
Mailchimp SMB email marketing mailchimp.md
Nitrosend AI-native email (sequences via prompts) nitrosend.md
Resend Developer-friendly transactional resend.md
SendGrid Transactional email at scale - sendgrid.md
Kit Creator/newsletter focused - kit.md

Related Skills

  • lead-magnets: For planning lead magnets that feed into nurture sequences
  • churn-prevention: For cancel flows, save offers, and dunning strategy (email supports this)
  • onboarding-cro: For in-app onboarding (email supports this)
  • copywriting: For landing pages emails link to
  • ab-test-setup: For testing email elements
  • popup-cro: For email capture popups
  • revops: For lifecycle stages that trigger email sequences
how to use email-sequence

How to use email-sequence on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add email-sequence
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/coreyhaines31/marketingskills --skill email-sequence

The skills CLI fetches email-sequence from GitHub repository coreyhaines31/marketingskills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/email-sequence

Reload or restart Cursor to activate email-sequence. Access the skill through slash commands (e.g., /email-sequence) or your agent's skill management interface.

Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

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

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate 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

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.869 reviews
  • Chinedu Sethi· Dec 28, 2024

    Keeps context tight: email-sequence is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Ren Liu· Dec 28, 2024

    email-sequence is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Chinedu Desai· Dec 20, 2024

    Useful defaults in email-sequence — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Evelyn Bansal· Dec 12, 2024

    We added email-sequence from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Aditi Kapoor· Dec 8, 2024

    I recommend email-sequence for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Aditi Shah· Dec 4, 2024

    Solid pick for teams standardizing on skills: email-sequence is focused, and the summary matches what you get after install.

  • Kabir Tandon· Nov 23, 2024

    We added email-sequence from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Zara Bansal· Nov 19, 2024

    Registry listing for email-sequence matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Chinedu Brown· Nov 19, 2024

    email-sequence reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Yusuf Khanna· Nov 11, 2024

    Useful defaults in email-sequence — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 69

1 / 7