MCPInstall

email-sequence

Designs complete email automation sequences with timing, subject lines, copy, and conditional logic. Supports welcome series, nurture campaigns, re-engagement, abandoned cart, post-purchase, review requests, and custom sequences. Adapts sequence type, cadence, frameworks, and conditional branching to business context. Use when user wants to create an automated email series triggered by subscriber actions or time intervals.

Installs
75
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/agricidaniel/claude-email --skill email-sequence
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads email-sequence automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Email Sequence Designer

Designs complete email automation sequences with strategic timing, persuasive copy, and conditional logic.

Quick Reference

Sequence TypeEmailsDurationBest For
Welcome Series4-614 daysNew subscribers
Nurture6-106-10 weeksEducation, engagement
Re-engagement3-528 daysInactive subscribers
Abandoned Cart33 daysE-commerce recovery
Post-Purchase4-630 daysCustomer experience
Review Request1-21-24 hoursSocial proof
CustomVariableVariableSpecific goals

Execution Protocol

Step 1: Load Context

Read the business profile for context:

  • email-profile.md (project root)

Load reference files for frameworks and benchmarks:

  • references/copy-frameworks.md
  • references/benchmarks.md

Step 2: Gather Sequence Requirements

Ask the user:

  1. Sequence type: welcome, nurture, re-engagement, abandoned-cart, post-purchase, review-request, or custom
  2. If custom: goal, trigger event, desired email count, preferred cadence, tone

Confirm business context from profile:

  • Industry
  • Target audience
  • Brand voice
  • Primary offer/product

Step 3: Design Sequence Architecture

Based on sequence type, define:

  • Total number of emails
  • Timing between emails
  • Framework assignment per email
  • Conditional logic rules
  • KPI targets

Step 4: Generate Each Email

For each email in sequence, create:

  1. Position and timing: Email X, Day Y or Hours after trigger
  2. Subject lines: 3 variants with scores (60-100)
  3. Preheader text: 30-80 characters
  4. Email body: Full copy following assigned framework
  5. CTA: Button text and link placeholder
  6. Conditional logic: What happens based on engagement

Step 5: Add Implementation Guidance

Include:

  • Platform setup notes
  • A/B test recommendations
  • KPI benchmarks for this sequence type
  • Segment considerations

Sequence Type Templates

1. Welcome Series (4-6 emails, 14 days)

Standard Timeline:

  • Email 1: Immediate (welcome + deliver lead magnet)
  • Email 2: Day 1 (brand story)
  • Email 3: Day 2 (best content/resource)
  • Email 4: Day 4 (social proof)
  • Email 5: Day 7 (soft offer)
  • Email 6: Day 14 (stronger CTA or segmentation)

Framework Assignment:

  • Email 1: BAB (Before-After-Bridge)
  • Email 2: BAB (Before-After-Bridge)
  • Email 3: FAB (Features-Advantages-Benefits)
  • Email 4: 4Ps (Picture-Promise-Prove-Push)
  • Email 5: AIDA (Attention-Interest-Desire-Action)
  • Email 6: PAS (Problem-Agitate-Solution)

KPI Targets:

  • Average open rate: 40-60%
  • Average click rate: 3-8%
  • Conversion rate: 2-5%

2. Nurture Sequence (6-10 emails, 6-10 weeks)

Cadence: 1-2 emails per week

Content Mix:

  • 80% value (education, tips, resources)
  • 20% promotion (offers, CTAs)

Framework Rotation: PAS -> FAB -> BAB -> 4Ps -> AIDA -> repeat

Progressive Profiling: Gather data over time through link clicks, survey questions

KPI Targets:

  • Average open rate: 25-35%
  • Average click rate: 2-5%
  • Conversion rate: 1-3%

3. Re-engagement / Win-Back (3-5 emails, 28 days)

Trigger: 90 days no click engagement (not opens, due to Apple MPP)

Standard Timeline:

  • Email 1: Day 0 (friendly check-in)
  • Email 2: Day 5-7 (value reminder)
  • Email 3: Day 10-14 (incentive offer)
  • Email 4: Day 21 (last chance)
  • Email 5: Day 28 (final goodbye)

Framework Assignment:

  • Email 1: BAB (Before-After-Bridge)
  • Email 2: 4Ps (Picture-Promise-Prove-Push)
  • Email 3: AIDA (Attention-Interest-Desire-Action)
  • Email 4: PAS (Problem-Agitate-Solution)
  • Email 5: Direct

After sequence: Remove non-responders from active list to protect sender reputation

KPI Targets:

  • Average open rate: 15-25%
  • Average click rate: 1-3%
  • Re-engagement rate: 5-10%

4. Abandoned Cart (3 emails, 3 days)

Standard Timeline:

  • Email 1: 1 hour (reminder, no discount)
  • Email 2: 24 hours (address objections, social proof)
  • Email 3: 48-72 hours (incentive offer)

Framework Assignment:

  • Email 1: Direct
  • Email 2: PAS (Problem-Agitate-Solution)
  • Email 3: AIDA (Attention-Interest-Desire-Action)

Show cart items: Include product images, names, prices in email body

Target recovery rate: 5-15%

KPI Targets:

  • Email 1 open rate: 40-50%
  • Email 2 open rate: 30-40%
  • Email 3 open rate: 25-35%
  • Total recovery rate: 10-18%

5. Post-Purchase (4-6 emails, 30 days)

Standard Timeline:

  • Email 1: Immediate (order confirmation)
  • Email 2: Shipped (shipping notification)
  • Email 3: Delivered (delivery confirmation + tips)
  • Email 4: Day 7 (value-add content)
  • Email 5: Day 14 (review request)
  • Email 6: Day 30 (cross-sell/upsell)

Framework Assignment:

  • Email 1: Direct
  • Email 2: Direct
  • Email 3: FAB (Features-Advantages-Benefits)
  • Email 4: BAB (Before-After-Bridge)
  • Email 5: PAS (Problem-Agitate-Solution)
  • Email 6: AIDA (Attention-Interest-Desire-Action)

KPI Targets:

  • Average open rate: 50-70%
  • Average click rate: 5-12%
  • Review request response: 5-15%
  • Cross-sell conversion: 3-8%

6. Review Request (1-2 emails)

Timing varies by business type:

  • Restaurant/food: within 24 hours
  • Salon/spa/service: same day or next day
  • Home services: 24-48 hours
  • Retail (simple products): 1-2 days
  • Shoes/clothing: 1-2 weeks
  • Courses/coaching: 1+ week
  • Medical/dental: 24 hours

Framework: PAS (Problem-Agitate-Solution) - position review as helping others

Include:

  • Direct link to review platform
  • Multiple platform options if applicable
  • Incentive (optional): discount on next purchase

KPI Targets:

  • Open rate: 50-70%
  • Review completion: 10-25%

7. Custom Sequence

For custom sequences, ask user:

  1. Goal: What should this sequence accomplish?
  2. Trigger event: What starts this sequence?
  3. Email count: How many emails?
  4. Cadence: How often should emails send?
  5. Tone: Formal, casual, urgent, educational?

Design sequence architecture based on responses.

Conditional Logic Rules

Apply these rules to every sequence:

Engagement-Based Branching

If opened previous email but didn't click:

  • Emphasize CTA more strongly
  • Add social proof elements
  • Simplify the ask

If clicked previous email:

  • Move faster in sequence
  • Skip reminder emails
  • Advance to stronger offer

If no engagement on 2+ consecutive emails:

  • Slow down cadence
  • Change subject line approach
  • Test different framework

If unsubscribed:

  • Stop sequence immediately
  • Remove from all active lists

Time-Based Branching

If cart value is high (e.g., over $200):

  • Extend abandoned cart sequence
  • Add personal outreach email

If first purchase:

  • Trigger post-purchase sequence
  • Add to VIP nurture track

If repeat customer:

  • Skip welcome emails
  • Go straight to loyalty sequence

Output Format Template

## Email Sequence: [Sequence Type]

**Business**: [from email-profile.md]
**Industry**: [from profile]
**Trigger**: [what starts this sequence]
**Total Emails**: X
**Duration**: X days/weeks
**Goal**: [primary objective]

### Sequence Timeline

Day 0 -> Email 1 (immediate)
Day 1 -> Email 2
Day 4 -> Email 3
Day 7 -> Email 4
[visual timeline]

---

### Email 1: [Descriptive Title] (Day 0 / Immediate)

**Purpose**: [what this email accomplishes]

**Subject Lines:**
| # | Subject | Score | Reason |
|---|---------|-------|--------|
| 1 | [subject line] | 85 | [why this scores high] |
| 2 | [subject line] | 80 | [why this scores high] |
| 3 | [subject line] | 78 | [why this scores high] |

**Preheader**: [30-80 character preview text]

**Framework**: [PAS/AIDA/BAB/FAB/4Ps/Direct]

**Body:**

[Full email copy with proper formatting, following the selected framework structure]

**CTA**: [Button text] -> [link placeholder or description]

**Conditional Logic:**
- **If opened**: Proceed to Email 2 at scheduled time
- **If not opened**: Wait 24h, resend with subject line variant #2
- **If clicked CTA**: [action - skip email, advance sequence, tag subscriber]
- **If no engagement**: [fallback action]

**A/B Test Recommendation**: [specific element to test for this email]

---

[Repeat full structure for each email in sequence]

---

### Implementation Notes

**Platform Setup:**
- [Automation trigger setup instructions]
- [Segmentation requirements]
- [Tag/field requirements]

**Recommended A/B Tests:**
1. [Test for Email 1]
2. [Test for Email 3]
3. [Overall sequence test]

**KPI Targets:**
| Metric | Target | Industry Benchmark |
|--------|--------|-------------------|
| Average Open Rate | X% | X% |
| Average Click Rate | X% | X% |
| Conversion Rate | X% | X% |
| Unsubscribe Rate | <0.5% | <0.5% |

**Monitoring:**
- Check performance after 50 subscribers complete sequence
- Adjust timing if open rates drop >20% between emails
- Test new subject lines if Email 1 opens <30%

**Segment Considerations:**
- [How to adapt for different audience segments]
- [Mobile vs desktop considerations]
- [Geographic/timezone notes if applicable]

Quality Checklist

Before delivering sequence, verify:

  • Each email has 3 subject line variants
  • Preheaders are 30-80 characters
  • Each email follows assigned framework structure
  • CTAs are clear and actionable
  • Conditional logic is defined for each email
  • Timing makes sense for business type
  • KPI targets are realistic
  • A/B test recommendations are specific
  • Implementation notes include platform setup

Framework Quick Reference

Load ../../references/copy-frameworks.md for detailed structures:

  • PAS: Problem -> Agitate -> Solution
  • AIDA: Attention -> Interest -> Desire -> Action
  • BAB: Before -> After -> Bridge
  • FAB: Features -> Advantages -> Benefits
  • 4Ps: Picture -> Promise -> Prove -> Push
  • Direct: Straightforward, no persuasion layer (transactional emails)

Notes

  • Always adapt sequence length and cadence to business context
  • B2B sequences should be longer (nurture over 8-12 weeks)
  • E-commerce can be more aggressive (faster cadence)
  • Service businesses benefit from educational content
  • Always include easy unsubscribe option
  • Test sequences with small segment before full deployment
  • Monitor sender reputation metrics (bounce rate, complaint rate)
  • Apple Mail Privacy Protection makes open tracking unreliable - focus on clicks
  • Use sunset policies: remove non-engaged subscribers after 6-12 months

Integration with Other Skills

  • Use /email audit to verify domain deliverability before launching sequences
  • Use /email write for individual email drafts or rewrites
  • Use /email review to score and optimize each email in the sequence
  • Use /email plan to align sequences with overall marketing strategy

FAQ

What does the email-sequence skill do?

Designs complete email automation sequences with timing, subject lines, copy, and conditional logic. Supports welcome series, nurture campaigns, re-engagement, abandoned cart, post-purchase, review requests, and custom sequences. Adapts sequence type, cadence, frameworks, and conditional branching to business context. Use when user wants to create an automated email series triggered by subscriber actions or time intervals.

How do I install email-sequence?

Run npx skills add https://github.com/agricidaniel/claude-email --skill email-sequence in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/email-sequence/ (personal) or .claude/skills/email-sequence/ (project).

Which AI agents can use email-sequence?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is email-sequence safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains email-sequence?

It is published by agricidaniel in agricidaniel/claude-email. It has 75 recorded installs.

More from agricidaniel/claude-email

View all →

email-check

agricidaniel/claude-email

Open the skill to read its SKILL.md instructions.

email

agricidaniel/claude-email

Open the skill to read its SKILL.md instructions.

email-audit

agricidaniel/claude-email

Open the skill to read its SKILL.md instructions.

email-review

agricidaniel/claude-email

Open the skill to read its SKILL.md instructions.

email-write

agricidaniel/claude-email

Open the skill to read its SKILL.md instructions.

email-plan

agricidaniel/claude-email

Open the skill to read its SKILL.md instructions.

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。