skillboardUpdated every 6 hours
skillboardWhen 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.
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.
Load 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.
| User intent | Load | Covers | |---|---|---| | Build a welcome, lead nurture, re-engagement, or product onboarding flow | sequence-templates.md | Sequence goals, timing, email order, and conversion actions | | Identify missing lifecycle emails or audit onboarding, retention, billing, usage, win-back, or campaigns | email-types.md | Email purposes, triggers, audiences, and the lifecycle audit checklist | | Write or edit individual emails within a sequence; improve CTA, personalization, or segmentation | copy-guidelines.md | Structure, tone, length, merge fields, dynamic content, and copy testing |
Check for product marketing context first:
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.
Before creating a sequence, understand:
Sequence Type
Audience Context
Goals
Depends on:
Consider:
Patterns that work:
Length: 5-7 emails over 12-14 days Goal: Activate, build trust, convert
Key emails:
Length: 6-8 emails over 2-3 weeks Goal: Build trust, demonstrate expertise, convert
Key emails:
Length: 3-4 emails over 2 weeks Trigger: 30-60 days of inactivity Goal: Win back or clean list
Key emails:
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:
For detailed templates: See references/sequence-templates.md
For detailed email type reference: See references/email-types.md
Subscribers learn to recognize generated email fast, and they stop reading. Write from the specific thing you want them to know or do.
Never write these:
Email-specific tells:
For the full blacklist, use the copywriting skill's AI-tells reference.
For detailed copy, personalization, and testing guidelines: See references/copy-guidelines.md
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]
Email [#]: [Name/Purpose]
Send: [Timing]
Subject: [Subject line]
Preview: [Preview text]
Body: [Full copy]
CTA: [Button text] → [Link destination]
Segment/Conditions: [If applicable]
What to measure and benchmarks
For implementation, see the tools registry. Key email tools:
| Tool | Best For | MCP | Guide | |------|----------|:---:|-------| | Customer.io | Behavior-based automation | - | customer-io.md | | Mailchimp | SMB email marketing | ✓ | mailchimp.md | | Nitrosend | AI-native email (sequences via prompts) | ✓ | nitrosend.md | | Resend | Developer-friendly transactional | ✓ | resend.md | | SendGrid | Transactional email at scale | - | sendgrid.md | | Kit | Creator/newsletter focused | - | kit.md |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/emails · pinned to the source commit
# Run from your project root
git clone https://github.com/coreyhaines31/marketingskills.git .skillboard-tmp
git -C .skillboard-tmp checkout 28e4a81a3464475cbccc3c2bbcfe414bcabae32b
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/emails" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/coreyhaines31/marketingskills.git .skillboard-tmp
git -C .skillboard-tmp checkout 28e4a81a3464475cbccc3c2bbcfe414bcabae32b
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/emails" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/emails
Scanner static-checks@0.1.0 · commit 28e4a81a3464. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.