Approach and advantage
The bundled sequence analyzer checks supplied drafts and pacing, while the playbook defines the sequence structure.
Design lifecycle email sequences with triggers, timing, exit conditions, copy, and a metrics plan.
Design lifecycle email sequences with triggers, timing, exit conditions, copy, and a metrics plan. The bundled sequence analyzer checks supplied drafts and pacing, while the playbook defines the sequence structure.
The bundled sequence analyzer checks supplied drafts and pacing, while the playbook defines the sequence structure.
Draft a welcome sequence with clear exit conditions; Review post-purchase timing and message overlap; Analyze a re-engagement sequence before manual platform setup.
Audience, entry trigger, goal, approved offer, brand context, existing emails, and unsubscribe rules.
Use a Skill-capable agent with file access. Python 3 is required for the bundled Python helpers; inspect their sample schemas before supplying data.
The listed package is Alireza Rezvani’s version. Mentioned email-platform integrations require separate tools; this package does not send campaigns.
The repository installer copies this complete Skill into your Codex skills directory. Git and the installer’s shell/Python requirements must be available.
git clone https://github.com/alirezarezvani/claude-skills.git
cd claude-skills
git checkout 6d2f02ea077eead1bee5411a31bcc6db5a11a70c
./scripts/codex-install.sh --skill email-sequenceThis is the unchanged source SKILL.md for the reviewed version. Install the complete package to retain referenced scripts, assets, and instructions. Starter prompts below are EcomAgentTools examples.
Source and package files reviewed on October 25, 2026: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.
View the reviewed source · MIT
MIT License Copyright (c) 2025 Alireza Rezvani Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
---
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:**
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 | - |
---
## Related Skills
- **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 |
Starter prompts for the main use cases—copy and use them directly.
Draft a welcome sequence with clear exit conditions Use for: Draft a welcome sequence with clear exit conditions. Prepare: Audience, entry trigger, goal, approved offer, brand context, existing emails, and unsubscribe rules.
Use the installed email-sequence Skill. Task: Draft a welcome sequence with clear exit conditions. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. The listed package is Alireza Rezvani’s version. Mentioned email-platform integrations require separate tools; this package does not send campaigns.[INPUT][CONSTRAINTS]Review post-purchase timing and message overlap Use for: Review post-purchase timing and message overlap. Prepare: Audience, entry trigger, goal, approved offer, brand context, existing emails, and unsubscribe rules.
Use the installed email-sequence Skill. Task: Review post-purchase timing and message overlap. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. The listed package is Alireza Rezvani’s version. Mentioned email-platform integrations require separate tools; this package does not send campaigns.[INPUT][CONSTRAINTS]Analyze a re-engagement sequence before manual platform setup Use for: Analyze a re-engagement sequence before manual platform setup. Prepare: Audience, entry trigger, goal, approved offer, brand context, existing emails, and unsubscribe rules.
Use the installed email-sequence Skill. Task: Analyze a re-engagement sequence before manual platform setup. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. The listed package is Alireza Rezvani’s version. Mentioned email-platform integrations require separate tools; this package does not send campaigns.[INPUT][CONSTRAINTS]The listed package is Alireza Rezvani’s version. Mentioned email-platform integrations require separate tools; this package does not send campaigns.
Source and package files reviewed on October 25, 2026: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.
Use authorized inputs and keep secrets out of prompts. Review customer-facing claims, calculations, code changes, and any proposed external action before applying them.
Design lifecycle email sequences with triggers, timing, exit conditions, copy, and a metrics plan. The bundled sequence analyzer checks supplied drafts and pacing, while the playbook defines the sequence structure.
Choose the method for your agent and install the complete package, not just the displayed SKILL.md. Audience, entry trigger, goal, approved offer, brand context, existing emails, and unsubscribe rules. Start a new agent session and explicitly ask to use email-sequence. Try one use case below with a small sample and review the output.
Draft a welcome sequence with clear exit conditions; Review post-purchase timing and message overlap; Analyze a re-engagement sequence before manual platform setup
The listed package is Alireza Rezvani’s version. Mentioned email-platform integrations require separate tools; this package does not send campaigns.
Source and package files reviewed on October 25, 2026: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.
Source and package files reviewed on October 25, 2026: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.
Source and package files reviewed on October 25, 2026: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.
Content checked:
No reviews yet.