[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7819E5PEDMPJCCFMEVK0GF4":3,"skill-same:01M7819E5PEDMPJCCFMEVK0GF4":76},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7819E5PEDMPJCCFMEVK0GF4","marketing-emails",null,"When the user wants to create or improve automated email sequences, or asks what to send, when, or whether an email or flow is working: welcome, onboarding, nurture, and win-back flows. No AI tells like 'it's not X, it's Y', 'no X, no Y, no Z' lists, or fake 'Re:' subject lines. For cold outreach, see cold-email. For in-app onboarding, see onboarding. For texts, see sms.","TheAngryPit\u002FTheAngrySkills","TheAngryPit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7040636?v=4","01M7803EENA9ATXJ46S9268QJX","Vitor Cepeda Lopes","01M7803EF9FMF4G4420XE4DV7Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-emails\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-emails\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: marketing-emails\ndescription: \"When the user wants to create or improve automated email sequences, or asks what to send, when, or whether an email or flow is working: welcome, onboarding, nurture, and win-back flows. No AI tells like 'it's not X, it's Y', 'no X, no Y, no Z' lists, or fake 'Re:' subject lines. For cold outreach, see cold-email. For in-app onboarding, see onboarding. For texts, see sms.\"\nmetadata:\n  version: 2.1.7\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":25,"description":7},{"version":26},"2.1.7","main","f31e1d2df163b90a48e30d0a3df67285f6641418","skills\u002Fmirrors-marketing\u002Fmarketing-emails",1,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills","https:\u002F\u002Fgithub.com\u002FTheAngryPit","www.vitorcepedalopes.com","Creative Director | Executive Producer | Storyteller | Narrative Worlds & Creative Production Systems\r\nFounder @TheHive-Mind ","2026-11-14 21:48:38",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add TheAngryPit\u002FTheAngrySkills --skill marketing-emails",{"tool":42,"command":43},"bunx","bunx skills add TheAngryPit\u002FTheAngrySkills --skill marketing-emails",{"tool":45,"command":46},"pnpm","pnpm dlx skills add TheAngryPit\u002FTheAngrySkills --skill marketing-emails","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-emails\u002FSKILL.md",true,[50,56,60,64,68,72],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"evals\u002Fevals.json","REFERENCE","参考文档",7471,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-emails\u002Fevals\u002Fevals.json",{"path":57,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":16},"LICENSE","许可证",1069,{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"MIRROR.md",567,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-emails\u002FMIRROR.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fcopy-guidelines.md",2332,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-emails\u002Freferences\u002Fcopy-guidelines.md",{"path":69,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Femail-types.md",14250,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-emails\u002Freferences\u002Femail-types.md",{"path":73,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fsequence-templates.md",3909,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-emails\u002Freferences\u002Fsequence-templates.md",[77,84,91,98,105,112],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":20},"01M782GJ4CTPNKZN0WXTASXXZ4","X MCP guide","ALWAYS read this before using any X tool (the X plugin, any X MCP, or Grok Bot's built-in public X reads) and again on any X error. X tools are included in Grok Bot at no cost: never estimate costs, check credits, or tell the user to buy credits. tools=0 \u002F user-X-* not found is a setup failure, not a paywall. Covers Spaces, communities, and Lists (reads and list writes), X Chat (XChat, inbox, DMs, unread, message requests, Chat PIN, juicebox, xchat_lite: clone xchat-grokbot-helper yourself and decrypt locally), scheduled X calls (schedule_call, list_scheduled_calls and the other call tools), and livestreams (stream sources, broadcasts, scheduled broadcasts, broadcast chat, moderators, mutes). Chat, call, livestream, Spaces, or Lists tools missing while other X tools work: reconnect the X plugin.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx\u002Fskills\u002Fx-api-mcp-guide\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":20},"01M782GBW77901ESC9PD3XAM6V","X Money guide","Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability. Covers the approval rule for every action that moves money (always ask, every time, no exceptions), how the connection works (connection code plus passkey in the X app), how to guide the user through connect, reconnect, and revoke at x.com\u002Fi\u002Fmoney\u002Fsettings\u002Fconnections, and what each failure message means.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx-money\u002Fskills\u002Fx-money-guide\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M782G7CMYD2JSVT3RX81QRB8","google-slides","Build and edit Google Slides through the google-slides MCP tools - slides, grids of cards and columns, text boxes, shapes, images, tables, styling, layout inspection, and per-slide PNG rendering. Use when creating a deck, laying out slide elements, matching a template, or verifying how a slide looks.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-slides\u002Fskills\u002Fgoogle-slides\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M782G4DDAJ4SMGJEF13HTX69","google-sheets","Build and edit Google Sheets with the google-sheets tools - values, formatting, charts, conditional formatting, structure, validation, named and protected ranges. Use when creating a spreadsheet or dashboard, formatting cells, adding or fixing charts, or reorganizing tabs and rows.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-sheets\u002Fskills\u002Fgoogle-sheets\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":20},"01M782G1F8QNMNKRSY6M3Y0QG6","google-drive","Work with Google Drive through its MCP tools - search, read, create, organize, share, comment, and export files. Use when creating files in specific folders, moving or renaming, converting Markdown\u002FCSV into Docs\u002FSheets, managing comments, or exporting a rendered PDF.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-drive\u002Fskills\u002Fgoogle-drive\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":20},"01M782FYVJ5XTP2R0B446RRYTX","google-docs","Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers\u002Ffooters. Use when creating a formatted document, editing document content, or applying styles.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-docs\u002Fskills\u002Fgoogle-docs\u002FSKILL.md",[],[]]