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.
7k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
512
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
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.
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.
Draft remaining emails. Each builds on the previous.
Test the sequence. Send to yourself. Read on mobile. Time the gaps.
Set up triggers. Configure in the email service provider.
Measure. Open rate, click rate, completion rate per email. Sequence completion rate.
For a single broadcast
Define the audience. Specific segment, not the whole list.
Define the goal. One thing this email accomplishes.
Draft subject + preview. Generate 5 to 10 variations.
Draft body. Single message, clear CTA.
Test on mobile. Most opens are mobile.
Schedule. Day and time matched to audience behavior.
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:
# 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
references/subject-line-patterns.md - Subject line patterns with examples for each sequence type.
references/sequence-templates.md - Skeleton templates for the 6 sequence types.
How to use it
Copy the folder
Take rampstackco/email-sequences from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
Check the name does not clash
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.