
Email Sequence
Design a full multi-email lifecycle sequence with copy, timing, branches, exit rules, and benchmark targets for onboarding or nurture.
Overview
Email Sequence is an agent skill for the Grow phase that designs and drafts multi-email lifecycle flows with timing, branching, benchmarks, and full copy.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill email-sequenceWhat is this skill?
- Supports 8 sequence types including onboarding, lead nurture, re-engagement, launch, win-back, and educational drip
- Delivers full email copy per step with timing, branching logic, and exit conditions
- Includes A/B test suggestions and performance benchmarks aligned to sequence goals
- Maps end-to-end flows with a diagram-friendly structure for ESP implementation
- Gathers goal, audience segmentation, and optional email count before drafting
- 8 sequence types: onboarding, lead nurture, re-engagement, product launch, event follow-up, upgrade or upsell, win-back,
Adoption & trust: 1.5k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know you need onboarding or nurture emails but only have vague ideas—not a timed sequence with branches, exits, and measurable benchmarks.
Who is it for?
Indie SaaS founders building activation onboarding, trial nurture, re-engagement, or launch announcement series with clear goals and segments.
Skip if: One-off transactional emails, deep ESP automation coding, or paid ad creative—those need integration or distribution skills instead.
When should I use this skill?
User runs /email-sequence or asks to create, design, build, or draft an email sequence, drip campaign, nurture flow, or onboarding series.
What do I get? / Deliverables
You get a complete drip campaign blueprint with per-email copy, scheduling logic, A/B suggestions, and a flow you can implement in your ESP.
- Multi-email sequence with full copy and send timing
- Branching logic, exit conditions, A/B ideas, and benchmark notes
- End-to-end flow suitable for a sequence diagram
Recommended Skills
Journey fit
Grow is where solo builders turn activated users into retained customers through structured email programs rather than one-off blasts. Lifecycle subphase matches onboarding drips, nurture, win-back, and upsell flows with behavioral triggers and stage-aware audiences.
How it compares
Use instead of asking the agent for a single welcome email when you need an end-to-end sequence with branching and performance targets.
Common Questions / FAQ
Who is email-sequence for?
Solo builders and small growth teams who own lifecycle email for a product, newsletter, or store and want implementation-ready sequences.
When should I use email-sequence?
Use it in Grow (lifecycle) when building onboarding, nurture, win-back, upsell, or launch drips, or when you ask to design a drip campaign with a flow diagram.
Is email-sequence safe to install?
It generates marketing copy only; avoid pasting live customer PII into prompts and review the Security Audits panel on this Prism page.
SKILL.md
READMESKILL.md - Email Sequence
# Email Sequence > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Design and draft complete email sequences with full copy, timing, branching logic, and performance benchmarks for any lifecycle or campaign use case. ## Trigger User runs `/email-sequence` or asks to create, design, build, or draft an email sequence, drip campaign, nurture flow, or onboarding series. ## Inputs Gather the following from the user. If not provided, ask before proceeding: 1. **Sequence type** — one of: - Onboarding - Lead nurture - Re-engagement - Product launch - Event follow-up - Upgrade/upsell - Win-back - Educational drip 2. **Goal** — what the sequence should achieve (e.g., activate new users, convert leads to customers, reduce churn, drive event attendance, upsell to a higher tier) 3. **Audience** — who receives this sequence, what stage they are at, and any relevant segmentation details (role, industry, behavior triggers, lifecycle stage) 4. **Number of emails** (optional) — if not specified, recommend a count based on the sequence type using the templates in the Sequence Type Templates section below 5. **Timing/cadence preferences** (optional) — desired spacing between emails (e.g., "every 3 days", "weekly", "aggressive first week then taper off") 6. **Brand voice** — if configured in local settings, apply automatically and inform the user. If not configured, ask: "Do you have brand voice guidelines I should follow? If not, I'll use a clear, conversational professional tone." 7. **Additional context** (optional): - Specific offers, discounts, or incentives to include - CTAs or landing pages to link to - Content assets available (blog posts, case studies, videos, guides) - Product features to highlight - Competitor differentiators to reference ## Process ### 1. Sequence Strategy Before drafting any emails, define the overall sequence architecture: - **Narrative arc** — what story does this sequence tell across all emails? What is the emotional and logical progression from first email to last? - **Journey mapping** — map each email to a stage of the buyer or user journey (awareness, consideration, decision, activation, expansion) - **Escalation logic** — how does the intensity, urgency, or value of each email build on the previous one? - **Success definition** — what specific action signals that the sequence has done its job and the recipient should exit? ### 2. Individual Email Design For each email in the sequence, produce: #### Subject Line - Provide 2-3 options per email - Vary approaches: curiosity, benefit-driven, urgency, personalization, question-based - Keep under 50 characters where possible; note preview behavior on mobile #### Preview Text - 40-90 characters that complement (not repeat) the subject line - Should add context or intrigue that increases open likelihood #### Email Purpose - One sentence explaining why this email exists and what it moves the recipient toward #### Body Copy - Full draft ready to use - Clear hierarchy: hook, body, CTA - Short paragraphs (2-3 sentences max) - Scannable formatting with bold key phrases where appropriate - Personalization tokens where relevant (e.g., first name, company name, product used) #### Primary CTA - Button text and destination - One primary CTA per email (secondary CTA only if appropriate for the sequence stage) #### Timing - Days after the trigger event or after the previous email - Note if timing should adjust based on engagement (e.