agentleFS
CodeAlive-AICodeAlive-AI/ceo-ai-os/skills/email-sequence/SKILL.md

email-sequence

Skill9 starsChanged 6 months agoMITView on GitHub

Create or optimize email sequences, drip campaigns, nurture flows, onboarding emails, welcome series, re-engagement emails. Use for "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome series," "what emails should I send," "email cadence." For web page copy, see copywriting. For in-app onboarding, see user-onboarding.

81 other projects use a version of this, 58 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • silvainfmSkill

    paid-ads

    When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.

    Also in 39 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • silvainfmSkill

    competitor-alternatives

    When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.

    Also in 34 projects that use this

  • +6 more from nicepkg

The file

We split this skill into the rules it gives an agent

5 rules. 2 are common, 2 are distinctive, and 1 is very specific to this project.

  • 2

    Common

    Most of the 79 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.

    line 9
  2. Distinctive:

    Follow output preferences from USER.md (language, format, platform constraints).

    line 11
  3. Common:

    Before creating a sequence, understand:

    line 21
  4. Distinctive:

    Every email moves them somewhere.

    line 58
  5. Common:

    Don't repeat subject line, complete the thought

    line 150

“Common” is measured: kept by at least 6 in 10 of the 79 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

[YOUR_PRODUCT] Context

Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint. Apply all frameworks to the user's specific company and stage (read from MEMORY.md). Follow output preferences from USER.md (language, format, platform constraints). For chat platforms: max 15 lines, no markdown tables, be concrete and actionable.

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

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.

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. Make next steps obvious.


Sequence Types

Welcome Sequence (Post-Signup)

Length: 5-7 emails over 12-14 days

  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

  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

  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 Note: Coordinate with in-app onboarding

  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, key step reminders, new user invites

Retention Emails

  • Upgrade to paid, ask for review, proactive support, usage reports, NPS survey, referral program

Billing Emails

  • Switch to annual, failed payment recovery, cancellation survey, renewal reminders

Usage Emails

  • Daily/weekly/monthly summaries, milestone celebrations

Win-Back Emails

  • Expired trials, cancelled customers

Campaign Emails

  • Monthly roundup, product updates, industry news

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


Subject Line Strategy

  • Clear > Clever, Specific > Vague
  • Benefit or curiosity-driven, 40-60 characters ideal

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

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

Length

  • 50-125 words for transactional
  • 150-300 words for educational
  • 300-500 words for story-driven

CTA Guidelines

  • Buttons for primary actions
  • One clear primary CTA per email
  • Button text: Action + outcome

For detailed copy 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]

Related Skills

  • outreach-sender — for cold outreach send/track (not lifecycle sequences)
  • pipeline-manager — nurture sequences for pipeline prospects
  • copywriting — for landing pages emails link to
  • humanizer — polish email copy to remove AI patterns
  • user-onboarding — for in-app onboarding (email supports this)
  • founder-sales — for sales-oriented email outreach

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.