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.
npx skills add https://github.com/rampstackco/claude-skills --skill 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.
landing-page-copy)content-and-copy)brand-voice)analytics-strategy)If the audience is undefined, define it before writing. Generic emails to "everyone" perform worse than targeted ones.
Most email programs run a handful of standard sequence patterns. Each has its own goals, structure, and pitfalls.
Triggered by signup. Goal: get the user to first value.
Typical structure (5 emails over 14 days):
Common failure: Front-loading product features. Users don't care about features yet; they care about getting to value.
Time- or behavior-triggered. Goal: move users from signup to engaged user.
Patterns:
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.
Ongoing. Goal: keep active users engaged.
Patterns:
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.
Triggered by inactivity. Goal: pull a lapsed user back.
Typical structure (3 emails):
Best practice: Honor the unsubscribe. Aggressive win-back damages deliverability. A clean list of engaged subscribers beats a large list of inactive ones.
Triggered by actions: receipts, password resets, notifications, order confirmations, shipping updates.
Best practices:
Highest open rates of any email type. Use sparingly for marketing nudges; over-marketing transactional emails damages trust.
One-off sends. Announcements, launches, news, time-sensitive campaigns.
Best practices:
Regardless of sequence type, every email has the same components.
The deciding factor for whether the email gets opened.
Patterns:
Avoid:
Length: 30 to 50 characters. Mobile clients truncate longer.
The line that appears below or beside the subject in most email clients.
Best practice:
The first line of the email body. The reader is deciding whether to keep reading.
Strong openings:
Weak openings:
The substance.
Length guide:
Structure:
The action the email is asking for.
Best practices:
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.
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.Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current schemas.
Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.
Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".
You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.
Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders.
Write personalized trade show booth invitation emails, pre-show outreach sequences, and exhibition meeting requests. Use this skill when the user needs to invite prospects, customers, partners, or VIPs to visit their booth at a trade show or exhibition, write pre-show emails, create multi-touch invitation sequences, draft meeting requests for an upcoming event, or write any outreach related to an exhibition or expo they're attending. Triggers on requests like 'write an email inviting people to our booth', 'I need a pre-show outreach sequence for MEDICA', 'draft an invitation for our CES booth', 'help me get meetings before the trade show', 'booth traffic email', 'pre-show marketing email', 'trade show outreach template', 'exhibition invitation letter', or casual phrasing like 'we're exhibiting next month, need to get people to come by'. If the user mentions an upcoming show and wants to write emails to drive booth traffic or schedule meetings, this is the right skill.
Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns.
Take rampstackco/email-sequences from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.