Email Sequence Design
Unverified●25/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add emailsWho is stuck, and on what
People sign up or buy from you and then you never really follow up, so they forget about you and drift away. You know you should be emailing them but you have no idea what to say or when to send it.
What it gives you
A complete set of written emails with subject lines, send timing, and exact wording, ready to paste into your email tool.
When NOT to use it
It will not send the emails for you or connect to your email account.
The whole source
Frontmatter — 3 properties
| name | emails |
|---|---|
| description | 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. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding. |
| metadata | version: 2.0.0 |
| 1 | --- |
| 2 | name: emails |
| 3 | description: 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. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.B1 — Line is 581 characters — unreadable by eye |
| 4 | metadata: |
| 5 | version: 2.0.0 |
| 6 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 7 | |
| 8 | # Email Sequence Design |
| 9 | |
| 10 | 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. |
| 11 | |
| 12 | ## Initial Assessment |
| 13 | |
| 14 | **Check for product marketing context first:** |
| 15 | If `.agents/product-marketing.md` exists (or `.claude/product-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. |
| 16 | |
| 17 | Before creating a sequence, understand: |
| 18 | |
| 19 | 1. **Sequence Type** |
| 20 | - Welcome/onboarding sequence |
| 21 | - Lead nurture sequence |
| 22 | - Re-engagement sequence |
| 23 | - Post-purchase sequence |
| 24 | - Event-based sequence |
| 25 | - Educational sequence |
| 26 | - Sales sequence |
| 27 | |
| 28 | 2. **Audience Context** |
| 29 | - Who are they? |
| 30 | - What triggered them into this sequence? |
| 31 | - What do they already know/believe? |
| 32 | - What's their current relationship with you? |
| 33 | |
| 34 | 3. **Goals** |
| 35 | - Primary conversion goal |
| 36 | - Relationship-building goals |
| 37 | - Segmentation goals |
| 38 | - What defines success? |
| 39 | |
| 40 | --- |
| 41 | |
| 42 | ## Core Principles |
| 43 | |
| 44 | ### 1. One Email, One Job |
| 45 | - Each email has one primary purpose |
| 46 | - One main CTA per email |
| 47 | - Don't try to do everything |
| 48 | |
| 49 | ### 2. Value Before Ask |
| 50 | - Lead with usefulness |
| 51 | - Build trust through content |
| 52 | - Earn the right to sell |
| 53 | |
| 54 | ### 3. Relevance Over Volume |
| 55 | - Fewer, better emails win |
| 56 | - Segment for relevance |
| 57 | - Quality > frequency |
| 58 | |
| 59 | ### 4. Clear Path Forward |
| 60 | - Every email moves them somewhere |
| 61 | - Links should do something useful |
| 62 | - Make next steps obvious |
| 63 | |
| 64 | --- |
| 65 | |
| 66 | ## Email Sequence Strategy |
| 67 | |
| 68 | ### Sequence Length |
| 69 | - Welcome: 3-7 emails |
| 70 | - Lead nurture: 5-10 emails |
| 71 | - Onboarding: 5-10 emails |
| 72 | - Re-engagement: 3-5 emails |
| 73 | |
| 74 | Depends on: |
| 75 | - Sales cycle length |
| 76 | - Product complexity |
| 77 | - Relationship stage |
| 78 | |
| 79 | ### Timing/Delays |
| 80 | - Welcome email: Immediately |
| 81 | - Early sequence: 1-2 days apart |
| 82 | - Nurture: 2-4 days apart |
| 83 | - Long-term: Weekly or bi-weekly |
| 84 | |
| 85 | Consider: |
| 86 | - B2B: Avoid weekends |
| 87 | - B2C: Test weekends |
| 88 | - Time zones: Send at local time |
| 89 | |
| 90 | ### Subject Line Strategy |
| 91 | - Clear > Clever |
| 92 | - Specific > Vague |
| 93 | - Benefit or curiosity-driven |
| 94 | - 40-60 characters ideal |
| 95 | - Test emoji (they're polarizing) |
| 96 | |
| 97 | **Patterns that work:** |
| 98 | - Question: "Still struggling with X?" |
| 99 | - How-to: "How to [achieve outcome] in [timeframe]" |
| 100 | - Number: "3 ways to [benefit]" |
| 101 | - Direct: "[First name], your [thing] is ready" |
| 102 | - Story tease: "The mistake I made with [topic]" |
| 103 | |
| 104 | ### Preview Text |
| 105 | - Extends the subject line |
| 106 | - ~90-140 characters |
| 107 | - Don't repeat subject line |
| 108 | - Complete the thought or add intrigue |
| 109 | |
| 110 | --- |
| 111 | |
| 112 | ## Sequence Types Overview |
| 113 | |
| 114 | ### Welcome Sequence (Post-Signup) |
| 115 | **Length**: 5-7 emails over 12-14 days |
| 116 | **Goal**: Activate, build trust, convert |
| 117 | |
| 118 | Key emails: |
| 119 | 1. Welcome + deliver promised value (immediate) |
| 120 | 2. Quick win (day 1-2) |
| 121 | 3. Story/Why (day 3-4) |
| 122 | 4. Social proof (day 5-6) |
| 123 | 5. Overcome objection (day 7-8) |
| 124 | 6. Core feature highlight (day 9-11) |
| 125 | 7. Conversion (day 12-14) |
| 126 | |
| 127 | ### Lead Nurture Sequence (Pre-Sale) |
| 128 | **Length**: 6-8 emails over 2-3 weeks |
| 129 | **Goal**: Build trust, demonstrate expertise, convert |
| 130 | |
| 131 | Key emails: |
| 132 | 1. Deliver lead magnet + intro (immediate) |
| 133 | 2. Expand on topic (day 2-3) |
| 134 | 3. Problem deep-dive (day 4-5) |
| 135 | 4. Solution framework (day 6-8) |
| 136 | 5. Case study (day 9-11) |
| 137 | 6. Differentiation (day 12-14) |
| 138 | 7. Objection handler (day 15-18) |
| 139 | 8. Direct offer (day 19-21) |
| 140 | |
| 141 | ### Re-Engagement Sequence |
| 142 | **Length**: 3-4 emails over 2 weeks |
| 143 | **Trigger**: 30-60 days of inactivity |
| 144 | **Goal**: Win back or clean list |
| 145 | |
| 146 | Key emails: |
| 147 | 1. Check-in (genuine concern) |
| 148 | 2. Value reminder (what's new) |
| 149 | 3. Incentive (special offer) |
| 150 | 4. Last chance (stay or unsubscribe) |
| 151 | |
| 152 | ### Onboarding Sequence (Product Users) |
| 153 | **Length**: 5-7 emails over 14 days |
| 154 | **Goal**: Activate, drive to aha moment, upgrade |
| 155 | **Note**: Coordinate with in-app onboarding—email supports, doesn't duplicate |
| 156 | |
| 157 | Key emails: |
| 158 | 1. Welcome + first step (immediate) |
| 159 | 2. Getting started help (day 1) |
| 160 | 3. Feature highlight (day 2-3) |
| 161 | 4. Success story (day 4-5) |
| 162 | 5. Check-in (day 7) |
| 163 | 6. Advanced tip (day 10-12) |
| 164 | 7. Upgrade/expand (day 14+) |
| 165 | |
| 166 | **For detailed templates**: See [references/sequence-templates.md](references/sequence-templates.md) |
| 167 | |
| 168 | --- |
| 169 | |
| 170 | ## Email Types by Category |
| 171 | |
| 172 | ### Onboarding Emails |
| 173 | - New users series |
| 174 | - New customers series |
| 175 | - Key onboarding step reminders |
| 176 | - New user invites |
| 177 | |
| 178 | ### Retention Emails |
| 179 | - Upgrade to paid |
| 180 | - Upgrade to higher plan |
| 181 | - Ask for review |
| 182 | - Proactive support offers |
| 183 | - Product usage reports |
| 184 | - NPS survey |
| 185 | - Referral program |
| 186 | |
| 187 | ### Billing Emails |
| 188 | - Switch to annual |
| 189 | - Failed payment recovery |
| 190 | - Cancellation survey |
| 191 | - Upcoming renewal reminders |
| 192 | |
| 193 | ### Usage Emails |
| 194 | - Daily/weekly/monthly summaries |
| 195 | - Key event notifications |
| 196 | - Milestone celebrations |
| 197 | |
| 198 | ### Win-Back Emails |
| 199 | - Expired trials |
| 200 | - Cancelled customers |
| 201 | |
| 202 | ### Campaign Emails |
| 203 | - Monthly roundup / newsletter |
| 204 | - Seasonal promotions |
| 205 | - Product updates |
| 206 | - Industry news roundup |
| 207 | - Pricing updates |
| 208 | |
| 209 | **For detailed email type reference**: See [references/email-types.md](references/email-types.md) |
| 210 | |
| 211 | --- |
| 212 | |
| 213 | ## Email Copy Guidelines |
| 214 | |
| 215 | ### Structure |
| 216 | 1. **Hook**: First line grabs attention |
| 217 | 2. **Context**: Why this matters to them |
| 218 | 3. **Value**: The useful content |
| 219 | 4. **CTA**: What to do next |
| 220 | 5. **Sign-off**: Human, warm close |
| 221 | |
| 222 | ### Formatting |
| 223 | - Short paragraphs (1-3 sentences) |
| 224 | - White space between sections |
| 225 | - Bullet points for scanability |
| 226 | - Bold for emphasis (sparingly) |
| 227 | - Mobile-first (most read on phone) |
| 228 | |
| 229 | ### Tone |
| 230 | - Conversational, not formal |
| 231 | - First-person (I/we) and second-person (you) |
| 232 | - Active voice |
| 233 | - Read it out loud—does it sound human? |
| 234 | |
| 235 | ### Length |
| 236 | - 50-125 words for transactional |
| 237 | - 150-300 words for educational |
| 238 | - 300-500 words for story-driven |
| 239 | |
| 240 | ### CTA Guidelines |
| 241 | - Buttons for primary actions |
| 242 | - Links for secondary actions |
| 243 | - One clear primary CTA per email |
| 244 | - Button text: Action + outcome |
| 245 | |
| 246 | **For detailed copy, personalization, and testing guidelines**: See [references/copy-guidelines.md](references/copy-guidelines.md) |
| 247 | |
| 248 | --- |
| 249 | |
| 250 | ## Output Format |
| 251 | |
| 252 | ### Sequence Overview |
| 253 | ``` |
| 254 | Sequence Name: [Name] |
| 255 | Trigger: [What starts the sequence] |
| 256 | Goal: [Primary conversion goal] |
| 257 | Length: [Number of emails] |
| 258 | Timing: [Delay between emails] |
| 259 | Exit Conditions: [When they leave the sequence] |
| 260 | ``` |
| 261 | |
| 262 | ### For Each Email |
| 263 | ``` |
| 264 | Email [#]: [Name/Purpose] |
| 265 | Send: [Timing] |
| 266 | Subject: [Subject line] |
| 267 | Preview: [Preview text] |
| 268 | Body: [Full copy] |
| 269 | CTA: [Button text] → [Link destination] |
| 270 | Segment/Conditions: [If applicable] |
| 271 | ``` |
| 272 | |
| 273 | ### Metrics Plan |
| 274 | What to measure and benchmarks |
| 275 | |
| 276 | --- |
| 277 | |
| 278 | ## Task-Specific Questions |
| 279 | |
| 280 | 1. What triggers entry to this sequence? |
| 281 | 2. What's the primary goal/conversion action? |
| 282 | 3. What do they already know about you? |
| 283 | 4. What other emails are they receiving? |
| 284 | 5. What's your current email performance? |
| 285 | |
| 286 | --- |
| 287 | |
| 288 | ## Tool Integrations |
| 289 | |
| 290 | For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email tools: |
| 291 | |
| 292 | | Tool | Best For | MCP | Guide | |
| 293 | |------|----------|:---:|-------| |
| 294 | | **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) | |
| 295 | | **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) | |
| 296 | | **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](../../tools/integrations/nitrosend.md) | |
| 297 | | **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) | |
| 298 | | **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) | |
| 299 | | **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) | |
| 300 | |
| 301 | --- |
| 302 | |
| 303 | ## Related Skills |
| 304 | |
| 305 | - **lead-magnets**: For planning lead magnets that feed into nurture sequences |
| 306 | - **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this) |
| 307 | - **onboarding**: For in-app onboarding (email supports this) |
| 308 | - **copywriting**: For landing pages emails link to |
| 309 | - **ab-testing**: For testing email elements |
| 310 | - **popups**: For email capture popups |
| 311 | - **revops**: For lifecycle stages that trigger email sequences |
| 312 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Structure Your Invention For A Patent FilingDescribe your invention in plain words and get back a formal write-up that lays out the problem it solves, how it works, and which parts are worth protecting.●····●37/40Claims Drafting: The Core Patent SkillDescribe your invention in plain words and get back a numbered set of formal patent claims — the legal wording that defines exactly what you own.●····●36/40Patent Novelty and Non-Obviousness CheckDescribe your invention in everyday words and get back a clear read on whether it's new and original enough to patent, plus where it might hit trouble.●····●35/40Patent Pipeline: From Invention to FilingDescribe your invention in plain words and get back a complete first-draft patent application — claims, full description, and abstract — ready to hand to a patent attorney.●····●35/40