Skip to content
Agentmart
Submit a tool

email-sequences

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

Skill by rampstackco

IndexedMIT★ 992
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/rampstackco-email-sequences

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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.

Use cases: design, writing, marketing, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/email-sequences

What's inside

Skill 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.
License
MIT
Instructions
276 lines in SKILL.md · view on GitHub

Files (4)

  • SKILL.md
  • _claude-frontmatter-extras.yaml · references/
  • sequence-templates.md · references/
  • subject-line-patterns.md · references/

SKILL.md (first lines)

# 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.

From rampstackco/claude-skills, MIT.

More from rampstackco/claude-skills

Signals

Stars
992
Forks
134
Open issues
2
Last commit (this folder)
Sep 15, 2026 (1 month ago)
Last release
May 8, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from rampstackco

Cite this page

email-sequences skill. Agent Mart. https://agentmart.dev/skills/rampstackco-email-sequences (last updated 2026-10-24)