marketing-email-sequence/SKILL.md
Use when creating email sequences, drip campaigns, welcome flows, onboarding emails, trial nurture sequences, or re-engagement campaigns. Produces complete sequences with subject lines, preview text, timing, and email body copy.
npx skillsauth add paulund/ai marketing-email-sequenceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
references/email-sequence-guide.md before drafting.One email, one job.
Every email in a sequence has a single purpose. Not "introduce the product and explain the pricing and collect a testimonial request." Just one thing. If an email is trying to do two things, it is two emails.
Deliver value before asking. People ignore sequences that only sell. People read sequences that teach, help, or entertain — and then buy when the time is right.
For new signups or subscribers. Goal: build trust, deliver early value, and drive first meaningful action.
| Email | Timing | Goal | | --- | --- | --- | | 1 | Immediately | Confirm signup, set expectations, deliver first value | | 2 | Day 2 | Show the quickest path to value | | 3 | Day 4 | Share a specific use case or success story | | 4 | Day 7 | Address the most common objection or question | | 5 | Day 10 | Introduce an advanced feature or capability | | 6 | Day 12 | Social proof — case study or customer quote | | 7 | Day 14 | Soft CTA to upgrade, book a call, or complete setup |
For trial users or new paid customers. Goal: drive product activation (first meaningful action in the product).
| Email | Timing | Goal | | --- | --- | --- | | 1 | Immediately | Welcome + first step to activate | | 2 | Day 2 | Follow up on activation — help if stuck | | 3 | Day 5 | Show a specific feature they have not used yet | | 4 | Day 8 | Share a power-user tip | | 5 | Day 12 | Check in — offer help if they have not engaged | | 6 | Day 14 | Trial ending warning (if applicable) |
For leads who are not ready to buy yet. Goal: build credibility and stay top-of-mind until they are ready.
| Email | Timing | Goal | | --- | --- | --- | | 1 | Immediately | Welcome + deliver lead magnet or content promise | | 2 | Day 3 | Teach something useful with no ask | | 3 | Day 6 | Case study or real-world example | | 4 | Day 9 | Address common objection or misconception | | 5 | Day 12 | Compare options — position your solution honestly | | 6 | Day 16 | Soft CTA with low-commitment offer (free trial, demo) | | 7 | Day 20 | Final value email — reiterate what they get |
For subscribers who have gone quiet. Goal: either re-activate or cleanly remove from list.
| Email | Timing | Goal | | --- | --- | --- | | 1 | Day 0 | "We miss you" — check in, offer value | | 2 | Day 5 | Share something new that might be relevant | | 3 | Day 10 | Last chance — explicit re-engagement ask | | 4 | Day 14 | Confirm unsubscribe (cleans list) |
Every email follows this structure:
Before presenting any sequence, verify:
| Topic | Reference | Load When |
| ----- | --------- | --------- |
| Email Sequence Patterns | references/email-sequence-guide.md | Always |
development
Use when implementing any logic, fixing any bug, or changing any behaviour. Use when you need to prove code works, when a bug report arrives, or when modifying existing functionality. Do NOT use for config changes, data migrations, or dependency updates.
development
Use when starting a new feature, when requirements are unclear, when asked to write code without a clear spec, or before any non-trivial implementation. Do NOT use for trivial bug fixes or one-line changes.
development
Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters. Detects the stack from dependency files, fetches official documentation, implements following documented patterns, and cites sources for every framework-specific decision.
development
Use when preparing to ship a feature, release, or deployment. Use before merging to main, creating a release, or deploying to production. Do NOT use for CI-only changes or internal refactors that don't reach production.