New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Email Sequence

by AgriciDaniel in AgriciDaniel/claude-email

Designs complete email automation sequences with timing, subject lines, copy, and conditional logic.

MITAuto-check passedMarketing & SEO

Install Email Sequence

skills CLI
$ npx skills add AgriciDaniel/claude-email --skill email-sequence -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AgriciDaniel/claude-email email-sequence --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-email.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/email-sequence .claude/skills/email-sequence && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
email-sequence
GitHub stars
128
Token cost
~2.8k tokens
SKILL.md length
1,084 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Designs complete email automation sequences with timing, subject lines, copy, and conditional logic.

  • Works in 12 steps: Load Context → Gather Sequence Requirements → Design Sequence Architecture → …
  • User wants to create an automated email series triggered by subscriber actions
  • SKILL.md covers Quick Reference, Execution Protocol, Sequence Type Templates and Conditional Logic Rules, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Email Sequence is an agent skill from AgriciDaniel/claude-email. 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.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Email marketing and Email management. The repository describes itself as: AI-powered email management and marketing skill for Claude Code. Inbox triage, composition, quality review, deliverability audit, automation sequences, and marketing strategy. The licence is MIT.

When your agent uses it

  • User wants to create an automated email series triggered by subscriber actions
  • Tasks that involve Email marketing
  • Tasks that involve Email management

Example prompts

  • “Use the email-sequence skill to design complete email automation sequences with timing, subject lines, copy, and conditional logic”
  • “/email-sequence”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Grep, Glob

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Load Context
  2. Gather Sequence Requirements
  3. Design Sequence Architecture
  4. Generate Each Email
  5. Add Implementation Guidance
  6. Welcome Series (4-6 emails, 14 days)
  7. Nurture Sequence (6-10 emails, 6-10 weeks)
  8. Re-engagement / Win-Back (3-5 emails, 28 days)
  9. Abandoned Cart (3 emails, 3 days)
  10. Post-Purchase (4-6 emails, 30 days)
  11. Review Request (1-2 emails)
  12. Custom Sequence

What it can do on your machine

Read from SKILL.md and the folder at commit 182270a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Email Sequence loads about 2.8k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 1,084 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AgriciDaniel/claude-email at commit 182270a, republished under its MIT licence (© AgriciDaniel). 1,084 words, ~2,843 tokens.

Download SKILL.mdSave it as .claude/skills/email-sequence/SKILL.md (or your agent's skills folder).
name
email-sequence
description
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.
allowed-tools
Read, Write, Grep, Glob
user-invocable
false

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%
Show full SKILL.md (442 more words)Show less
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

© AgriciDaniel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/email-sequence of AgriciDaniel/claude-email.

Open the folder on GitHubat commit 182270a

Compare with similar skills

Email Sequence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Email Sequence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Email Sequence this skillAgriciDaniel/claude-email128—~2.8kAutomated safety check: PassMIT
Email Marketing BibleCosmoBlk/email-marketing-bible324—~6.8kAutomated safety check: PassMIT
Email Automation BuilderAffitor/affiliate-skills698—~2.9kAutomated safety check: PassMIT
Shopify Email Flowsnexscope-ai/eCommerce-Skills1.1k—~461Automated safety check: PassMIT
Abm Outboundsundial-org/awesome-openclaw-skills663—~1.8kAutomated safety check: PassNone
49 HTML Email Template Globalminhnv0807/ai-business-skills608—~2.6kAutomated safety check: PassMIT

Similar skills

  • Email Marketing Bible

    CosmoBlk/email-marketing-bible

    Data-backed email marketing skill for AI agents. An agent skill from CosmoBlk/email-marketing-bible.

    324 GitHub stars~6.8k tokensUpdated today
    Marketing & SEOAuto-check passed

  • Email Automation Builder

    Affitor/affiliate-skills

    Build multi-sequence email automation flows with branching logic.

    698 GitHub stars~2.9k tokensUpdated 22 days ago
    Marketing & SEOAuto-check passed

  • Shopify Email Flows

    nexscope-ai/eCommerce-Skills

    Email automation flows — welcome series, abandoned cart, post-purchase, win-back, browse abandonment

    1.1k GitHub stars~461 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Abm Outbound

    sundial-org/awesome-openclaw-skills

    Multi-channel ABM automation that turns LinkedIn URLs into coordinated outbound campaigns.

    663 GitHub stars~1.8k tokensUpdated 7 mo ago
    Marketing & SEOAuto-check passed

  • 49 HTML Email Template Global

    minhnv0807/ai-business-skills

    A skill your agent uses when responsive HTML email has to render correctly in every client — table-based structure, inline CSS, 600px max width, dark mode handling, quirks for Gmail, Apple Mail…

    608 GitHub stars~2.6k tokensUpdated 25 days ago
    Frontend & DesignAuto-check passed

  • 49 HTML Email Template

    minhnv0807/ai-business-skills

    Dung khi can FILE HTML email chay duoc tren moi email client — cau truc table, CSS inline, be ngang 600px, dark mode, spec rieng cho Gmail, Outlook, Apple Mail va checklist test truoc khi gui.

    608 GitHub stars~2k tokensUpdated 25 days ago
    Frontend & DesignAuto-check passed

More from AgriciDaniel/claude-email

  • Email Plan

    AgriciDaniel/claude-email

    Generate comprehensive email marketing strategy with 90-day implementation roadmap.

    128 GitHub stars~4.3k tokensUpdated 4 mo ago
    Auto-check passed

  • Email Audit

    AgriciDaniel/claude-email

    Audits email domain deliverability setup (SPF, DKIM, DMARC, MX records, blacklists, TLS) and generates health score (0-100) with prioritized fix list.

    128 GitHub stars~3k tokensUpdated 4 mo ago
    Auto-check: notes

  • Email Check

    AgriciDaniel/claude-email

    Intelligent inbox triage that connects to Gmail or Outlook, scores emails by importance (0-100) using sender recognition, urgency keywords, thread depth, time sensitivity, and business relevance…

    128 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed

  • Email Review

    AgriciDaniel/claude-email

    Pre-send email quality review and scoring across 5 dimensions (subject line, copy quality, technical/HTML, deliverability, compliance).

    128 GitHub stars~3.3k tokensUpdated 4 mo ago
    Auto-check: notes

  • Email

    AgriciDaniel/claude-email

    Comprehensive email management and marketing for any business type.

    128 GitHub stars~2k tokensUpdated 4 mo ago
    Auto-check: notes

  • Email Write

    AgriciDaniel/claude-email

    Compose high-converting emails using proven copy frameworks (PAS, AIDA, BAB, FAB, 4Ps).

    128 GitHub stars~2.8k tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Email Sequence

What does Email Sequence do?

Designs complete email automation sequences with timing, subject lines, copy, and conditional logic. Email Sequence is an agent skill from AgriciDaniel/claude-email. Designs complete email automation sequences with timing, subject lines, copy, and conditional logic.

When should I use Email Sequence?

Email Sequence fits situations like: user wants to create an automated email series triggered by subscriber actions; tasks that involve Email marketing; tasks that involve Email management.

How do I install Email Sequence in Claude Code?

Run `npx skills add AgriciDaniel/claude-email --skill email-sequence -a claude-code`. Or copy the skill folder (skills/email-sequence in AgriciDaniel/claude-email) into .claude/skills/email-sequence in your project. Claude Code loads it when a task matches its description.

How do I install Email Sequence in Codex?

Run `npx skills add AgriciDaniel/claude-email --skill email-sequence -a codex`. Or copy the skill folder (skills/email-sequence in AgriciDaniel/claude-email) into .agents/skills/email-sequence in your project. Codex loads it when a task matches its description.

Can I use Email Sequence in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgriciDaniel/claude-email --skill email-sequence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/email-sequence, .gemini/skills/email-sequence, .github/skills/email-sequence and .opencode/skills/email-sequence in your project.

What does Email Sequence need to run?

SKILL.md names no scripts, command-line tools or credentials: Email Sequence is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Grep, Glob.

Does Email Sequence access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Email Sequence safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Email Sequence use?

Email Sequence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Email Sequence use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Email Sequence?

Skills that share tags, products or a category with Email Sequence: Email Marketing Bible (CosmoBlk/email-marketing-bible, 324 stars), Email Automation Builder (Affitor/affiliate-skills, 698 stars), Shopify Email Flows (nexscope-ai/eCommerce-Skills, 1.1k stars) and Abm Outbound (sundial-org/awesome-openclaw-skills, 663 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Sequence?

AgriciDaniel (a GitHub user) maintains it in AgriciDaniel/claude-email, which has 128 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on May 23, 2026.

Source: AgriciDaniel/claude-email on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.