Creator · coreyhaines31
Last updated · Sep 3, 2026
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," "e
Creator · coreyhaines31
Last updated · Sep 3, 2026
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," "e
Creator · coreyhaines31
Last updated · Sep 3, 2026
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," "e
Creator · coreyhaines31
Last updated · Sep 3, 2026
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," "e
Review then install
Install targets
Codex install prompt
Install the "emails" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/emails. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"coreyhaines31-emails","task":"Install emails","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
SEO, content operations, lead generation, CRM, email automation, analytics, and growth workflows.
Scenario
Content automation
I need my agent to turn research and product updates into useful content drafts.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add coreyhaines31/marketingskills --skill emails
Maintenance
fresh
3d since push
Risk
Safe to try
No explicit security boundaries or instructions about handling sensitive data, but the skill only generates text and reads local context files, so risk is low.
GitHub quality
47K
93/100 Quality · 85/100 Trust
Coverage tags
Review notes
No explicit security boundaries or instructions about handling sensitive data, but the skill only generates text and reads local context files, so risk is low.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
ExcellentHigh-confidence pick with strong adoption and healthy maintenance signals.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Safe to tryA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
47K GitHub stars
Repo activity
47K stars, 7.3K forks
Maintenance
3d since push
License
MIT
Install
npx skills add coreyhaines31/marketingskills --skill emails
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add coreyhaines31/marketingskills --skill emailsDo not use when
Alternative
16.3K Stars
npx skills add hardikpandya/stop-slop --skill stop-slop
Alternative
37.4K Stars
npx skills add blader/humanizer --skill humanizer
Alternative
5.8K Stars
npx skills add petergyang/no-ai-slop --skill no-ai-slop
Alternative
4.8K Stars
npx skills add cursor/plugins --skill unslop
Agent safety v2
Good audit and safety signals with no high-risk permission hints in public metadata.
Review the audit page, then allow agent install in a sandboxed workflow.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/coreyhaines31-emails/install
Agent should check
Copy prompt
Task: Use emails in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/coreyhaines31-emails/install
Install command: npx skills add coreyhaines31/marketingskills --skill emails
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/coreyhaines31-emails/install
LLM text format
/api/skills/coreyhaines31-emails/install?format=text
Find alternatives
/api/skills/search?q=emails&limit=3
Agent prompt
Use emails for this task. Review https://www.openagentskill.com/api/skills/coreyhaines31-emails/install, then install with: npx skills add coreyhaines31/marketingskills --skill emailsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/coreyhaines31-emails
LLM text
/api/registry/manifest/coreyhaines31-emails?format=text
Install alias
/api/registry/install/coreyhaines31-emails
Recommend
/api/registry/recommend?task=Use%20emails%20in%20an%20agent%20workflow&limit=3
Agent fit
Workflow automation
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Workflow automation
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS47K GitHub stars
Stars/forks activity
PASS47K stars, 7.3K forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
High-confidence pick with strong adoption and healthy maintenance signals.
Workflow fit
Automate repeated work
I need my agent to automate a repeated workflow across tools and files.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Operate local tools
I need my agent to operate local files and desktop apps in a repeatable workflow.
Workflow fit
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Eliminates predictable AI writing patterns from prose while preserving specific meaning and reader trust.
Rewrites AI-sounding text so it reads naturally while preserving every factual claim and matching the writer's voice.
Audits or minimally edits drafts to remove named AI-writing patterns without flattening the author's voice.
Applies Cursor's prose-discipline rules to remove filler and AI writing tells from agent-facing and user-facing text.
--- 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 ---
# 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.
## 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](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](references/email-types.md)
---
## Email Copy Guidelines
### 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 human?
### 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](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](../../tools/REGISTRY.md). Key email tools:
| Tool | Best For | MCP | Guide | |------|----------|:---:|-------| | **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) | | **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) | | **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](../../tools/integrations/nitrosend.md) | | **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) | | **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) | | **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) |
---
## Related Skills
- **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
Source provenance
Decision snapshot
46,637 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for emails, ready for a manual X post.
A practical pick for market research: emails: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email progra... 46.6K stars https://www.openagentskill.com/skills/coreyhaines31-emails?ref=x
Listing + install path for emails: https://www.openagentskill.com/skills/coreyhaines31-emails?ref=x Install: npx skills add coreyhaines31/marketingskills --skill emails
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to coreyhaines31 but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-emails/audit)
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)coreyhaines31
@coreyhaines31
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
stop-slop
Eliminates predictable AI writing patterns from prose while preserving specific meaning and reader trust.
16.3K StarsHumanizer
Rewrites AI-sounding text so it reads naturally while preserving every factual claim and matching the writer's voice.
37.4K Starsno-ai-slop
Audits or minimally edits drafts to remove named AI-writing patterns without flattening the author's voice.
5.8K Starsunslop
Applies Cursor's prose-discipline rules to remove filler and AI writing tells from agent-facing and user-facing text.
4.8K StarsReview then install
Install targets
Codex install prompt
Install the "emails" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/emails. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"coreyhaines31-emails","task":"Install emails","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
SEO, content operations, lead generation, CRM, email automation, analytics, and growth workflows.
Scenario
Content automation
I need my agent to turn research and product updates into useful content drafts.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add coreyhaines31/marketingskills --skill emails
Maintenance
fresh
3d since push
Risk
Safe to try
No explicit security boundaries or instructions about handling sensitive data, but the skill only generates text and reads local context files, so risk is low.
GitHub quality
47K
93/100 Quality · 85/100 Trust
Coverage tags
Review notes
No explicit security boundaries or instructions about handling sensitive data, but the skill only generates text and reads local context files, so risk is low.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
ExcellentHigh-confidence pick with strong adoption and healthy maintenance signals.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Safe to tryA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
47K GitHub stars
Repo activity
47K stars, 7.3K forks
Maintenance
3d since push
License
MIT
Install
npx skills add coreyhaines31/marketingskills --skill emails
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add coreyhaines31/marketingskills --skill emailsDo not use when
Alternative
16.3K Stars
npx skills add hardikpandya/stop-slop --skill stop-slop
Alternative
37.4K Stars
npx skills add blader/humanizer --skill humanizer
Alternative
5.8K Stars
npx skills add petergyang/no-ai-slop --skill no-ai-slop
Alternative
4.8K Stars
npx skills add cursor/plugins --skill unslop
Agent safety v2
Good audit and safety signals with no high-risk permission hints in public metadata.
Review the audit page, then allow agent install in a sandboxed workflow.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/coreyhaines31-emails/install
Agent should check
Copy prompt
Task: Use emails in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/coreyhaines31-emails/install
Install command: npx skills add coreyhaines31/marketingskills --skill emails
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/coreyhaines31-emails/install
LLM text format
/api/skills/coreyhaines31-emails/install?format=text
Find alternatives
/api/skills/search?q=emails&limit=3
Agent prompt
Use emails for this task. Review https://www.openagentskill.com/api/skills/coreyhaines31-emails/install, then install with: npx skills add coreyhaines31/marketingskills --skill emailsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/coreyhaines31-emails
LLM text
/api/registry/manifest/coreyhaines31-emails?format=text
Install alias
/api/registry/install/coreyhaines31-emails
Recommend
/api/registry/recommend?task=Use%20emails%20in%20an%20agent%20workflow&limit=3
Agent fit
Workflow automation
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Workflow automation
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS47K GitHub stars
Stars/forks activity
PASS47K stars, 7.3K forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
High-confidence pick with strong adoption and healthy maintenance signals.
Workflow fit
Automate repeated work
I need my agent to automate a repeated workflow across tools and files.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Operate local tools
I need my agent to operate local files and desktop apps in a repeatable workflow.
Workflow fit
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Eliminates predictable AI writing patterns from prose while preserving specific meaning and reader trust.
Rewrites AI-sounding text so it reads naturally while preserving every factual claim and matching the writer's voice.
Audits or minimally edits drafts to remove named AI-writing patterns without flattening the author's voice.
Applies Cursor's prose-discipline rules to remove filler and AI writing tells from agent-facing and user-facing text.
--- 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 ---
# 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.
## 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](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](references/email-types.md)
---
## Email Copy Guidelines
### 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 human?
### 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](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](../../tools/REGISTRY.md). Key email tools:
| Tool | Best For | MCP | Guide | |------|----------|:---:|-------| | **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) | | **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) | | **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](../../tools/integrations/nitrosend.md) | | **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) | | **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) | | **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) |
---
## Related Skills
- **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
Source provenance
Decision snapshot
46,637 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for emails, ready for a manual X post.
A practical pick for market research: emails: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email progra... 46.6K stars https://www.openagentskill.com/skills/coreyhaines31-emails?ref=x
Listing + install path for emails: https://www.openagentskill.com/skills/coreyhaines31-emails?ref=x Install: npx skills add coreyhaines31/marketingskills --skill emails
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to coreyhaines31 but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-emails/audit)
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)coreyhaines31
@coreyhaines31
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
stop-slop
Eliminates predictable AI writing patterns from prose while preserving specific meaning and reader trust.
16.3K StarsHumanizer
Rewrites AI-sounding text so it reads naturally while preserving every factual claim and matching the writer's voice.
37.4K Starsno-ai-slop
Audits or minimally edits drafts to remove named AI-writing patterns without flattening the author's voice.
5.8K Starsunslop
Applies Cursor's prose-discipline rules to remove filler and AI writing tells from agent-facing and user-facing text.
4.8K StarsReview then install
Install targets
Codex install prompt
Install the "emails" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/emails. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"coreyhaines31-emails","task":"Install emails","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
SEO, content operations, lead generation, CRM, email automation, analytics, and growth workflows.
Scenario
Content automation
I need my agent to turn research and product updates into useful content drafts.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add coreyhaines31/marketingskills --skill emails
Maintenance
fresh
3d since push
Risk
Safe to try
No explicit security boundaries or instructions about handling sensitive data, but the skill only generates text and reads local context files, so risk is low.
GitHub quality
47K
93/100 Quality · 85/100 Trust
Coverage tags
Review notes
No explicit security boundaries or instructions about handling sensitive data, but the skill only generates text and reads local context files, so risk is low.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
ExcellentHigh-confidence pick with strong adoption and healthy maintenance signals.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Safe to tryA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
47K GitHub stars
Repo activity
47K stars, 7.3K forks
Maintenance
3d since push
License
MIT
Install
npx skills add coreyhaines31/marketingskills --skill emails
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add coreyhaines31/marketingskills --skill emailsDo not use when
Alternative
16.3K Stars
npx skills add hardikpandya/stop-slop --skill stop-slop
Alternative
37.4K Stars
npx skills add blader/humanizer --skill humanizer
Alternative
5.8K Stars
npx skills add petergyang/no-ai-slop --skill no-ai-slop
Alternative
4.8K Stars
npx skills add cursor/plugins --skill unslop
Agent safety v2
Good audit and safety signals with no high-risk permission hints in public metadata.
Review the audit page, then allow agent install in a sandboxed workflow.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/coreyhaines31-emails/install
Agent should check
Copy prompt
Task: Use emails in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/coreyhaines31-emails/install
Install command: npx skills add coreyhaines31/marketingskills --skill emails
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/coreyhaines31-emails/install
LLM text format
/api/skills/coreyhaines31-emails/install?format=text
Find alternatives
/api/skills/search?q=emails&limit=3
Agent prompt
Use emails for this task. Review https://www.openagentskill.com/api/skills/coreyhaines31-emails/install, then install with: npx skills add coreyhaines31/marketingskills --skill emailsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/coreyhaines31-emails
LLM text
/api/registry/manifest/coreyhaines31-emails?format=text
Install alias
/api/registry/install/coreyhaines31-emails
Recommend
/api/registry/recommend?task=Use%20emails%20in%20an%20agent%20workflow&limit=3
Agent fit
Workflow automation
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Workflow automation
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS47K GitHub stars
Stars/forks activity
PASS47K stars, 7.3K forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
High-confidence pick with strong adoption and healthy maintenance signals.
Workflow fit
Automate repeated work
I need my agent to automate a repeated workflow across tools and files.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Operate local tools
I need my agent to operate local files and desktop apps in a repeatable workflow.
Workflow fit
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Eliminates predictable AI writing patterns from prose while preserving specific meaning and reader trust.
Rewrites AI-sounding text so it reads naturally while preserving every factual claim and matching the writer's voice.
Audits or minimally edits drafts to remove named AI-writing patterns without flattening the author's voice.
Applies Cursor's prose-discipline rules to remove filler and AI writing tells from agent-facing and user-facing text.
--- 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 ---
# 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.
## 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](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](references/email-types.md)
---
## Email Copy Guidelines
### 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 human?
### 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](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](../../tools/REGISTRY.md). Key email tools:
| Tool | Best For | MCP | Guide | |------|----------|:---:|-------| | **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) | | **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) | | **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](../../tools/integrations/nitrosend.md) | | **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) | | **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) | | **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) |
---
## Related Skills
- **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
Source provenance
Decision snapshot
46,637 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for emails, ready for a manual X post.
A practical pick for market research: emails: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email progra... 46.6K stars https://www.openagentskill.com/skills/coreyhaines31-emails?ref=x
Listing + install path for emails: https://www.openagentskill.com/skills/coreyhaines31-emails?ref=x Install: npx skills add coreyhaines31/marketingskills --skill emails
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to coreyhaines31 but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-emails/audit)
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)coreyhaines31
@coreyhaines31
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
stop-slop
Eliminates predictable AI writing patterns from prose while preserving specific meaning and reader trust.
16.3K StarsHumanizer
Rewrites AI-sounding text so it reads naturally while preserving every factual claim and matching the writer's voice.
37.4K Starsno-ai-slop
Audits or minimally edits drafts to remove named AI-writing patterns without flattening the author's voice.
5.8K Starsunslop
Applies Cursor's prose-discipline rules to remove filler and AI writing tells from agent-facing and user-facing text.
4.8K StarsReview then install
Install targets
Codex install prompt
Install the "emails" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/emails. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"coreyhaines31-emails","task":"Install emails","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
SEO, content operations, lead generation, CRM, email automation, analytics, and growth workflows.
Scenario
Content automation
I need my agent to turn research and product updates into useful content drafts.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add coreyhaines31/marketingskills --skill emails
Maintenance
fresh
3d since push
Risk
Safe to try
No explicit security boundaries or instructions about handling sensitive data, but the skill only generates text and reads local context files, so risk is low.
GitHub quality
47K
93/100 Quality · 85/100 Trust
Coverage tags
Review notes
No explicit security boundaries or instructions about handling sensitive data, but the skill only generates text and reads local context files, so risk is low.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
ExcellentHigh-confidence pick with strong adoption and healthy maintenance signals.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Safe to tryA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
47K GitHub stars
Repo activity
47K stars, 7.3K forks
Maintenance
3d since push
License
MIT
Install
npx skills add coreyhaines31/marketingskills --skill emails
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add coreyhaines31/marketingskills --skill emailsDo not use when
Alternative
16.3K Stars
npx skills add hardikpandya/stop-slop --skill stop-slop
Alternative
37.4K Stars
npx skills add blader/humanizer --skill humanizer
Alternative
5.8K Stars
npx skills add petergyang/no-ai-slop --skill no-ai-slop
Alternative
4.8K Stars
npx skills add cursor/plugins --skill unslop
Agent safety v2
Good audit and safety signals with no high-risk permission hints in public metadata.
Review the audit page, then allow agent install in a sandboxed workflow.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/coreyhaines31-emails/install
Agent should check
Copy prompt
Task: Use emails in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20emails%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/coreyhaines31-emails/install
Install command: npx skills add coreyhaines31/marketingskills --skill emails
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/coreyhaines31-emails/install
LLM text format
/api/skills/coreyhaines31-emails/install?format=text
Find alternatives
/api/skills/search?q=emails&limit=3
Agent prompt
Use emails for this task. Review https://www.openagentskill.com/api/skills/coreyhaines31-emails/install, then install with: npx skills add coreyhaines31/marketingskills --skill emailsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/coreyhaines31-emails
LLM text
/api/registry/manifest/coreyhaines31-emails?format=text
Install alias
/api/registry/install/coreyhaines31-emails
Recommend
/api/registry/recommend?task=Use%20emails%20in%20an%20agent%20workflow&limit=3
Agent fit
Workflow automation
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Workflow automation
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS47K GitHub stars
Stars/forks activity
PASS47K stars, 7.3K forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
High-confidence pick with strong adoption and healthy maintenance signals.
Workflow fit
Automate repeated work
I need my agent to automate a repeated workflow across tools and files.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Operate local tools
I need my agent to operate local files and desktop apps in a repeatable workflow.
Workflow fit
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Eliminates predictable AI writing patterns from prose while preserving specific meaning and reader trust.
Rewrites AI-sounding text so it reads naturally while preserving every factual claim and matching the writer's voice.
Audits or minimally edits drafts to remove named AI-writing patterns without flattening the author's voice.
Applies Cursor's prose-discipline rules to remove filler and AI writing tells from agent-facing and user-facing text.
--- 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 ---
# 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.
## 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](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](references/email-types.md)
---
## Email Copy Guidelines
### 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 human?
### 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](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](../../tools/REGISTRY.md). Key email tools:
| Tool | Best For | MCP | Guide | |------|----------|:---:|-------| | **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) | | **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) | | **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](../../tools/integrations/nitrosend.md) | | **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) | | **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) | | **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) |
---
## Related Skills
- **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
Source provenance
Decision snapshot
46,637 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for emails, ready for a manual X post.
A practical pick for market research: emails: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email progra... 46.6K stars https://www.openagentskill.com/skills/coreyhaines31-emails?ref=x
Listing + install path for emails: https://www.openagentskill.com/skills/coreyhaines31-emails?ref=x Install: npx skills add coreyhaines31/marketingskills --skill emails
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to coreyhaines31 but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-emails/audit)
[](https://www.openagentskill.com/skills/coreyhaines31-emails?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)coreyhaines31
@coreyhaines31
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
stop-slop
Eliminates predictable AI writing patterns from prose while preserving specific meaning and reader trust.
16.3K StarsHumanizer
Rewrites AI-sounding text so it reads naturally while preserving every factual claim and matching the writer's voice.
37.4K Starsno-ai-slop
Audits or minimally edits drafts to remove named AI-writing patterns without flattening the author's voice.
5.8K Starsunslop
Applies Cursor's prose-discipline rules to remove filler and AI writing tells from agent-facing and user-facing text.
4.8K StarsPermission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness