Skip to content

rampstackco/claude-skills / skills/email-sequences

email-sequences

Verified

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.

FileKindSize
README.mdmarkdown356 B
SKILL.mdskill md10.2 KB
references/sequence-templates.mdmarkdown8.0 KB
references/subject-line-patterns.mdmarkdown7.4 KB

references/subject-line-patterns.md

View on GitHub
# Subject Line Patterns

Subject lines are the deciding factor for opens. A great email with a weak subject gets archived unread.

These patterns are tools, not formulas. Apply them, then make them sound like the brand.

---

## Universal rules

- **Length:** 30 to 50 characters. Mobile clients truncate longer.
- **No ALL CAPS.** Reads as shouting and triggers spam filters.
- **No excessive punctuation.** "!!!" reads as desperate.
- **Match the body.** A subject that doesn't deliver in the body kills trust.
- **Sentence case** is more readable than Title Case in inboxes.
- **Skip the prefix conventions** ("Newsletter #23"). Subscribers ignore them.

---

## Pattern 1: Specific outcome

Names what the reader gets.

**Examples:**
- "The 5 questions to ask before hiring a designer"
- "Your team's productivity numbers for September"
- "How to cut your invoicing time in half"
- "What changed in your competitor's pricing this month"

**Strengths:** Clear value. Easy to evaluate whether to open.

**When to use:** Newsletters, content emails, value-driven sends.

---

## Pattern 2: Curiosity gap

Opens a loop the email body closes.

**Examples:**
- "The mistake most teams make in week 2"
- "Why your best customers are leaving"
- "The one habit your top performers share"
- "What I wish I'd known before scaling to 50 people"

**Strengths:** High open rates when the gap is genuine.

**Risks:** Becomes click-bait if the body doesn't deliver. Erodes trust over time.

**When to use:** Sparingly. The body must deliver real insight.

---

## Pattern 3: Personal / direct

Speaks as if to a friend.

**Examples:**
- "Quick question, [name]"
- "Saw this and thought of you"
- "Got 5 minutes?"
- "Are you still using [tool]?"

**Strengths:** Feels human. Cuts through marketing-speak.

**Risks:** Used by every spam email. Authentic context required for it to work.

**When to use:** 1:1 sends, personalized cold outreach, founder-to-customer emails.

---

## Pattern 4: Direct / no-mystery

States exactly what the email is about.

**Examples:**
- "Your receipt for order #12345"
- "Password reset link"
- "Invoice for September"
- "Meeting confirmation: Tuesday 2pm"

**Strengths:** High trust. High open rates for transactional content.

**When to use:** Transactional emails. Always be direct.

---

## Pattern 5: Question

Poses the question the reader is asking.

**Examples:**
- "Should you hire a generalist or specialist first?"
- "Is your pricing too cheap?"
- "What's the ROI of customer service?"
- "Are you measuring the wrong KPIs?"

**Strengths:** Aligns with the reader's mental state. Strong for educational content.

**When to use:** Newsletters and educational sequences.

---

## Pattern 6: Number / list

Promises a specific quantity of items.

**Examples:**
- "3 things to do this week to retain customers"
- "7 signs your team is about to burn out"
- "The 4-step checklist for a clean handoff"

**Strengths:** Sets clear expectations. Easy to scan.

**Risks:** Overused. Can read as listicle filler.

**When to use:** When the content genuinely is a list and the count matters.

---

## Pattern 7: Time-bound / urgency

Signals the email is time-sensitive.

**Examples:**
- "Last day: free shipping on your order"
- "Webinar starts in 2 hours"
- "Pricing changes Thursday"

**Strengths:** Drives immediate action.

**Risks:** Overuse trains subscribers to ignore urgency cues. Reserve for genuine deadlines.

**When to use:** Real time-sensitive sends only. Never fake urgency.

---

## Pattern 8: News / update

States what's new.

**Examples:**
- "New: instant export to spreadsheets"
- "Just launched: team mode"
- "Update on the integration you asked for"

**Strengths:** Useful for product update emails.

**When to use:** Real product announcements that the recipient signed up to hear about.

---

## Pattern 9: Personal anecdote / story

Hints at a story.

**Examples:**
- "I almost didn't ship this"
- "What happened when we tried [thing]"
- "The phone call that changed our hiring process"

**Strengths:** Strong for narrative-driven brand newsletters.

**When to use:** When the brand voice supports storytelling.

---

## Pattern 10: Reference to recipient's behavior

Acknowledges what they did.

**Examples:**
- "Saw you tried [feature] - here's what's next"
- "Welcome back. Here's what you missed."
- "You completed week 1. Here's week 2."

**Strengths:** Personalization that actually feels personal.

**When to use:** Behavior-triggered emails. Lifecycle and onboarding sequences.

---

## Subject lines by sequence type

### Welcome / onboarding

```
Email 1: Welcome to [Brand], [name]
Email 2: The first thing to do in [Brand]
Email 3: How [audience] use [Brand] (3 examples)
Email 4: Did this happen for you?
Email 5: 30 days in: where you could be
```

### Lifecycle / activation

```
Trigger: completed milestone
"Nice work hitting [milestone]. Here's what's next."

Trigger: stalled on a step
"Quick question about your setup"
```

### Re-engagement / win-back

```
Email 1: Hey [name], we miss you
Email 2: Here's [specific incentive]
Email 3: Last email - should we say goodbye?
```

### Newsletter

```
Curiosity: "The metric most teams ignore"
Specific: "September wrap: what we shipped, what we learned"
Question: "Should you raise your prices?"
Number: "3 reads from this week"
```

### Transactional

```
"Your order is on the way (#12345)"
"Receipt for your subscription"
"Your password was changed"
"Action required: confirm your email"
```

### Broadcast

```
Launch: "Just shipped: [feature]"
Event: "Live this Thursday: [topic]"
Update: "Our pricing changed today. Here's what it means for you."
```

---

## A/B test ideas

Subject lines are the easiest thing to test. For any meaningful send, generate 2 to 4 variations along these axes:

- **Specific vs. curiosity:** Does the audience prefer to know what they're getting, or to be intrigued?
- **Personal vs. direct:** Does first-person ("I just shipped this") work better than third-person ("Just launched")?
- **Length:** Short (under 30 chars) vs. medium (30 to 50 chars).
- **Punctuation:** Question vs. statement.
- **Personalization:** With name vs. without.

Track open rates and click-through rates. Open alone is incomplete; some subject patterns get opened but discarded.

---

## What to avoid

### "Just checking in"
Empty. Adds no value. Reads as nag.

### "Following up"
Same problem. The reader knows you're following up. Tell them why.

### "Thoughts?"
A request without context. Comes across as lazy.

### "Hi"
Just don't. Even from someone you know.

### Excessive emojis
🎉🚀✨ does not signal value. Often signals spam to filters.

### Re: when it's not actually a reply
Deceptive. Damages trust.

### Personalization gone wrong
"{first_name} wanted to chat" with the variable un-rendered. Test send before broadcast.

---

## Preview text (preheader)

The line that appears next to or below the subject. Often more important than the subject for engagement.

**Best practice:**
- Use it as the subject's continuation
- 50 to 90 characters
- Don't waste it on "View in browser" or boilerplate
- Add the detail the subject didn't fit

**Examples of subject + preview pairs:**

| Subject | Preview |
|---|---|
| "Your week 1 progress" | "3 of 5 steps complete. Here's what's next." |
| "The mistake most teams make" | "(It's not the obvious one)" |
| "Just shipped: team mode" | "Invite up to 50 teammates and assign roles." |

A weak preview wastes prime real estate. A strong preview can save a mediocre subject.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall