New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Create or optimize an email sequence, drip campaign

Email Sequence Design

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

Email Sequence Design cover

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails,"…

---
name: "email-sequence"
description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
license: MIT
metadata:
  version: 1.0.0
  author: Alireza Rezvani
  category: marketing
  updated: 2026-03-06
---

# 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:**

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add alirezarezvani/claude-skills --skill email-sequence -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \ | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/marketing-skill/skills/email-sequence
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/93027b0f7f6f53796af7/email-sequence.zip" -OutFile "$env:TEMP\email-sequence.zip"; Expand-Archive "$env:TEMP\email-sequence.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md5.8 KB
  • references/1 file · 4.7 KB
  • scripts/1 file · 13.4 KB
Read the files here
alirezarezvani/19392f73 files
SKILL.md
Show the full text146 lines

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 .claude/product-marketing-context.md exists, 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

→ See references/email-sequence-playbook.md for details

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


Tools

Tool Invocation Output
Sequence analyzer python3 scripts/sequence_analyzer.py --file sequence.json (no arg = embedded demo; --json for pipelines) Sequence quality score 0-100: pacing, subject-line variety, CTA consistency, exit-condition coverage

Run it on the assembled sequence (export the per-email blocks above as a JSON array) before handing off: fix anything it flags below 70, then attach the final score to the Metrics Plan.


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

Key email tools:

Tool Best For MCP
Customer.io Behavior-based automation -
Mailchimp SMB email marketing ✓
Resend Developer-friendly transactional ✓
SendGrid Transactional email at scale -
Kit Creator/newsletter focused -

  • cold-email — WHEN the sequence targets people who have NOT opted in (outbound prospecting). NOT for warm leads or subscribers who have expressed interest.
  • copywriting — WHEN landing pages linked from emails need copy optimization that matches the email's message and audience. NOT for the email copy itself.
  • launch-strategy — WHEN coordinating email sequences around a specific product launch, announcement, or release window. NOT for evergreen nurture or onboarding sequences.
  • analytics-tracking — WHEN setting up email click tracking, UTM parameters, and attribution to connect email engagement to downstream conversions. NOT for writing or designing the sequence.
  • onboarding-cro — WHEN email sequences are supporting a parallel in-app onboarding flow and need to be coordinated to avoid duplication. NOT as a replacement for in-app onboarding experience.

Communication

Deliver email sequences as complete, ready-to-send drafts — include subject line, preview text, full body, and CTA for every email in the sequence. Always specify the trigger condition and send timing. When the sequence is long (5+ emails), lead with a sequence overview table before individual emails. Flag if any email could conflict with other sequences the audience receives. Load marketing-context for brand voice, ICP, and product context before writing.


Proactive Triggers

  • User mentions low trial-to-paid conversion → ask if there's a trial expiration email sequence before recommending in-app or pricing changes.
  • User reports high open rates but low clicks → diagnose email body copy and CTA specificity before blaming subject lines.
  • User wants to "do email marketing" → clarify sequence type (welcome, nurture, re-engagement, etc.) before writing anything.
  • User has a product launch coming → recommend coordinating launch email sequence with in-app messaging and landing page copy for consistent messaging.
  • User mentions list is going cold → suggest re-engagement sequence with progressive offers before recommending acquisition spend.

Output Artifacts

Artifact Description
Sequence Architecture Doc Trigger, goal, length, timing, exit conditions, and branching logic for the full sequence
Complete Email Drafts Subject line, preview text, full body, and CTA for every email in the sequence
Metrics Benchmarks Open rate, click rate, and conversion rate targets per email type and sequence goal
Segmentation Rules Audience entry/exit conditions, behavioral branching, and suppression lists
Subject Line Variations 3 subject line alternatives per email for A/B testing
1---
2name: "email-sequence"
3description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
4license: MIT
5metadata:
6 version: 1.0.0
7 author: Alireza Rezvani
8 category: marketing
9 updated: 2026-03-06
10---
11 
12# Email Sequence Design
13 
14You 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.
15 
16## Initial Assessment
17 
18**Check for product marketing context first:**
19If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
20 
21Before creating a sequence, understand:
22 
231. **Sequence Type**
24 - Welcome/onboarding sequence
25 - Lead nurture sequence
26 - Re-engagement sequence
27 - Post-purchase sequence
28 - Event-based sequence
29 - Educational sequence
30 - Sales sequence
31 
322. **Audience Context**
33 - Who are they?
34 - What triggered them into this sequence?
35 - What do they already know/believe?
36 - What's their current relationship with you?
37 
383. **Goals**
39 - Primary conversion goal
40 - Relationship-building goals
41 - Segmentation goals
42 - What defines success?
43 
44---
45 
46## Core Principles
47→ See references/email-sequence-playbook.md for details
48 
49## Output Format
50 
51### Sequence Overview
52```
53Sequence Name: [Name]
54Trigger: [What starts the sequence]
55Goal: [Primary conversion goal]
56Length: [Number of emails]
57Timing: [Delay between emails]
58Exit Conditions: [When they leave the sequence]
59```
60 
61### For Each Email
62```
63Email [#]: [Name/Purpose]
64Send: [Timing]
65Subject: [Subject line]
66Preview: [Preview text]
67Body: [Full copy]
68CTA: [Button text] → [Link destination]
69Segment/Conditions: [If applicable]
70```
71 
72### Metrics Plan
73What to measure and benchmarks
74 
75---
76 
77## Tools
78 
79| Tool | Invocation | Output |
80|---|---|---|
81| Sequence analyzer | `python3 scripts/sequence_analyzer.py --file sequence.json` (no arg = embedded demo; `--json` for pipelines) | Sequence quality score 0-100: pacing, subject-line variety, CTA consistency, exit-condition coverage |
82 
83Run it on the assembled sequence (export the per-email blocks above as a JSON array) before handing off: fix anything it flags below 70, then attach the final score to the Metrics Plan.
84 
85---
86 
87## Task-Specific Questions
88 
891. What triggers entry to this sequence?
902. What's the primary goal/conversion action?
913. What do they already know about you?
924. What other emails are they receiving?
935. What's your current email performance?
94 
95---
96 
97## Tool Integrations
98 
99Key email tools:
100 
101| Tool | Best For | MCP |
102|------|----------|:---:|
103| **Customer.io** | Behavior-based automation | - |
104| **Mailchimp** | SMB email marketing | ✓ |
105| **Resend** | Developer-friendly transactional | ✓ |
106| **SendGrid** | Transactional email at scale | - |
107| **Kit** | Creator/newsletter focused | - |
108 
109---
110 
111## Related Skills
112 
113- **cold-email** — WHEN the sequence targets people who have NOT opted in (outbound prospecting). NOT for warm leads or subscribers who have expressed interest.
114- **copywriting** — WHEN landing pages linked from emails need copy optimization that matches the email's message and audience. NOT for the email copy itself.
115- **launch-strategy** — WHEN coordinating email sequences around a specific product launch, announcement, or release window. NOT for evergreen nurture or onboarding sequences.
116- **analytics-tracking** — WHEN setting up email click tracking, UTM parameters, and attribution to connect email engagement to downstream conversions. NOT for writing or designing the sequence.
117- **onboarding-cro** — WHEN email sequences are supporting a parallel in-app onboarding flow and need to be coordinated to avoid duplication. NOT as a replacement for in-app onboarding experience.
118 
119---
120 
121## Communication
122 
123Deliver email sequences as complete, ready-to-send drafts — include subject line, preview text, full body, and CTA for every email in the sequence. Always specify the trigger condition and send timing. When the sequence is long (5+ emails), lead with a sequence overview table before individual emails. Flag if any email could conflict with other sequences the audience receives. Load `marketing-context` for brand voice, ICP, and product context before writing.
124 
125---
126 
127## Proactive Triggers
128 
129- User mentions low trial-to-paid conversion → ask if there's a trial expiration email sequence before recommending in-app or pricing changes.
130- User reports high open rates but low clicks → diagnose email body copy and CTA specificity before blaming subject lines.
131- User wants to "do email marketing" → clarify sequence type (welcome, nurture, re-engagement, etc.) before writing anything.
132- User has a product launch coming → recommend coordinating launch email sequence with in-app messaging and landing page copy for consistent messaging.
133- User mentions list is going cold → suggest re-engagement sequence with progressive offers before recommending acquisition spend.
134 
135---
136 
137## Output Artifacts
138 
139| Artifact | Description |
140|----------|-------------|
141| Sequence Architecture Doc | Trigger, goal, length, timing, exit conditions, and branching logic for the full sequence |
142| Complete Email Drafts | Subject line, preview text, full body, and CTA for every email in the sequence |
143| Metrics Benchmarks | Open rate, click rate, and conversion rate targets per email type and sequence goal |
144| Segmentation Rules | Audience entry/exit conditions, behavioral branching, and suppression lists |
145| Subject Line Variations | 3 subject line alternatives per email for A/B testing |
146 
View all files on GitHub →

Details

Updated
Aug 30, 2026
License
MIT
Stars on the repo
★ 26,349
Checked
Source
alirezarezvani/claude-skills ↗
Creator
alirezarezvani · 363 listings
View creator

Similar skills

See all →
SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillSays 'newsletter', 'email newsletter', 'weekly digest'Newsletter: Writing email newsletter edition...cwinvestments/memstack · by cwinvestmentsUse this skill when the user says 'newsletter', 'email newsletter', 'weekly digest', 'subscriber growth', 'open rates', or needs subject lines, content structure, sponsorship placement, and growth tactics for email newsletters. Do NOT use for lead magnets or content pipelines.★ 423 GitHub starsSkillWrite a signal-based cold outreach email that earns a replySignal-Based Cold Email (2026 benchmarks)kami-community/kami · by kami-communityWrite a signal-based cold outreach email that earns a reply. Use when drafting outbound/SDR email to a prospect with a known recent signal (funding, hiring, exec hire, launch, community post).★ 64 GitHub starsSkillHostinger Reach API for contact management, segmentationHostinger Reach (Email Marketing)hostinger/hostinger-agent-skills · by hostingerHostinger Reach (Email Marketing) API for contact management, segmentation, contact groups, and profile management. Use when creating or listing contacts, managing contact segments or groups, filtering contacts by subscription status, or working with email marketing profiles.★ 23 GitHub starsMCPExpert email marketing strategist for CRM-driven campaignsmsitarzewski/agency-agents · by msitarzewskiExpert email marketing strategist for CRM-driven campaigns, lifecycle automation, segmentation architecture, and deliverability. Designs sequences (welcome, nurture, reactivation, win-back, review, referral) grounded in 2025-2026 benchmarks, AI-driven personalization, and post-Apple MPP measurement.★ 154k GitHub starsSkillWrite B2B cold emails and follow-up sequences that getCold Email Writingcoreyhaines31/marketingskills · by coreyhaines31Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.★ 51.1k GitHub stars

More from alirezarezvani

SkillResume a paused experiment/ar:ar-resume — Resume Experimentalirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub starsSkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboardalirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillStart an autonomous experiment loop with user-selected/ar:loop — Autonomous Experiment Loopalirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub starsSkillRun a single experiment iteration/ar:run — Single Experiment Iterationalirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub starsSkillSet up a new autoresearch experiment interactively/ar:setup — Create New Experimentalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub starsSkill/cs:boardroom <brief/cs:boardroom — Multi-Role Boardroom Deliberationalirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars