When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

MITAuto-check passedMarketing & SEO

Install Emails

skills CLI
$ npx skills add coreyhaines31/marketingskills --skill emails -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coreyhaines31/marketingskills emails --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/emails .claude/skills/emails && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
emails
GitHub stars
54k
Used in
1 other repo
Token cost
~2.8k tokens
SKILL.md length
1,227 words
Files
5 (incl. references)
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

  • Works in 4 steps: One Email, One Job → Value Before Ask → Relevance Over Volume → …
  • Wants to create
  • SKILL.md covers Reference Routing, Initial Assessment, Core Principles and Email Sequence Strategy, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Emails is an agent skill from coreyhaines31/marketingskills. 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…

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `evals/evals.json`, `references/copy-guidelines.md` and `references/email-types.md`).

It sits in Marketing & SEO, covering Email marketing and Cold outreach. The repository describes itself as: Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. The licence is MIT.

When your agent uses it

  • Wants to create
  • Optimize an email sequence
  • Automated email flow
  • Lifecycle email program

Example prompts

  • “email sequence,”
  • “drip campaign,”
  • “nurture sequence,”
  • “/emails”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. One Email, One Job
  2. Value Before Ask
  3. Relevance Over Volume
  4. Clear Path Forward

What it can do on your machine

Read from SKILL.md and the folder at commit 1efedbc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Emails loads about 2.8k tokens when it runs, and up to ~8k if it reads all its reference files. Until then it costs about 176 tokens; SKILL.md has 1,227 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~176
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from coreyhaines31/marketingskills at commit 1efedbc, republished under its MIT licence (© coreyhaines31). 1,227 words, ~2,836 tokens.

Download SKILL.mdSave it as .claude/skills/emails/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
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. 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.
metadata.version
2.1.3

Email Sequence Design

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.

Reference Routing

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 intentLoadCovers
Build a welcome, lead nurture, re-engagement, or product onboarding flowsequence-templates.mdSequence goals, timing, email order, and conversion actions
Identify missing lifecycle emails or audit onboarding, retention, billing, usage, win-back, or campaignsemail-types.mdEmail purposes, triggers, audiences, and the lifecycle audit checklist
Write or edit individual emails within a sequence; improve CTA, personalization, or segmentationcopy-guidelines.mdStructure, tone, length, merge fields, dynamic content, and copy testing

Initial Assessment

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:

  1. Sequence Type

    • Welcome/onboarding sequence
    • Lead nurture sequence
    • Re-engagement sequence
    • Post-purchase sequence
    • Event-based sequence
    • Educational sequence
    • Sales sequence
  2. Audience Context

    • Who are they?
    • What triggered them into this sequence?
    • What do they already know/believe?
    • What's their current relationship with you?
  3. Goals

    • Primary conversion goal
    • Relationship-building goals
    • Segmentation goals
    • What defines success?

Core Principles

1. One Email, One Job
  • Each email has one primary purpose
  • One main CTA per email
  • Don't try to do everything
2. Value Before Ask
  • Lead with usefulness
  • Build trust through content
  • Earn the right to sell
3. Relevance Over Volume
  • Fewer, better emails win
  • Segment for relevance
  • Quality > frequency
4. Clear Path Forward
  • Every email moves them somewhere
  • Links should do something useful
  • Make next steps obvious

Email Sequence Strategy

Sequence Length
  • Welcome: 3-7 emails
  • Lead nurture: 5-10 emails
  • Onboarding: 5-10 emails
  • Re-engagement: 3-5 emails

Depends on:

  • Sales cycle length
  • Product complexity
  • Relationship stage
Timing/Delays
  • Welcome email: Immediately
  • Early sequence: 1-2 days apart
  • Nurture: 2-4 days apart
  • Long-term: Weekly or bi-weekly

Consider:

  • B2B: Avoid weekends
  • B2C: Test weekends
  • Time zones: Send at local time
Subject Line Strategy
  • Clear > Clever
  • Specific > Vague
  • Benefit or curiosity-driven
  • 40-60 characters ideal
  • Test emoji (they're polarizing)

Patterns that work:

  • Question: "Still struggling with X?"
  • How-to: "How to [achieve outcome] in [timeframe]"
  • Number: "3 ways to [benefit]"
  • Direct: "[First name], your [thing] is ready"
  • Story tease: "The mistake I made with [topic]"
Preview Text
  • Extends the subject line
  • ~90-140 characters
  • Don't repeat subject line
  • Complete the thought or add intrigue

Sequence Types Overview

Welcome Sequence (Post-Signup)

Length: 5-7 emails over 12-14 days Goal: Activate, build trust, convert

Key emails:

  1. Welcome + deliver promised value (immediate)
  2. Quick win (day 1-2)
  3. Story/Why (day 3-4)
  4. Social proof (day 5-6)
  5. Overcome objection (day 7-8)
  6. Core feature highlight (day 9-11)
  7. Conversion (day 12-14)
Lead Nurture Sequence (Pre-Sale)

Length: 6-8 emails over 2-3 weeks Goal: Build trust, demonstrate expertise, convert

Key emails:

  1. Deliver lead magnet + intro (immediate)
  2. Expand on topic (day 2-3)
  3. Problem deep-dive (day 4-5)
  4. Solution framework (day 6-8)
  5. Case study (day 9-11)
  6. Differentiation (day 12-14)
  7. Objection handler (day 15-18)
  8. Direct offer (day 19-21)
Re-Engagement Sequence

Length: 3-4 emails over 2 weeks Trigger: 30-60 days of inactivity Goal: Win back or clean list

Key emails:

  1. Check-in (genuine concern)
  2. Value reminder (what's new)
  3. Incentive (special offer)
  4. Last chance (stay or unsubscribe)
Onboarding Sequence (Product Users)

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:

  1. Welcome + first step (immediate)
  2. Getting started help (day 1)
  3. Feature highlight (day 2-3)
  4. Success story (day 4-5)
  5. Check-in (day 7)
  6. Advanced tip (day 10-12)
  7. Upgrade/expand (day 14+)

For detailed templates: See references/sequence-templates.md


Email Types by Category

Onboarding Emails
  • New users series
  • New customers series
  • Key onboarding step reminders
  • New user invites
Retention Emails
  • Upgrade to paid
  • Upgrade to higher plan
  • Ask for review
  • Proactive support offers
  • Product usage reports
  • NPS survey
  • Referral program
Billing Emails
  • Switch to annual
  • Failed payment recovery
  • Cancellation survey
  • Upcoming renewal reminders
Usage Emails
  • Daily/weekly/monthly summaries
  • Key event notifications
  • Milestone celebrations
Win-Back Emails
  • Expired trials
  • Cancelled customers
Campaign Emails
  • Monthly roundup / newsletter
  • Seasonal promotions
  • Product updates
  • Industry news roundup
  • Pricing updates

For detailed email type reference: See references/email-types.md


Email Copy Guidelines

Show full SKILL.md (490 more words)Show less
Structure
  1. Hook: First line grabs attention
  2. Context: Why this matters to them
  3. Value: The useful content
  4. CTA: What to do next
  5. Sign-off: Human, warm close
Formatting
  • Short paragraphs (1-3 sentences)
  • White space between sections
  • Bullet points for scanability
  • Bold for emphasis (sparingly)
  • Mobile-first (most read on phone)
Tone
  • Conversational, not formal
  • First-person (I/we) and second-person (you)
  • Active voice
  • Read it out loud. Does it sound like a person?
No AI Tells

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:

  • Contrast reveals: "It's not X, it's Y." "Not because X. Because Y." State Y directly, with the reason.
  • Negation lists: "No X, no Y, no Z." Say what does happen. One plain absence ("No card required") is fine.
  • Trailing pile-ons: a full claim, then a comma and more restating clauses. End the sentence at the claim.
  • 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.
  • Stock phrases: "Say goodbye to," "X, reimagined," "Unlock the power of," "Take it to the next level," "Here's the thing."
  • Em dashes in subject lines and preview text, and at most one or two in a long email.

Email-specific tells:

  • 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.
  • Stock openers: "I hope this email finds you well," "Just checking in," "Great news!" Open with the reason you're writing.
  • Sign-off filler: "Feel free to reach out if you have any questions." Ask for one specific action, or end.

For the full blacklist, use the copywriting skill's AI-tells reference.

Length
  • 50-125 words for transactional
  • 150-300 words for educational
  • 300-500 words for story-driven
CTA Guidelines
  • Buttons for primary actions
  • Links for secondary actions
  • One clear primary CTA per email
  • Button text: Action + outcome

For detailed copy, personalization, and testing guidelines: See references/copy-guidelines.md


Output Format

Sequence Overview
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]
For Each Email
Email [#]: [Name/Purpose]
Send: [Timing]
Subject: [Subject line]
Preview: [Preview text]
Body: [Full copy]
CTA: [Button text] → [Link destination]
Segment/Conditions: [If applicable]
Metrics Plan

What to measure and benchmarks


Task-Specific Questions

  1. What triggers entry to this sequence?
  2. What's the primary goal/conversion action?
  3. What do they already know about you?
  4. What other emails are they receiving?
  5. What's your current email performance?

Tool Integrations

For implementation, see the tools registry. Key email tools:

ToolBest ForMCPGuide
Customer.ioBehavior-based automation-customer-io.md
MailchimpSMB email marketing✓mailchimp.md
NitrosendAI-native email (sequences via prompts)✓nitrosend.md
ResendDeveloper-friendly transactional✓resend.md
SendGridTransactional email at scale-sendgrid.md
KitCreator/newsletter focused-kit.md

  • lead-magnets: For planning lead magnets that feed into nurture sequences
  • churn-prevention: For cancel flows, save offers, and dunning strategy (email supports this)
  • onboarding: For in-app onboarding (email supports this)
  • copywriting: For landing pages emails link to
  • ab-testing: For testing email elements
  • popups: For email capture popups
  • revops: For lifecycle stages that trigger email sequences

© coreyhaines31, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/emails of coreyhaines31/marketingskills.

  • SKILL.md
  • evals/evals.json
  • references/copy-guidelines.md
  • references/email-types.md
  • references/sequence-templates.md

Open the folder on GitHubat commit 1efedbc

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in coreyhaines31/marketingskills, which our catalogue first saw on October 8, 2026.

Compare with similar skills

Emails next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Emails compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Emails this skillcoreyhaines31/marketingskills54k1 repos~2.8kAutomated safety check: PassMIT
Email Marketing BibleCosmoBlk/email-marketing-bible3301 repos~6.8kAutomated safety check: PassMIT
Email Sequence Designeraaron-he-zhu/aaron-marketing-skills2.9k2 repos~4.2kAutomated safety check: PassApache-2.0
Email Generationextruct-ai/gtm-skills109—~1.7kAutomated safety check: PassNone
Social Selling Planneraaron-he-zhu/aaron-marketing-skills2.9k—~3.3kAutomated safety check: PassApache-2.0
56 Retargeting Plan Globalminhnv0807/ai-business-skills610—~2.8kAutomated safety check: PassMIT

Similar skills

  • Email Marketing Bible

    CosmoBlk/email-marketing-bible

    Data-backed email marketing skill for AI agents. An agent skill from CosmoBlk/email-marketing-bible.

    330 GitHub starsUsed in 1 repo~6.8k tokens
    Marketing & SEOAuto-check passed
  • Email Sequence Designer

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound…

    2.9k GitHub starsUsed in 2 repos~4.2k tokens
    Marketing & SEOAuto-check passed
  • Email Generation

    extruct-ai/gtm-skills

    Render a cold-outreach email sequence from a fixed template set and a contact CSV whose input fields are already filled.

    109 GitHub stars~1.7k tokensUpdated 11 days ago
    Marketing & SEOAuto-check passed
  • Social Selling Planner

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "set up my founder social-selling routine", "build a daily engagement block for target accounts", or "turn funding / hiring signals into selling plays"…

    2.9k GitHub stars~3.3k tokensUpdated today
    Marketing & SEOAuto-check passed
  • 56 Retargeting Plan Global

    minhnv0807/ai-business-skills

    A skill your agent uses when warm audiences need a plan — retargeting tiers by intent and recency, a different message per tier, frequency caps, attribution windows, lookalike seeds, exclusion…

    610 GitHub stars~2.8k tokensUpdated 27 days ago
    Marketing & SEOAuto-check passed
  • Suede Emails

    JasonColapietro/suede-creator-skills

    Suede-owned lifecycle email design for welcome, onboarding, nurture, re-engagement, post-purchase, and trigger-based sequences.

    127 GitHub stars~2.5k tokensUpdated today
    Marketing & SEOAuto-check passed

More from coreyhaines31/marketingskills

All 21 skills in this repo
  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Auto-check passed
  • Ab Testing

    coreyhaines31/marketingskills

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.

    54k GitHub starsUsed in 3 repos~3.1k tokens
    Auto-check passed
  • Referrals

    coreyhaines31/marketingskills

    When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.

    54k GitHub starsUsed in 2 repos~2.6k tokens
    Auto-check passed
  • Aso

    coreyhaines31/marketingskills

    When the user wants to audit or optimize an App Store or Google Play listing.

    54k GitHub starsUsed in 1 repo~4k tokens
    Auto-check passed
  • Paywalls

    coreyhaines31/marketingskills

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.

    54k GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Lead Magnets

    coreyhaines31/marketingskills

    When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation.

    54k GitHub starsUsed in 5 repos~2.8k tokens
    Auto-check passed

Categories

Questions about Emails

What does Emails do?

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Emails is an agent skill from coreyhaines31/marketingskills. When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

When should I use Emails?

Emails fits situations like: wants to create; optimize an email sequence; automated email flow; lifecycle email program.

How do I install Emails in Claude Code?

Run `npx skills add coreyhaines31/marketingskills --skill emails -a claude-code`. Or copy the skill folder (skills/emails in coreyhaines31/marketingskills) into .claude/skills/emails in your project. Claude Code loads it when a task matches its description.

How do I install Emails in Codex?

Run `npx skills add coreyhaines31/marketingskills --skill emails -a codex`. Or copy the skill folder (skills/emails in coreyhaines31/marketingskills) into .agents/skills/emails in your project. Codex loads it when a task matches its description.

Can I use Emails in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coreyhaines31/marketingskills --skill emails -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/emails, .gemini/skills/emails, .github/skills/emails and .opencode/skills/emails in your project.

What does Emails need to run?

SKILL.md names no scripts, command-line tools or credentials: Emails is instructions for the agent only.

Does Emails access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Emails safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Emails use?

Emails is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Emails use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.1k tokens, read only when the agent opens those files.

What are the alternatives to Emails?

Skills that share tags, products or a category with Emails: Email Marketing Bible (CosmoBlk/email-marketing-bible, 330 stars), Email Sequence Designer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Email Generation (extruct-ai/gtm-skills, 109 stars) and Social Selling Planner (aaron-he-zhu/aaron-marketing-skills, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Emails?

coreyhaines31 (a GitHub user) maintains it in coreyhaines31/marketingskills, which has 53,831 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

Source: coreyhaines31/marketingskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.