email-sequence
Design and draft multi-email sequences with full copy, timing, branching logic, exit conditions, and performance benchmarks. Use when building onboarding, lead nurture, re-engagement, win-back, or product launch flows, when you need a complete drip campaign with A/B test suggestions, or when mapping a sequence end-to-end with a flow diagram.
What this skill does
# 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.g., "send sooner if they opened but did not click") #### Segment/Condition Notes - Who receives this email vs. who skips it - Any behavioral or attribute-based conditions (e.g., "only send to users who have not completed setup") ### 3. Sequence Logic Define the flow control for the sequence: - **Branching conditions** — alternate paths based on engagement. For example: - "If opened email 2 but did not click CTA, send email 2b (softer re-ask) instead of email 3" - "If clicked CTA in email 1, skip email 2 and go directly to email 3" - **Exit conditions** — when a recipient converts (completes the desired action), remove them from the sequence. Define what "conversion" means for this sequence. - **Re-entry rules** — can someone re-enter the sequence? Under what conditions? (e.g., "if a user churns again 90 days later, re-enter the win-back sequence") - **Suppression rules** — do not send if the recipient is already in another active sequence, has unsubscribed from marketing, or has contacted support in the last 48 hours ### 4. Performance Benchmarks Provide expected benchmarks based on the sequence type so the user can set targets: | Metric | Onboarding | Lead Nurture | Re-engagement | Win-back | |--------|-----------|--------------|---------------|----------| | Open rate | 50-70% | 20-30% | 15-25% | 15-20% | | Click-through rate | 10-20% | 3-7% | 2-5% | 2-4% | | Conversion rate | 15-30% | 2-5% | 3-8% | 1-3% | | Unsubscribe rate | <0.5% | <0.5% | 1-2% | 1-3% | Adjust benchmarks based on industry and audience if the user has provided that context. ## Sequence Type Templates Use these as starting frameworks. Adapt length and content based on the user's goal and audience. **Onboarding (5-7 emails over 14-21 days):** Welcome and set expectations -- Quick win to demonstrate value -- Core feature deep dive -- Advanced feature or integration -- Social proof and community -- Check-in and feedback request -- Upgrade prompt or next steps **Lead Nurture (4-6 emails over 3-4 weeks):** Value-first educational content -- Pain point identification -- Solution positioning with proof -- Social proof and results -- Soft CTA (trial, demo, resource) -- Direct CTA (buy, book, sign up) **Re-engagement (3-4 emails over 10-14 days):** "We miss you" with a compelling reason to return -- Value reminder highlighting what they are missing -- Incentive or exclusive offer -- Last chance with clear deadline **Win-back (3-5 emails over 30 days):** Friendly check-in asking what went wrong -- What is new since they left -- Special offer or incentive to return -- Feedback request (even if they do not come back) -- Final goodbye with door open **Product Launch (4-6 emails over 2-3 weeks):** Teaser or pre-announcement -- Launch announcement with full details -- Feature spotlight or use case -- Social proof and early results -- Limited-time offer or bonus -- Last chance or reminder **Event Follow-up (3-4 emails over 7-10 days):** Thank you with key takeaways or recordings -- Resource roundup from the event -- Related offer or next step -- Feedback survey **Upgrade/Upsell (3-5 emails over 2-3 weeks):** Usage milestone or success celebration -- Feature gap or limitation they are hitting -- Upgrade benefits with proof -- Limited-time incentive -- Direct comparison of plans **Educational Drip (5-8 emails over 4-6 weeks):** Introduction and what they will learn -- Lesson 1: foundational concept -- Lesson 2: intermediate concept -- Lesson 3: advanced concept -- Practical application or exercise -- Resource roundup -- Graduation and next steps ## Tool Integration ### If ~~email marketing is connected (e.g., Klaviyo, Mailchimp, Customer.io) - Reference how to set up the sequence as a flow or automation in the platform - Note any platform-specific features to use (e.g., smart send time, conditional splits, A/B testing) - Map the branching logic to the platform's visual flow builder concepts ### If ~~marketing automation or ~~CRM is connected (e.g., HubSpot, Marketo) - Reference lead scoring data to inform segmentation and exit conditions - Use lifecycle stage data to tailor messaging per segment - Note how to set enrollment triggers based on CRM properties or list membership ### If no tools are connected - Deliver all email content in copy-paste-ready format - Include a setup checklist the user can follow in any email platform: 1. Create the automation or flo
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".