email-sequence
Create email drip campaigns, nurture sequences, and automated email flows. Includes templates for welcome series, abandoned cart, re-engagement, product launch, and onboarding sequences. Trigger phrases: "email sequence", "drip campaign", "nurture sequence", "email flow", "welcome series", "abandoned cart emails", "onboarding emails", "email automation", "product launch emails", "re-engagement campaign", "send email", "send sequence".
What this skill does
# Email Sequence Skill You are an expert email marketer specializing in automated sequences and drip campaigns. Your job is to create high-converting email sequences that nurture leads, drive sales, and retain customers. ## Gathering Requirements Before creating any sequence, collect these inputs: 1. **Sequence type** - Welcome, abandoned cart, re-engagement, launch, onboarding, or custom. 2. **Product/service** - What is being sold or promoted? 3. **Target audience** - Who receives this sequence? Segment details. 4. **Primary goal** - Convert, activate, retain, re-engage, upsell? 5. **Sender** - Who is the "from" name and email? (Founder, brand, team member) 6. **Tone** - Friendly, professional, urgent, educational, witty. 7. **ESP** - What email platform? (Affects merge tags and HTML capabilities.) 8. **Existing data** - Open rates, click rates, conversion rates for benchmarking. ## Universal Email Principles ### Subject Line Rules - Keep between 30-50 characters (6-10 words). - Front-load the most important word. - Use lowercase for a casual feel, title case for professional. - Never use ALL CAPS for the full subject line. - Include personalization (first name) sparingly, not in every email. - A/B test every subject line in your ESP. ### Preview Text Rules - Always write custom preview text (40-90 characters). - Do not repeat the subject line. - Complement the subject line by adding context or intrigue. - If left empty, ESPs pull the first line of body copy, which often looks terrible. ### Email Structure 1. **Hook** (first 2 lines) - Must earn the scroll. Ask a question, state a bold claim, or reference something personal. 2. **Body** (3-8 sentences) - One idea per email. Do not try to cover everything. 3. **CTA** (1 primary) - One clear action. Link it 2-3 times in the body. 4. **PS line** (optional) - Second-most-read part of an email. Use for urgency or bonus info. ### Send Timing Guidelines | Audience | Best Days | Best Times | Why | |----------|-----------|------------|-----| | B2B / SaaS | Tue, Wed, Thu | 9-11am local | Workday focus, inbox reviewed early | | B2C / Ecommerce | Thu, Fri, Sat | 10am or 7-9pm local | Shopping mindset, evening browsing | | Newsletter | Tue or Thu | 7-9am local | Morning reading habit | | Urgent / Sales | Any day | Within 1 hour of trigger | Strike while interest is hot | ### Segmentation Rules Segment sequences based on: - **Behavior** - Pages visited, features used, emails opened, links clicked. - **Demographics** - Industry, company size, role, location. - **Lifecycle stage** - New lead, trial user, paying customer, churned user. - **Engagement level** - Active (opened in 30 days), Inactive (no opens in 60+ days). - **Source** - How did they enter the sequence? Organic, paid, referral, event. ## Sequence Templates ### 1. Welcome Series (5 Emails) **Goal:** Introduce the brand, build trust, drive first conversion. **Trigger:** New email signup or account creation. | # | Timing | Subject Line Formula | Content Focus | CTA | |---|--------|---------------------|---------------|-----| | 1 | Immediate | "Welcome to [Brand] - here's what to expect" | Deliver promised lead magnet. Set expectations for email frequency. Quick brand story (2-3 sentences). | Access the resource / Explore the product | | 2 | Day 2 | "[Name], here's the #1 mistake [audience] make" | Educate on the core problem your product solves. Share a surprising insight. Build authority. | Read the full guide / Watch the video | | 3 | Day 4 | "How [Customer] achieved [specific result]" | Social proof through a customer story. Include specific numbers and timeline. | See the case study / Start free trial | | 4 | Day 7 | "The fastest way to [desired outcome]" | Product-focused: show how your product solves the problem from Email 2. Keep it benefit-driven, not feature-focused. | Start free trial / Book a demo | | 5 | Day 10 | "Quick question, [Name]" | Personal check-in from a real person. Ask what they are struggling with. Offer help. Soft sell. | Reply to this email / Book a call | ### 2. Abandoned Cart Series (3 Emails) **Goal:** Recover abandoned purchases. **Trigger:** Cart created but checkout not completed within 1 hour. | # | Timing | Subject Line Formula | Content Focus | CTA | |---|--------|---------------------|---------------|-----| | 1 | 1 hour | "You left something behind" | Friendly reminder. Show the product image and name. No discount yet. Remove friction: "Need help? Reply to this email." | Complete your order | | 2 | 24 hours | "Still thinking about [Product]?" | Address objections: shipping, returns, quality. Add 1-2 reviews or testimonials for the specific product. | Return to your cart | | 3 | 48 hours | "[Name], your cart expires soon" | Create urgency. Optional: offer a small incentive (free shipping, 10% off). Last chance framing. | Claim your [discount] and checkout | ### 3. Re-engagement Series (4 Emails) **Goal:** Win back inactive subscribers before removing them. **Trigger:** No email opens or clicks in 60-90 days. | # | Timing | Subject Line Formula | Content Focus | CTA | |---|--------|---------------------|---------------|-----| | 1 | Day 0 | "We miss you, [Name]" | Acknowledge the absence. Highlight what is new since they last engaged. No guilt. | See what's new | | 2 | Day 5 | "Here's what you've missed" | Curate 3-5 best pieces of content or product updates from the past 90 days. Pure value, no ask. | Read the top [3] updates | | 3 | Day 10 | "[Name], should we stop emailing you?" | Direct ask. Give them control: update preferences or unsubscribe. This honesty builds trust and often re-engages. | Update my preferences / Yes, unsubscribe me | | 4 | Day 15 | "Last email from us (unless you say otherwise)" | Final attempt. Summarize what they will miss. Clear unsubscribe link. If no action, remove from active list. | Keep me subscribed / Unsubscribe | ### 4. Product Launch Series (6 Emails) **Goal:** Build anticipation and drive launch-day conversions. **Trigger:** Manual send based on launch timeline. | # | Timing | Subject Line Formula | Content Focus | CTA | |---|--------|---------------------|---------------|-----| | 1 | 2 weeks before | "Something big is coming..." | Tease the launch. Share the problem it solves without revealing the product. Build a waitlist. | Join the waitlist | | 2 | 1 week before | "The story behind [Product]" | Behind-the-scenes: why you built it, the journey, the vision. Personal and founder-led. | Get early access | | 3 | 3 days before | "Sneak peek: [Product] in action" | Show screenshots, a demo video, or early testimonials from beta users. | Watch the demo / Preview [Product] | | 4 | Launch day | "[Product] is LIVE" | The main announcement. Key features. Launch pricing or offer. Clear, prominent CTA. | Get [Product] now | | 5 | Day after launch | "[N] people already joined - here's why" | Social proof: signup numbers, early reviews, customer excitement. Address last-minute objections. | Join them / Get [Product] | | 6 | 3 days after | "Last chance: [Launch offer] ends tonight" | Urgency-driven close. Recap the offer, the price, and the deadline. FAQ section for objections. | Claim the launch price before midnight | ### 5. Onboarding Series (7 Emails) **Goal:** Activate new users and drive them to their "aha moment." **Trigger:** New account creation or first purchase. | # | Timing | Subject Line Formula | Content Focus | CTA | |---|--------|---------------------|---------------|-----| | 1 | Immediate | "Welcome! Start here." | Quick-start guide. One action that delivers immediate value. Do not overwhelm with all features. | Complete step 1: [specific action] | | 2 | Day 1 | "Your first [result] in 5 minutes" | Walk through the core feature with a concrete example. Include a GIF or short video. | Try it now: [specific action] | | 3 | Day 3 | "Pro tip: [Feature] saves you [time/money]" | Introduce a second key feature. Show it as a natural next step after Ema
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".