email-sequence
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
Best use case
email-sequence is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
Teams using email-sequence should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/email-sequence/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How email-sequence Compares
| Feature / Agent | email-sequence | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agent for Cold Email Generation
Discover AI agent skills for cold email generation, outreach copy, lead personalization, CRM support, and sales-adjacent messaging workflows.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# Email Sequence Design 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. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before creating a sequence, understand: 1. **Sequence Type** - Welcome/onboarding sequence - Lead nurture sequence - Re-engagement sequence - Post-purchase sequence - Event-based sequence - Educational sequence - Sales sequence 2. **Audience Context** - Who are they? - What triggered them into this sequence? - What do they already know/believe? - What's their current relationship with you? 3. **Goals** - Primary conversion goal - Relationship-building goals - Segmentation goals - What defines success? --- ## Core Principles ### 1. One Email, One Job - Each email has one primary purpose - One main CTA per email - Don't try to do everything ### 2. Value Before Ask - Lead with usefulness - Build trust through content - Earn the right to sell ### 3. Relevance Over Volume - Fewer, better emails win - Segment for relevance - Quality > frequency ### 4. Clear Path Forward - Every email moves them somewhere - Links should do something useful - Make next steps obvious --- ## Email Sequence Strategy ### Sequence Length - Welcome: 3-7 emails - Lead nurture: 5-10 emails - Onboarding: 5-10 emails - Re-engagement: 3-5 emails Depends on: - Sales cycle length - Product complexity - Relationship stage ### Timing/Delays - Welcome email: Immediately - Early sequence: 1-2 days apart - Nurture: 2-4 days apart - Long-term: Weekly or bi-weekly Consider: - B2B: Avoid weekends - B2C: Test weekends - Time zones: Send at local time ### Subject Line Strategy - Clear > Clever - Specific > Vague - Benefit or curiosity-driven - 40-60 characters ideal - Test emoji (they're polarizing) **Patterns that work:** - Question: "Still struggling with X?" - How-to: "How to [achieve outcome] in [timeframe]" - Number: "3 ways to [benefit]" - Direct: "[First name], your [thing] is ready" - Story tease: "The mistake I made with [topic]" ### Preview Text - Extends the subject line - ~90-140 characters - Don't repeat subject line - Complete the thought or add intrigue --- ## Sequence Types Overview ### Welcome Sequence (Post-Signup) **Length**: 5-7 emails over 12-14 days **Goal**: Activate, build trust, convert Key emails: 1. Welcome + deliver promised value (immediate) 2. Quick win (day 1-2) 3. Story/Why (day 3-4) 4. Social proof (day 5-6) 5. Overcome objection (day 7-8) 6. Core feature highlight (day 9-11) 7. Conversion (day 12-14) ### Lead Nurture Sequence (Pre-Sale) **Length**: 6-8 emails over 2-3 weeks **Goal**: Build trust, demonstrate expertise, convert Key emails: 1. Deliver lead magnet + intro (immediate) 2. Expand on topic (day 2-3) 3. Problem deep-dive (day 4-5) 4. Solution framework (day 6-8) 5. Case study (day 9-11) 6. Differentiation (day 12-14) 7. Objection handler (day 15-18) 8. Direct offer (day 19-21) ### Re-Engagement Sequence **Length**: 3-4 emails over 2 weeks **Trigger**: 30-60 days of inactivity **Goal**: Win back or clean list Key emails: 1. Check-in (genuine concern) 2. Value reminder (what's new) 3. Incentive (special offer) 4. Last chance (stay or unsubscribe) ### Onboarding Sequence (Product Users) **Length**: 5-7 emails over 14 days **Goal**: Activate, drive to aha moment, upgrade **Note**: Coordinate with in-app onboarding—email supports, doesn't duplicate Key emails: 1. Welcome + first step (immediate) 2. Getting started help (day 1) 3. Feature highlight (day 2-3) 4. Success story (day 4-5) 5. Check-in (day 7) 6. Advanced tip (day 10-12) 7. Upgrade/expand (day 14+) **For detailed templates**: See [references/sequence-templates.md](references/sequence-templates.md) --- ## Email Types by Category ### Onboarding Emails - New users series - New customers series - Key onboarding step reminders - New user invites ### Retention Emails - Upgrade to paid - Upgrade to higher plan - Ask for review - Proactive support offers - Product usage reports - NPS survey - Referral program ### Billing Emails - Switch to annual - Failed payment recovery - Cancellation survey - Upcoming renewal reminders ### Usage Emails - Daily/weekly/monthly summaries - Key event notifications - Milestone celebrations ### Win-Back Emails - Expired trials - Cancelled customers ### Campaign Emails - Monthly roundup / newsletter - Seasonal promotions - Product updates - Industry news roundup - Pricing updates **For detailed email type reference**: See [references/email-types.md](references/email-types.md) --- ## Email Copy Guidelines ### Structure 1. **Hook**: First line grabs attention 2. **Context**: Why this matters to them 3. **Value**: The useful content 4. **CTA**: What to do next 5. **Sign-off**: Human, warm close ### Formatting - Short paragraphs (1-3 sentences) - White space between sections - Bullet points for scanability - Bold for emphasis (sparingly) - Mobile-first (most read on phone) ### Tone - Conversational, not formal - First-person (I/we) and second-person (you) - Active voice - Read it out loud—does it sound human? ### Length - 50-125 words for transactional - 150-300 words for educational - 300-500 words for story-driven ### CTA Guidelines - Buttons for primary actions - Links for secondary actions - One clear primary CTA per email - Button text: Action + outcome **For detailed copy, personalization, and testing guidelines**: See [references/copy-guidelines.md](references/copy-guidelines.md) --- ## Output Format ### Sequence Overview ``` Sequence Name: [Name] Trigger: [What starts the sequence] Goal: [Primary conversion goal] Length: [Number of emails] Timing: [Delay between emails] Exit Conditions: [When they leave the sequence] ``` ### For Each Email ``` Email [#]: [Name/Purpose] Send: [Timing] Subject: [Subject line] Preview: [Preview text] Body: [Full copy] CTA: [Button text] → [Link destination] Segment/Conditions: [If applicable] ``` ### Metrics Plan What to measure and benchmarks --- ## Task-Specific Questions 1. What triggers entry to this sequence? 2. What's the primary goal/conversion action? 3. What do they already know about you? 4. What other emails are they receiving? 5. What's your current email performance? --- ## Tool Integrations For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email tools: | Tool | Best For | MCP | Guide | |------|----------|:---:|-------| | **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) | | **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) | | **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) | | **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) | | **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) | --- ## Related Skills - **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this) - **onboarding-cro**: For in-app onboarding (email supports this) - **copywriting**: For landing pages emails link to - **ab-test-setup**: For testing email elements - **popup-cro**: For email capture popups - **revops**: For lifecycle stages that trigger email sequences
Related Skills
imap-smtp-email
Read and send email via IMAP/SMTP. Check for new/unread messages, fetch content, search mailboxes, mark as read/unread, and send emails with attachments. Works with any IMAP/SMTP server including Gmail, Outlook, 163.com, vip.163.com, 126.com, vip.126.com, 188.com, and vip.188.com.
email-template-builder
Email Template Builder
cold-email
When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).
youtube-watcher
Fetch and read transcripts from YouTube videos. Use when you need to summarize a video, answer questions about its content, or extract information from it.
youtube-transcript
Fetch and summarize YouTube video transcripts. Use when asked to summarize, transcribe, or extract content from YouTube videos. Handles transcript fetching via residential IP proxy to bypass YouTube's cloud IP blocks.
youtube-auto-captions - YouTube 自动字幕
## 描述
youtube
YouTube Data API integration with managed OAuth. Search videos, manage playlists, access channel data, and interact with comments. Use this skill when users want to interact with YouTube. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
yahoo-finance
Get stock prices, quotes, fundamentals, earnings, options, dividends, and analyst ratings using Yahoo Finance. Uses yfinance library - no API key required.
xurl
A Twitter research and content intelligence skill focused on attracting WordPress and Shopify clients. Use to analyze Twitter profiles, threads, and conversations for: (1) Identifying what small agency founders and eCommerce brands are discussing; (2) Understanding pain points around WordPress performance, Shopify CRO, and development bottlenecks; (3) Extracting high-performing content angles; (4) Turning insights into authority-building posts; (5) Converting Twitter intelligence into business leverage for clear content angles, strong positioning, and qualified inbound leads.
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
xiaohongshu-mcp
Automate Xiaohongshu (RedNote) content operations using a Python client for the xiaohongshu-mcp server. Use for: (1) Publishing image, text, and video content, (2) Searching for notes and trends, (3) Analyzing post details and comments, (4) Managing user profiles and content feeds. Triggers: xiaohongshu automation, rednote content, publish to xiaohongshu, xiaohongshu search, social media management.
twitter-openclaw
Interact with Twitter/X — read tweets, search, post, like, retweet, and manage your timeline.