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 Sequences

by rampstackco in rampstackco/claude-skills

Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails.

MITAuto-check passedMarketing & SEO

Install Email Sequences

skills CLI
$ npx skills add rampstackco/claude-skills --skill email-sequences -a claude-code

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

GitHub CLI
$ gh skill install rampstackco/claude-skills email-sequences --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/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/email-sequences .claude/skills/email-sequences && 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-sequences
GitHub stars
935
Token cost
~2.6k tokens
SKILL.md length
1,284 words
Files
4 (incl. references)
Skills in repo
103
Repo updated
First seen
Licence
MIT

At a glance

Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails.

  • Works in 11 steps: Welcome / onboarding → Lifecycle / activation → Retention / engagement → …
  • The user wants to write email copy
  • SKILL.md covers When to use, When NOT to use, Required inputs and The framework: 6 sequence types, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Email Sequences is an agent skill from rampstackco/claude-skills. Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails. Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip, or set up lifecycle email campaigns. Triggers on email sequence, drip campaign, onboarding email, lifecycle email, welcome email, transactional email, newsletter, email broadcast, launch email, announcement email, nurture…

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `README.md`, `references/sequence-templates.md` and `references/subject-line-patterns.md`).

It sits in Marketing & SEO, covering Email marketing and Transactional email. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.

When your agent uses it

  • The user wants to write email copy
  • Plan an email sequence
  • Design an onboarding drip
  • Set up lifecycle email campaigns

Example prompts

  • “/email-sequences”

Workflow steps

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

  1. Welcome / onboarding
  2. Lifecycle / activation
  3. Retention / engagement
  4. Re-engagement / win-back
  5. Transactional
  6. Broadcast
  7. Subject line
  8. Preview text (preheader)
  9. Opening
  10. Body
  11. CTA

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    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 Sequences loads about 2.6k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 170 tokens; SKILL.md has 1,284 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~170
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.5k

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 rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 1,284 words, ~2,608 tokens.

Download SKILL.mdSave it as .claude/skills/email-sequences/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
email-sequences
description
Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails. Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip, or set up lifecycle email campaigns. Triggers on email sequence, drip campaign, onboarding email, lifecycle email, welcome email, transactional email, newsletter, email broadcast, launch email, announcement email, nurture sequence, abandoned cart, re-engagement, win-back. Also triggers when planning email automation flows or writing email subject lines for campaigns.
category
content
catalog_summary
Onboarding flows, lifecycle campaigns, transactional copy
display_order
5

Email Sequences

Plan and write email campaigns. Sequences (multi-message flows triggered by events) and broadcasts (one-off sends). Stack-agnostic. Works with any email service provider.

When to use

  • Writing welcome and onboarding email sequences
  • Planning lifecycle campaigns (activation, retention, win-back)
  • Writing transactional emails (receipts, password resets, notifications)
  • Newsletter design and writing
  • Abandoned-cart or re-engagement flows
  • Writing a one-off broadcast, launch announcement, or news email
  • Drafting email subject lines and preview text for any send

When NOT to use

  • Landing pages and conversion pages (use landing-page-copy)
  • Long-form articles (use content-and-copy)
  • Brand voice work (use brand-voice)
  • Analytics setup for email (use analytics-strategy)

Required inputs

  • The audience (segment or list)
  • The trigger or context (signup, purchase, abandonment, time-based, manual)
  • The goal of the email or sequence
  • Brand voice
  • Any technical constraints (provider, deliverability requirements)

If the audience is undefined, define it before writing. Generic emails to "everyone" perform worse than targeted ones.

The framework: 6 sequence types

Most email programs run a handful of standard sequence patterns. Each has its own goals, structure, and pitfalls.

1. Welcome / onboarding

Triggered by signup. Goal: get the user to first value.

Typical structure (5 emails over 14 days):

  • Email 1 (immediate): Welcome. Confirm they're in. State what happens next. Single CTA: the next obvious action.
  • Email 2 (day 1 or 2): First-value step. Help them get to a quick win or core action.
  • Email 3 (day 4 or 5): Education. Show them something they probably haven't discovered yet.
  • Email 4 (day 8): Social proof. Customer story or use case relevant to their segment.
  • Email 5 (day 14): Outcome reminder. Where they could be in 30/60/90 days. Soft commercial cue.

Common failure: Front-loading product features. Users don't care about features yet; they care about getting to value.

2. Lifecycle / activation

Time- or behavior-triggered. Goal: move users from signup to engaged user.

Patterns:

  • Sent when a user completes a milestone (first project, first invite, first export)
  • Or sent when a user has NOT completed a milestone after N days
  • Each email targets a specific next step

Best practice: Trigger on behavior, not just time. A user who has done 3 onboarding steps doesn't need an email telling them to get started.

3. Retention / engagement

Ongoing. Goal: keep active users engaged.

Patterns:

  • Newsletter (weekly or monthly)
  • Product updates
  • Tips and tutorials
  • Customer-only content (community, behind-the-scenes)

Cadence rule: Frequency that earns the read, not frequency that fills the calendar. Weekly newsletter that is genuinely useful beats daily newsletter that gets archived.

4. Re-engagement / win-back

Triggered by inactivity. Goal: pull a lapsed user back.

Typical structure (3 emails):

  • Email 1: "We miss you" framing or value reminder. What's new since they were last active.
  • Email 2: Specific incentive (discount, feature unlock, content offer).
  • Email 3: "Last call" or list-cleaning email. "We'll stop emailing you unless you click this."

Best practice: Honor the unsubscribe. Aggressive win-back damages deliverability. A clean list of engaged subscribers beats a large list of inactive ones.

5. Transactional

Triggered by actions: receipts, password resets, notifications, order confirmations, shipping updates.

Best practices:

  • Confirm the action that triggered the email at the top
  • Include all relevant detail without padding
  • Use plain language ("Your order shipped" not "Your shipment notification")
  • One primary CTA (track package, view receipt, view account)
  • Subject line states the action ("Your receipt for order #12345")

Highest open rates of any email type. Use sparingly for marketing nudges; over-marketing transactional emails damages trust.

6. Broadcast

One-off sends. Announcements, launches, news, time-sensitive campaigns.

Best practices:

  • Subject line earns the open
  • Single clear message per send
  • Specific audience targeting (do not blast the entire list for narrow announcements)
  • Clear CTA in the first screen-height
  • Mobile-optimized (most opens are mobile)

The 5 components of every email

Regardless of sequence type, every email has the same components.

1. Subject line

The deciding factor for whether the email gets opened.

Patterns:

  • Specific ("Your week 1 progress: 3 of 5 steps done")
  • Curiosity ("The mistake most teams make in week 2")
  • Direct ("Your invoice #12345")
  • Personal ("Quick question, [name]")
  • Urgency ("Last day for the team plan discount") - use sparingly

Avoid:

  • ALL CAPS
  • Excessive punctuation (!!!)
  • Click-bait that doesn't deliver
  • Generic ("Newsletter #23")

Length: 30 to 50 characters. Mobile clients truncate longer.

2. Preview text (preheader)

The line that appears below or beside the subject in most email clients.

Best practice:

  • Treat as the subject's wingman
  • Add what the subject line couldn't fit
  • Avoid wasting it on "View this email in browser"
  • 50 to 90 characters
Show full SKILL.md (544 more words)Show less
3. Opening

The first line of the email body. The reader is deciding whether to keep reading.

Strong openings:

  • Reference the trigger ("You signed up yesterday for...")
  • Get to the point ("Here's what changed this week...")
  • Personal ("Saw your team just hit milestone X. Nice work.")

Weak openings:

  • "I hope this email finds you well."
  • "Welcome to our amazing platform."
  • Long throat-clearing before the actual content
4. Body

The substance.

Length guide:

  • Welcome and transactional: under 100 words
  • Lifecycle and activation: 100 to 250 words
  • Newsletter: 200 to 800 words depending on format
  • Sales sequences: 250 to 500 words

Structure:

  • One core message per email (avoid "while we have you...")
  • Short paragraphs (2 to 3 lines)
  • Bullets or lists when content is enumerable
  • Mobile-first formatting
5. CTA

The action the email is asking for.

Best practices:

  • One primary CTA per email (multiple CTAs split attention)
  • Button or clearly-styled link, not buried in prose
  • Action verb + specific outcome ("See your dashboard" not "Click here")
  • Above the fold AND repeated at the end of longer emails
  • Plain text link as a fallback for users who block buttons

Workflow

For a new sequence
  1. Define the trigger. What event starts this sequence? (Signup, purchase, abandonment, manual.)
  2. Define the goal. What does success look like at the end of the sequence?
  3. Map the journey. What does the recipient need to know, do, or feel between trigger and goal?
  4. Outline emails. One purpose per email. Sequence them across appropriate timing.
  5. Draft email 1. Subject, preview, opening, body, CTA.
  6. Draft remaining emails. Each builds on the previous.
  7. Test the sequence. Send to yourself. Read on mobile. Time the gaps.
  8. Set up triggers. Configure in the email service provider.
  9. Measure. Open rate, click rate, completion rate per email. Sequence completion rate.
For a single broadcast
  1. Define the audience. Specific segment, not the whole list.
  2. Define the goal. One thing this email accomplishes.
  3. Draft subject + preview. Generate 5 to 10 variations.
  4. Draft body. Single message, clear CTA.
  5. Test on mobile. Most opens are mobile.
  6. Schedule. Day and time matched to audience behavior.
  7. Measure. Open rate, click rate, downstream conversions.

Failure patterns

  • Sending to "everyone." Generic broadcasts to the full list have lower engagement than targeted segments.
  • Too many CTAs in one email. Splits attention. Pick one.
  • Subject line clickbait that doesn't deliver. Crashes the trust the email program is trying to build.
  • Sequences that ignore behavior. Sending day-3 onboarding email to a user who already activated wastes the touch.
  • Mobile-broken layouts. 60 to 70 percent of opens are on mobile. Test there first.
  • Long pre-text. Burying the message under "I hope this email finds you well" wastes the read.
  • Aggressive win-back. Emailing dormant users 5 times damages deliverability and brand trust.
  • No measurement. Without tracking opens, clicks, and downstream conversion, you can't iterate.
  • Ignoring deliverability. Sender reputation, authentication (SPF, DKIM, DMARC), list hygiene. Skip these and emails go to spam regardless of how good the content is.

Output format

Default output is a markdown document per email or sequence:

markdown
# Sequence: [Name]

**Trigger:** [What starts this sequence]
**Goal:** [Outcome at completion]
**Audience:** [Specific segment]
**Length:** [N emails over X days]

## Email 1 - [Subject working title]

**Send:** [Trigger / Day N]
**Subject:** [text]
**Preview:** [text]

[Body]

**Primary CTA:** [text]
**CTA URL:** [destination]

---

## Email 2 - [Subject working title]

[Same structure]

---

[etc.]

For a single broadcast, just one email block.

Reference files

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

Files

SKILL.md and 3 other files (references) in skills/email-sequences of rampstackco/claude-skills.

  • SKILL.md
  • README.md
  • references/sequence-templates.md
  • references/subject-line-patterns.md

Open the folder on GitHubat commit 482c9bf

Compare with similar skills

Email Sequences 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 Sequences compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Email Sequences this skillrampstackco/claude-skills935—~2.6kAutomated safety check: PassMIT
Email Marketing BibleCosmoBlk/email-marketing-bible324—~6.8kAutomated safety check: PassMIT
Email Quality Auditoraaron-he-zhu/aaron-marketing-skills2.9k2 repos~2.1kAutomated safety check: PassApache-2.0
EmailAgriciDaniel/claude-email128—~2kAutomated safety check: NotesMIT
Afa Emailafadtc/afa-dtc-skills168—~1.8kAutomated safety check: PassCustom licence
Smartlead Spintaxgrowthenginenowoslawski/coldoutboundskills740—~1.8kAutomated 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 Quality Auditor

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "audit an email program" or "is this campaign safe to send"; runs a typed 20-item SEND profile with authentication, consent, opt-out, and claim veto…

    2.9k GitHub starsUsed in 2 repos~2.1k tokens
    Marketing & SEOAuto-check passed

  • Email

    AgriciDaniel/claude-email

    Comprehensive email management and marketing for any business type.

    128 GitHub stars~2k tokensUpdated 4 mo ago
    Marketing & SEOAuto-check: notes

  • Afa Email

    afadtc/afa-dtc-skills

    DTC 品牌全生命周期邮件营销引擎——自动化流设计、Campaign 文案撰写、可交付性诊断、列表健康度管理、BFCM 作战规划。Use when user mentions: 邮件营销, email marketing, 弃单挽回, abandoned cart, 邮件自动化, email flow, 打开率, open rate, 可交付性, deliverability, BFCM邮件…

    168 GitHub stars~1.8k tokensUpdated 9 days ago
    Marketing & SEOAuto-check passed

  • Smartlead Spintax

    growthenginenowoslawski/coldoutboundskills

    Adds Smartlead-compatible spintax to cold email sequences for deliverability.

    740 GitHub stars~1.8k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed

  • Email Marketing

    sanqiufong/slides-from-anything

    A brand product-launch email — masthead with wordmark, hero image block, headline lockup with skewed-italic accent, body copy, primary CTA, and a specifications grid.

    132 GitHub starsUsed in 1 repo~861 tokens
    Marketing & SEOAuto-check passed

More from rampstackco/claude-skills

All 103 skills in this repo

  • After Action Report

    rampstackco/claude-skills

    Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.

    935 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Analytics Strategy

    rampstackco/claude-skills

    Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.

    935 GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check passed

  • Brand Style Guide

    rampstackco/claude-skills

    Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.

    935 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Brand Voice

    rampstackco/claude-skills

    Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.

    935 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Content And Copy

    rampstackco/claude-skills

    Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.

    935 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Content Strategy

    rampstackco/claude-skills

    Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.

    935 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Categories

Questions about Email Sequences

What does Email Sequences do?

Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails. Email Sequences is an agent skill from rampstackco/claude-skills. Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails.

When should I use Email Sequences?

Email Sequences fits situations like: the user wants to write email copy; plan an email sequence; design an onboarding drip; set up lifecycle email campaigns.

How do I install Email Sequences in Claude Code?

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

How do I install Email Sequences in Codex?

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

Can I use Email Sequences 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 rampstackco/claude-skills --skill email-sequences -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-sequences, .gemini/skills/email-sequences, .github/skills/email-sequences and .opencode/skills/email-sequences in your project.

What does Email Sequences need to run?

SKILL.md names no scripts, command-line tools or credentials: Email Sequences is instructions for the agent only.

Does Email Sequences 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 Sequences 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 Sequences use?

Email Sequences 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 Sequences use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.

What are the alternatives to Email Sequences?

Skills that share tags, products or a category with Email Sequences: Email Marketing Bible (CosmoBlk/email-marketing-bible, 324 stars), Email Quality Auditor (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Email (AgriciDaniel/claude-email, 128 stars) and Afa Email (afadtc/afa-dtc-skills, 168 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Sequences?

rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 935 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.

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