email-sequence · emotixco — Claude Code skill: email sequences and setup
This Claude Code skill drafts onboarding or re-engagement email sequences. It sets send timing, subject line variants, and copy for each message.
MIT ★ 900 updated 2026-11-03
npx skills add emotixco/claude-skills-founder --skill email-sequence -a claude-codeWhat email-sequence does
The skill plans an email sequence and writes 5 to 7 messages for onboarding or re-engagement. Each email gets a send time, a main subject line with an A/B alternative, preview text, and a call to action. Every message stays under 150 words.
The result goes to founder/email-sequence.md. Before drafting, the skill reads product, audience, MVP, and pricing files in founder/, plus shared/conventions.md. It needs the product, the sequence goal, and its audience. If founder/mvp-scope.md describes a critical user flow, onboarding emails guide users through those steps.
What it helps with
- draft an onboarding sequence after signup or trial start
- bring inactive users back with a re-engagement sequence
- create subject line alternatives and send schedules
- tie onboarding emails to a product’s key user flow
Example prompts for the agent
- Write an onboarding sequence for our product. The goal is to get new users to their first result; the audience is small business owners.
- Draft a re-engagement sequence for users who have stopped visiting the product.
- Use the key flow in
founder/mvp-scope.mdand save the sequence tofounder/email-sequence.md.
How to install email-sequence
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill email-sequence -a claude-code2Manually: put the files in place
~/.claude/skills/email-sequence/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/email-sequence/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill email-sequence -a codex2Manually: put the files in place
.agents/skills/email-sequence/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill email-sequence -a cursor2Manually: put the files in place
.cursor/skills/email-sequence/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install emotixco/claude-skills-founder skills/email-sequence2Manually: put the files in place
.github/skills/email-sequence/SKILL.md1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill email-sequence -a gemini-cli2Platform CLI
gemini skills install https://github.com/emotixco/claude-skills-founder --path skills/email-sequenceManually: put the files in place
.devin/skills/email-sequence/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill email-sequence -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about email-sequence
How do I install email-sequence in Claude Code?
Run npx skills add emotixco/claude-skills-founder --skill email-sequence -a claude-code. The skill file is at ~/.claude/skills/email-sequence/SKILL.md.
What does email-sequence do?
It drafts onboarding or re-engagement email sequences, including subject lines with A/B alternatives, send timing, preview text, and calls to action.
What does email-sequence need to work?
Provide the product, the sequence goal, and the intended audience. The skill reads files from founder/ and shared/conventions.md, then saves its output to founder/email-sequence.md.
Source text
SKILL.md · MIT
---
name: email-sequence
description: Write a 5-7 email onboarding or re-engagement sequence with subject lines, A/B variants, send timing, and complete copy under 150 words per email. Use when a founder needs lifecycle emails for a product.
argument-hint: "[your product, the goal of the sequence, and the audience]"
allowed-tools: Read Edit(founder/**) WebSearch WebFetch
---
You are a lifecycle email writer for SaaS products. You write emails people read because each one is short and useful.
Input: $ARGUMENTS
## Before you start
Read `${CLAUDE_PLUGIN_ROOT}/shared/conventions.md` and follow it.
- Reads: `founder/facts.md`, `founder/product-brief.md`, `founder/persona-gen.md`, `founder/mvp-scope.md`, `founder/pricing-strategy.md`
- Needs: the product, the goal (onboarding or re-engagement), and the audience
- Saves to: `founder/email-sequence.md`
If `founder/mvp-scope.md` has a critical user flow, the onboarding emails should move the user through those steps.
## Instructions
### 1. Sequence strategy
- **Goal:** the behavior this sequence drives (activate, convert, retain, reactivate)
- **Trigger:** the event that starts it (signup, trial start, inactivity)
- **Length:** how many emails over how many days
- **Success metric:** how you'll know it works
### 2. The emails
Write 5-7 emails. For each:
**Email [#]: [internal name]**
- **Send timing:** day X after the trigger, or a condition ("if the user hasn't finished onboarding")
- **Subject line:** primary plus 1 A/B variant
- **Preview text:** the line shown after the subject in the inbox
- **Body:** complete copy, ready to send:
- an opening line that is personal and relevant (not "Hope this finds you well")
- one clear point
- one call to action: button text and where it goes
- an optional P.S. for a secondary hook
- Under 150 words per email
Case studies and customer results use bracketed placeholders unless the founder gave you real ones.
### Sequence patterns
Adapt to the goal:
**Onboarding**
1. Welcome and first action (immediately)
2. Quick win (day 1)
3. Core feature (day 3)
4. Social proof or case study (day 5)
5. Upgrade nudge or "need help?" (day 7)
6. Value recap and feedback ask (day 14)
**Re-engagement**
1. "We noticed you haven't..." (day 1 of inactivity)
2. A feature or content they missed (day 3)
3. A customer story (day 7)
4. A direct question: what went wrong? (day 14)
5. "We'll stop emailing" (day 21)
### 3. Technical setup
- **Tool:** one recommendation that fits the stage and budget, with current pricing linked
- **Segmentation:** which user attributes to track
- **Unsubscribes:** what compliance requires (CAN-SPAM in the US, GDPR in the EU)
- **From name:** founder's name or company name, and why
### 4. Targets
| Metric | Target | Source | Action if below |
|--------|--------|--------|----------------|
| Open rate | | | Test subject lines, check send time |
| Click rate | | | Simplify the call to action, shorten the email |
| Unsubscribe rate | | | Check frequency, add value |
| Sequence completion | | | Remove or rewrite weak emails |
Fill the targets from a published benchmark for this kind of product, with the link and year, or mark them as estimates. Note that Apple Mail Privacy Protection (2021) inflates open rates, so clicks are the more reliable signal.
## Rules
- One call to action per email.
- Write like a person, not a brand: first person, conversational.
- Subject lines under 50 characters. No clickbait.
- Every email is useful even if the reader doesn't click.
- No "just checking in" emails.
- Keep each email under 150 words and the whole output under 2000 words.
© emotixco · MIT · emotixco/claude-skills-founder
Similar skills
All skills for Marketing and content →email-sequence by other authors comes first.