[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AFY2E96G2145QJEWA27T59":3,"skill-same:01M7AFY2E96G2145QJEWA27T59":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7AFY2E96G2145QJEWA27T59","emails",null,"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,\" \"lifecycle emails,\" \"trigger-based emails,\" \"email funnel,\" \"email workflow,\" \"what emails should I send,\" \"welcome series,\" or \"email cadence.\" Use this for any multi-email automated flow. Emails avoid AI tells like 'it's not X, it's Y' reveals, 'no X, no Y, no Z' lists, and fake 'Re:' subject lines. For cold outreach and outbound sequences, see cold-email. For in-app onboarding, see onboarding.","iamwaqargulzar\u002FMarketing-Agent-OS","iamwaqargulzar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96654715?v=4","01M7ACMBN0TACNXY53QYG8KDF6","Waqar Gulzar","01M7ACMBNP5ZX60H8CD3JK0633",8,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Femails\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: emails\ndescription: 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,\" \"lifecycle emails,\" \"trigger-based emails,\" \"email funnel,\" \"email workflow,\" \"what emails should I send,\" \"welcome series,\" or \"email cadence.\" Use this for any multi-email automated flow. Emails avoid AI tells like 'it's not X, it's Y' reveals, 'no X, no Y, no Z' lists, and fake 'Re:' subject lines. For cold outreach and outbound sequences, see cold-email. For in-app onboarding, see onboarding.\nmetadata:\n  version: 2.1.4\n---\n\n# Email Sequence Design\n\nYou 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.\n\n## Reference Routing\n\nLoad the matching reference before drafting or auditing the relevant part of a sequence. Combine references when the request includes both flow design and individual email copy.\n\n| User intent | Load | Covers |\n|---|---|---|\n| Build a welcome, lead nurture, re-engagement, or product onboarding flow | [sequence-templates.md](references\u002Fsequence-templates.md) | Sequence goals, timing, email order, and conversion actions |\n| Identify missing lifecycle emails or audit onboarding, retention, billing, usage, win-back, or campaigns | [email-types.md](references\u002Femail-types.md) | Email purposes, triggers, audiences, and the lifecycle audit checklist |\n| Write or edit individual emails within a sequence; improve CTA, personalization, or segmentation | [copy-guidelines.md](references\u002Fcopy-guidelines.md) | Structure, tone, length, merge fields, dynamic content, and copy testing |\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nCheck its **Learnings** section before drafting: angles, offers, and formats already tested there shouldn't be re-proposed as new ideas, and active lessons apply unless the user says otherwise.\n\nBefore creating a sequence, understand:\n\n1. **Sequence Type**\n   - Welcome\u002Fonboarding sequence\n   - Lead nurture sequence\n   - Re-engagement sequence\n   - Post-purchase sequence\n   - Event-based sequence\n   - Educational sequence\n   - Sales sequence\n\n2. **Audience Context**\n   - Who are they?\n   - What triggered them into this sequence?\n   - What do they already know\u002Fbelieve?\n   - What's their current relationship with you?\n\n3. **Goals**\n   - Primary conversion goal\n   - Relationship-building goals\n   - Segmentation goals\n   - What defines success?\n\n---\n\n## Core Principles\n\n### 1. One Email, One Job\n- Each email has one primary purpose\n- One main CTA per email\n- Don't try to do everything\n\n### 2. Value Before Ask\n- Lead with usefulness\n- Build trust through content\n- Earn the right to sell\n\n### 3. Relevance Over Volume\n- Fewer, better emails win\n- Segment for relevance\n- Quality > frequency\n\n### 4. Clear Path Forward\n- Every email moves them somewhere\n- Links should do something useful\n- Make next steps obvious\n\n---\n\n## Email Sequence Strategy\n\n### Sequence Length\n- Welcome: 3-7 emails\n- Lead nurture: 5-10 emails\n- Onboarding: 5-10 emails\n- Re-engagement: 3-5 emails\n\nDepends on:\n- Sales cycle length\n- Product complexity\n- Relationship stage\n\n### Timing\u002FDelays\n- Welcome email: Immediately\n- Early sequence: 1-2 days apart\n- Nurture: 2-4 days apart\n- Long-term: Weekly or bi-weekly\n\nConsider:\n- B2B: Avoid weekends\n- B2C: Test weekends\n- Time zones: Send at local time\n\n### Subject Line Strategy\n- Clear > Clever\n- Specific > Vague\n- Benefit or curiosity-driven\n- 40-60 characters ideal\n- Test emoji (they're polarizing)\n\n**Patterns that work:**\n- Question: \"Still struggling with X?\"\n- How-to: \"How to [achieve outcome] in [timeframe]\"\n- Number: \"3 ways to [benefit]\"\n- Direct: \"[First name], your [thing] is ready\"\n- Story tease: \"The mistake I made with [topic]\"\n\n### Preview Text\n- Extends the subject line\n- ~90-140 characters\n- Don't repeat subject line\n- Complete the thought or add intrigue\n\n---\n\n## Sequence Types Overview\n\n### Welcome Sequence (Post-Signup)\n**Length**: 5-7 emails over 12-14 days\n**Goal**: Activate, build trust, convert\n\nKey emails:\n1. Welcome + deliver promised value (immediate)\n2. Quick win (day 1-2)\n3. Story\u002FWhy (day 3-4)\n4. Social proof (day 5-6)\n5. Overcome objection (day 7-8)\n6. Core feature highlight (day 9-11)\n7. Conversion (day 12-14)\n\n### Lead Nurture Sequence (Pre-Sale)\n**Length**: 6-8 emails over 2-3 weeks\n**Goal**: Build trust, demonstrate expertise, convert\n\nKey emails:\n1. Deliver lead magnet + intro (immediate)\n2. Expand on topic (day 2-3)\n3. Problem deep-dive (day 4-5)\n4. Solution framework (day 6-8)\n5. Case study (day 9-11)\n6. Differentiation (day 12-14)\n7. Objection handler (day 15-18)\n8. Direct offer (day 19-21)\n\n### Re-Engagement Sequence\n**Length**: 3-4 emails over 2 weeks\n**Trigger**: 30-60 days of inactivity\n**Goal**: Win back or clean list\n\nKey emails:\n1. Check-in (genuine concern)\n2. Value reminder (what's new)\n3. Incentive (special offer)\n4. Last chance (stay or unsubscribe)\n\n### Onboarding Sequence (Product Users)\n**Length**: 5-7 emails over 14 days\n**Goal**: Activate, drive to aha moment, upgrade\n**Note**: Coordinate with in-app onboarding—email supports, doesn't duplicate\n\nKey emails:\n1. Welcome + first step (immediate)\n2. Getting started help (day 1)\n3. Feature highlight (day 2-3)\n4. Success story (day 4-5)\n5. Check-in (day 7)\n6. Advanced tip (day 10-12)\n7. Upgrade\u002Fexpand (day 14+)\n\n**For detailed templates**: See [references\u002Fsequence-templates.md](references\u002Fsequence-templates.md)\n\n---\n\n## Email Types by Category\n\n### Onboarding Emails\n- New users series\n- New customers series\n- Key onboarding step reminders\n- New user invites\n\n### Retention Emails\n- Upgrade to paid\n- Upgrade to higher plan\n- Ask for review\n- Proactive support offers\n- Product usage reports\n- NPS survey\n- Referral program\n\n### Billing Emails\n- Switch to annual\n- Failed payment recovery\n- Cancellation survey\n- Upcoming renewal reminders\n\n### Usage Emails\n- Daily\u002Fweekly\u002Fmonthly summaries\n- Key event notifications\n- Milestone celebrations\n\n### Win-Back Emails\n- Expired trials\n- Cancelled customers\n\n### Campaign Emails\n- Monthly roundup \u002F newsletter\n- Seasonal promotions\n- Product updates\n- Industry news roundup\n- Pricing updates\n\n**For detailed email type reference**: See [references\u002Femail-types.md](references\u002Femail-types.md)\n\n---\n\n## Email Copy Guidelines\n\n### Structure\n1. **Hook**: First line grabs attention\n2. **Context**: Why this matters to them\n3. **Value**: The useful content\n4. **CTA**: What to do next\n5. **Sign-off**: Human, warm close\n\n### Formatting\n- Short paragraphs (1-3 sentences)\n- White space between sections\n- Bullet points for scanability\n- Bold for emphasis (sparingly)\n- Mobile-first (most read on phone)\n\n### Tone\n- Conversational, not formal\n- First-person (I\u002Fwe) and second-person (you)\n- Active voice\n- Read it out loud. Does it sound like a person?\n\n### No AI Tells\n\nSubscribers learn to recognize generated email fast, and they stop reading. Write from the specific thing you want them to know or do.\n\nNever write these:\n- **Contrast reveals**: \"It's not X, it's Y.\" \"Not because X. Because Y.\" State Y directly, with the reason.\n- **Negation lists**: \"No X, no Y, no Z.\" Say what does happen. One plain absence (\"No card required\") is fine.\n- **Trailing pile-ons**: a full claim, then a comma and more restating clauses. End the sentence at the claim.\n- **Self-answered questions and colon reveals**: \"The result? 3x faster.\" \"The best part: it learns.\" FAQ questions and a question in the reader's own voice are fine.\n- **Stock phrases**: \"Say goodbye to,\" \"X, reimagined,\" \"Unlock the power of,\" \"Take it to the next level,\" \"Here's the thing.\"\n- **Em dashes** in subject lines and preview text, and at most one or two in a long email.\n\nEmail-specific tells:\n- **Subject-line bait**: fake \"Re:\" or \"Fwd:\", \"You won't believe...\", \"🔥 Big news.\" The subject should hold up if it's the only line they read.\n- **Stock openers**: \"I hope this email finds you well,\" \"Just checking in,\" \"Great news!\" Open with the reason you're writing.\n- **Sign-off filler**: \"Feel free to reach out if you have any questions.\" Ask for one specific action, or end.\n\nFor the full blacklist, use the **copywriting** skill's AI-tells reference.\n\n### Length\n- 50-125 words for transactional\n- 150-300 words for educational\n- 300-500 words for story-driven\n\n### CTA Guidelines\n- Buttons for primary actions\n- Links for secondary actions\n- One clear primary CTA per email\n- Button text: Action + outcome\n\n**For detailed copy, personalization, and testing guidelines**: See [references\u002Fcopy-guidelines.md](references\u002Fcopy-guidelines.md)\n\n---\n\n## Output Format\n\n### Sequence Overview\n```\nSequence Name: [Name]\nTrigger: [What starts the sequence]\nGoal: [Primary conversion goal]\nLength: [Number of emails]\nTiming: [Delay between emails]\nExit Conditions: [When they leave the sequence]\n```\n\n### For Each Email\n```\nEmail [#]: [Name\u002FPurpose]\nSend: [Timing]\nSubject: [Subject line]\nPreview: [Preview text]\nBody: [Full copy]\nCTA: [Button text] → [Link destination]\nSegment\u002FConditions: [If applicable]\n```\n\n### Metrics Plan\nWhat to measure and benchmarks\n\n---\n\n## Task-Specific Questions\n\n1. What triggers entry to this sequence?\n2. What's the primary goal\u002Fconversion action?\n3. What do they already know about you?\n4. What other emails are they receiving?\n5. What's your current email performance?\n\n---\n\n## Tool Integrations\n\nFor implementation, see the [tools registry](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002FREGISTRY.md). Key email tools:\n\n| Tool | Best For | MCP | Guide |\n|------|----------|:---:|-------|\n| **Customer.io** | Behavior-based automation | - | [customer-io.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fcustomer-io.md) |\n| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fmailchimp.md) |\n| **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fnitrosend.md) |\n| **Resend** | Developer-friendly transactional | ✓ | [resend.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fresend.md) |\n| **SendGrid** | Transactional email at scale | - | [sendgrid.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fsendgrid.md) |\n| **Kit** | Creator\u002Fnewsletter focused | - | [kit.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fkit.md) |\n\n---\n\n## Related Skills\n\n- **lead-magnets**: For planning lead magnets that feed into nurture sequences\n- **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)\n- **onboarding**: For in-app onboarding (email supports this)\n- **copywriting**: For landing pages emails link to\n- **ab-testing**: For testing email elements\n- **popups**: For email capture popups\n- **revops**: For lifecycle stages that trigger email sequences\n","# Email Sequence Design\n\nYou 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.\n\n## Reference Routing\n\nLoad the matching reference before drafting or auditing the relevant part of a sequence. Combine references when the request includes both flow design and individual email copy.\n\n| User intent | Load | Covers |\n|---|---|---|\n| Build a welcome, lead nurture, re-engagement, or product onboarding flow | [sequence-templates.md](references\u002Fsequence-templates.md) | Sequence goals, timing, email order, and conversion actions |\n| Identify missing lifecycle emails or audit onboarding, retention, billing, usage, win-back, or campaigns | [email-types.md](references\u002Femail-types.md) | Email purposes, triggers, audiences, and the lifecycle audit checklist |\n| Write or edit individual emails within a sequence; improve CTA, personalization, or segmentation | [copy-guidelines.md](references\u002Fcopy-guidelines.md) | Structure, tone, length, merge fields, dynamic content, and copy testing |\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nCheck its **Learnings** section before drafting: angles, offers, and formats already tested there shouldn't be re-proposed as new ideas, and active lessons apply unless the user says otherwise.\n\nBefore creating a sequence, understand:\n\n1. **Sequence Type**\n   - Welcome\u002Fonboarding sequence\n   - Lead nurture sequence\n   - Re-engagement sequence\n   - Post-purchase sequence\n   - Event-based sequence\n   - Educational sequence\n   - Sales sequence\n\n2. **Audience Context**\n   - Who are they?\n   - What triggered them into this sequence?\n   - What do they already know\u002Fbelieve?\n   - What's their current relationship with you?\n\n3. **Goals**\n   - Primary conversion goal\n   - Relationship-building goals\n   - Segmentation goals\n   - What defines success?\n\n---\n\n## Core Principles\n\n### 1. One Email, One Job\n- Each email has one primary purpose\n- One main CTA per email\n- Don't try to do everything\n\n### 2. Value Before Ask\n- Lead with usefulness\n- Build trust through content\n- Earn the right to sell\n\n### 3. Relevance Over Volume\n- Fewer, better emails win\n- Segment for relevance\n- Quality > frequency\n\n### 4. Clear Path Forward\n- Every email moves them somewhere\n- Links should do something useful\n- Make next steps obvious\n\n---\n\n## Email Sequence Strategy\n\n### Sequence Length\n- Welcome: 3-7 emails\n- Lead nurture: 5-10 emails\n- Onboarding: 5-10 emails\n- Re-engagement: 3-5 emails\n\nDepends on:\n- Sales cycle length\n- Product complexity\n- Relationship stage\n\n### Timing\u002FDelays\n- Welcome email: Immediately\n- Early sequence: 1-2 days apart\n- Nurture: 2-4 days apart\n- Long-term: Weekly or bi-weekly\n\nConsider:\n- B2B: Avoid weekends\n- B2C: Test weekends\n- Time zones: Send at local time\n\n### Subject Line Strategy\n- Clear > Clever\n- Specific > Vague\n- Benefit or curiosity-driven\n- 40-60 characters ideal\n- Test emoji (they're polarizing)\n\n**Patterns that work:**\n- Question: \"Still struggling with X?\"\n- How-to: \"How to [achieve outcome] in [timeframe]\"\n- Number: \"3 ways to [benefit]\"\n- Direct: \"[First name], your [thing] is ready\"\n- Story tease: \"The mistake I made with [topic]\"\n\n### Preview Text\n- Extends the subject line\n- ~90-140 characters\n- Don't repeat subject line\n- Complete the thought or add intrigue\n\n---\n\n## Sequence Types Overview\n\n### Welcome Sequence (Post-Signup)\n**Length**: 5-7 emails over 12-14 days\n**Goal**: Activate, build trust, convert\n\nKey emails:\n1. Welcome + deliver promised value (immediate)\n2. Quick win (day 1-2)\n3. Story\u002FWhy (day 3-4)\n4. Social proof (day 5-6)\n5. Overcome objection (day 7-8)\n6. Core feature highlight (day 9-11)\n7. Conversion (day 12-14)\n\n### Lead Nurture Sequence (Pre-Sale)\n**Length**: 6-8 emails over 2-3 weeks\n**Goal**: Build trust, demonstrate expertise, convert\n\nKey emails:\n1. Deliver lead magnet + intro (immediate)\n2. Expand on topic (day 2-3)\n3. Problem deep-dive (day 4-5)\n4. Solution framework (day 6-8)\n5. Case study (day 9-11)\n6. Differentiation (day 12-14)\n7. Objection handler (day 15-18)\n8. Direct offer (day 19-21)\n\n### Re-Engagement Sequence\n**Length**: 3-4 emails over 2 weeks\n**Trigger**: 30-60 days of inactivity\n**Goal**: Win back or clean list\n\nKey emails:\n1. Check-in (genuine concern)\n2. Value reminder (what's new)\n3. Incentive (special offer)\n4. Last chance (stay or unsubscribe)\n\n### Onboarding Sequence (Product Users)\n**Length**: 5-7 emails over 14 days\n**Goal**: Activate, drive to aha moment, upgrade\n**Note**: Coordinate with in-app onboarding—email supports, doesn't duplicate\n\nKey emails:\n1. Welcome + first step (immediate)\n2. Getting started help (day 1)\n3. Feature highlight (day 2-3)\n4. Success story (day 4-5)\n5. Check-in (day 7)\n6. Advanced tip (day 10-12)\n7. Upgrade\u002Fexpand (day 14+)\n\n**For detailed templates**: See [references\u002Fsequence-templates.md](references\u002Fsequence-templates.md)\n\n---\n\n## Email Types by Category\n\n### Onboarding Emails\n- New users series\n- New customers series\n- Key onboarding step reminders\n- New user invites\n\n### Retention Emails\n- Upgrade to paid\n- Upgrade to higher plan\n- Ask for review\n- Proactive support offers\n- Product usage reports\n- NPS survey\n- Referral program\n\n### Billing Emails\n- Switch to annual\n- Failed payment recovery\n- Cancellation survey\n- Upcoming renewal reminders\n\n### Usage Emails\n- Daily\u002Fweekly\u002Fmonthly summaries\n- Key event notifications\n- Milestone celebrations\n\n### Win-Back Emails\n- Expired trials\n- Cancelled customers\n\n### Campaign Emails\n- Monthly roundup \u002F newsletter\n- Seasonal promotions\n- Product updates\n- Industry news roundup\n- Pricing updates\n\n**For detailed email type reference**: See [references\u002Femail-types.md](references\u002Femail-types.md)\n\n---\n\n## Email Copy Guidelines\n\n### Structure\n1. **Hook**: First line grabs attention\n2. **Context**: Why this matters to them\n3. **Value**: The useful content\n4. **CTA**: What to do next\n5. **Sign-off**: Human, warm close\n\n### Formatting\n- Short paragraphs (1-3 sentences)\n- White space between sections\n- Bullet points for scanability\n- Bold for emphasis (sparingly)\n- Mobile-first (most read on phone)\n\n### Tone\n- Conversational, not formal\n- First-person (I\u002Fwe) and second-person (you)\n- Active voice\n- Read it out loud. Does it sound like a person?\n\n### No AI Tells\n\nSubscribers learn to recognize generated email fast, and they stop reading. Write from the specific thing you want them to know or do.\n\nNever write these:\n- **Contrast reveals**: \"It's not X, it's Y.\" \"Not because X. Because Y.\" State Y directly, with the reason.\n- **Negation lists**: \"No X, no Y, no Z.\" Say what does happen. One plain absence (\"No card required\") is fine.\n- **Trailing pile-ons**: a full claim, then a comma and more restating clauses. End the sentence at the claim.\n- **Self-answered questions and colon reveals**: \"The result? 3x faster.\" \"The best part: it learns.\" FAQ questions and a question in the reader's own voice are fine.\n- **Stock phrases**: \"Say goodbye to,\" \"X, reimagined,\" \"Unlock the power of,\" \"Take it to the next level,\" \"Here's the thing.\"\n- **Em dashes** in subject lines and preview text, and at most one or two in a long email.\n\nEmail-specific tells:\n- **Subject-line bait**: fake \"Re:\" or \"Fwd:\", \"You won't believe...\", \"🔥 Big news.\" The subject should hold up if it's the only line they read.\n- **Stock openers**: \"I hope this email finds you well,\" \"Just checking in,\" \"Great news!\" Open with the reason you're writing.\n- **Sign-off filler**: \"Feel free to reach out if you have any questions.\" Ask for one specific action, or end.\n\nFor the full blacklist, use the **copywriting** skill's AI-tells reference.\n\n### Length\n- 50-125 words for transactional\n- 150-300 words for educational\n- 300-500 words for story-driven\n\n### CTA Guidelines\n- Buttons for primary actions\n- Links for secondary actions\n- One clear primary CTA per email\n- Button text: Action + outcome\n\n**For detailed copy, personalization, and testing guidelines**: See [references\u002Fcopy-guidelines.md](references\u002Fcopy-guidelines.md)\n\n---\n\n## Output Format\n\n### Sequence Overview\n```\nSequence Name: [Name]\nTrigger: [What starts the sequence]\nGoal: [Primary conversion goal]\nLength: [Number of emails]\nTiming: [Delay between emails]\nExit Conditions: [When they leave the sequence]\n```\n\n### For Each Email\n```\nEmail [#]: [Name\u002FPurpose]\nSend: [Timing]\nSubject: [Subject line]\nPreview: [Preview text]\nBody: [Full copy]\nCTA: [Button text] → [Link destination]\nSegment\u002FConditions: [If applicable]\n```\n\n### Metrics Plan\nWhat to measure and benchmarks\n\n---\n\n## Task-Specific Questions\n\n1. What triggers entry to this sequence?\n2. What's the primary goal\u002Fconversion action?\n3. What do they already know about you?\n4. What other emails are they receiving?\n5. What's your current email performance?\n\n---\n\n## Tool Integrations\n\nFor implementation, see the [tools registry](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002FREGISTRY.md). Key email tools:\n\n| Tool | Best For | MCP | Guide |\n|------|----------|:---:|-------|\n| **Customer.io** | Behavior-based automation | - | [customer-io.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fcustomer-io.md) |\n| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fmailchimp.md) |\n| **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fnitrosend.md) |\n| **Resend** | Developer-friendly transactional | ✓ | [resend.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fresend.md) |\n| **SendGrid** | Transactional email at scale | - | [sendgrid.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fsendgrid.md) |\n| **Kit** | Creator\u002Fnewsletter focused | - | [kit.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002Ftools\u002Fintegrations\u002Fkit.md) |\n\n---\n\n## Related Skills\n\n- **lead-magnets**: For planning lead magnets that feed into nurture sequences\n- **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)\n- **onboarding**: For in-app onboarding (email supports this)\n- **copywriting**: For landing pages emails link to\n- **ab-testing**: For testing email elements\n- **popups**: For email capture popups\n- **revops**: For lifecycle stages that trigger email sequences\n",{"name":5,"metadata":24,"description":7},{"version":25},"2.1.4","main","ad108f7eb3f6764136d02fb875772ebb34f54078","upstreams\u002Fsource-d\u002Fskills\u002Femails",2,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar","iamwaqargulzar.com","2026-11-03 21:14:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill emails",{"tool":40,"command":41},"bunx","bunx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill emails",{"tool":43,"command":44},"pnpm","pnpm dlx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill emails","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Femails\u002FSKILL.md",true,[48,54,58,62],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"evals\u002Fevals.json","REFERENCE","参考文档",7471,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Femails\u002Fevals\u002Fevals.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcopy-guidelines.md",2332,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Femails\u002Freferences\u002Fcopy-guidelines.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Femail-types.md",14250,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Femails\u002Freferences\u002Femail-types.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fsequence-templates.md",3909,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Femails\u002Freferences\u002Fsequence-templates.md",[67,74,81,88,95,102],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AG5VYEX7J2R2AAD54A7YT7","video","When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'record a product demo,' 'feature demo video,' 'in-app demo,' 'video pipeline,' 'copy this edit,' 'match this video style,' 'reverse-engineer this video,' 'edit like this reference,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AG5FMXWA33FQDNS9PS1TE6","social","When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter\u002FX, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' 'create a reel,' 'social listening,' 'brand mentions,' 'competitor monitoring,' 'top posts to comment on,' 'find people asking for,' 'carousel,' 'slide-by-slide,' or 'document post.' Use this for social content, repurposing, scheduling, video scripts, and listening. Posts avoid AI tells like 'it's not X, it's Y' reveals and broetry. For broader content strategy, see content-strategy. For paid ads, see ad-creative. For earned media, see public-relations.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsocial\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7AG559W96W3DGE31KXYY78S","sms","When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional\u002Fauth SMS. Also use when the user mentions \"SMS marketing,\" \"text message campaigns,\" \"SMS sequence,\" \"SMS automation,\" \"abandoned cart text,\" \"post-purchase SMS,\" \"Klaviyo SMS,\" \"Postscript,\" \"Attentive,\" \"Twilio,\" \"A2P 10DLC,\" \"TCPA,\" \"SMS compliance,\" \"short code,\" \"toll-free SMS,\" \"MMS campaign,\" \"should I do SMS,\" \"SMS vs email,\" \"WhatsApp marketing,\" \"WhatsApp Business API,\" \"WhatsApp templates,\" or \"click-to-WhatsApp.\" For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsms\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7AG4WJ9EDSECNTQN0FEAYCQ","site-architecture","When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions \"sitemap,\" \"site map,\" \"visual sitemap,\" \"site structure,\" \"page hierarchy,\" \"information architecture,\" \"IA,\" \"navigation design,\" \"URL structure,\" \"breadcrumbs,\" \"internal linking strategy,\" \"website planning,\" \"what pages do I need,\" \"how should I organize my site,\" \"site navigation,\" \"which website builder should I use,\" \"migrate my website,\" or \"add a blog to my existing site.\" Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsite-architecture\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7AG4MH58GRMSHC0TADAWQ69","signup","When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup form optimization,\" \"free trial signup,\" \"reduce signup dropoff,\" \"account creation flow,\" \"people aren't signing up,\" \"signup abandonment,\" \"trial conversion rate,\" \"nobody completes registration,\" \"too many steps to sign up,\" or \"simplify our signup.\" Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsignup\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7AG4CGGH35KYDFHYSS1BQZ5","seo-audit","When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" \"SEO health check,\" \"my traffic dropped,\" \"lost rankings,\" \"not showing up in Google,\" \"site isn't ranking,\" \"Google update hit me,\" \"page speed,\" \"core web vitals,\" \"crawl errors,\" \"indexing issues,\" \"stuck on page 2,\" \"striking distance keywords,\" \"title tag rewrite,\" \"low CTR,\" \"local SEO,\" \"Google Business Profile,\" or \"map pack.\" Use this even if the user just says something vague like \"my SEO is bad\" or \"help with SEO\" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fseo-audit\u002FSKILL.md",[],[]]