← Back to Skills Marketplace
mariokarras

Email Sequence

by Mario Karras · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
166
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install abm-email-sequence
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...
README (SKILL.md)

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-context.md exists (or .claude/product-marketing-context.md 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

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


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:

Tool Best For MCP Guide
Customer.io Behavior-based automation - customer-io.md
Mailchimp SMB email marketing mailchimp.md
Resend Developer-friendly transactional resend.md
SendGrid Transactional email at scale - sendgrid.md
Kit Creator/newsletter focused - kit.md

Related Skills

  • churn-prevention: For cancel flows, save offers, and dunning strategy (email supports this)
  • onboarding-cro: For in-app onboarding (email supports this)
  • copywriting: For landing pages emails link to
  • ab-test-setup: For testing email elements
  • popup-cro: For email capture popups
  • revops: For lifecycle stages that trigger email sequences
Usage Guidance
This skill appears coherent and low-risk: it's instruction-only, asks for no credentials, and won't install code. Before installing, verify what (if anything) is stored in .agents/product-marketing-context.md or .claude/product-marketing-context.md in your agent workspace — the skill will read that file if present, and that file might contain sensitive business context. If that file might hold secrets or external credentials, either remove sensitive data from it or avoid giving this skill access. Otherwise it's safe to proceed, remembering that autonomous invocation is platform-default and this skill does not request extra privileges.
Capability Analysis
Type: OpenClaw Skill Name: abm-email-sequence Version: 1.0.0 The 'abm-email-sequence' skill bundle is a well-structured set of instructions and templates designed to help an AI agent create and optimize email marketing campaigns. The content across SKILL.md and the reference files (copy-guidelines.md, email-types.md, sequence-templates.md) is purely educational and functional, focusing on industry-standard email strategies like onboarding, lead nurturing, and re-engagement. No evidence of malicious intent, data exfiltration, or harmful prompt injections was found.
Capability Assessment
Purpose & Capability
The skill is an email-sequence authoring guide and all included templates, principles, and references align with that purpose. However, the runtime instructions tell the agent to read .agents/product-marketing-context.md (or .claude/product-marketing-context.md) if present — a local config path that is not listed in the skill's declared required config paths. Reading that file is plausibly relevant to producing tailored sequences, but the metadata omission is an inconsistency worth noting.
Instruction Scope
SKILL.md stays within the expected scope: it instructs the agent how to assess context, ask for missing info, and produce email sequences and templates. The only file-system action it prescribes is reading the product-marketing-context file before asking questions, which is reasonable for context-aware output but should be explicit in the metadata.
Install Mechanism
There is no install spec and no code to run — this is instruction-only, so nothing gets written to disk or downloaded. This is the lowest-risk install profile.
Credentials
The skill requests no environment variables, credentials, or external config paths in the manifest. The instructions also do not ask for API keys or secrets. The single file read it mentions is local/contextual and relevant to tailoring email content.
Persistence & Privilege
always is false and the skill does not request permanent presence or elevated privileges. It does not modify other skills or system configs; autonomous invocation is allowed by default but there are no additional privileges requested.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install abm-email-sequence
  3. After installation, invoke the skill by name or use /abm-email-sequence
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Major update: New strategic guide for any multi-email automated sequences (drip, onboarding, nurture, etc.). - Comprehensive frameworks for defining sequence type, audience, timing, and goals. - Best practices added for email copy, subject lines, CTAs, and segmentation. - Standardized output format for sequence overviews and individual emails. - Includes suggested measurement metrics and tool integration references. - Clear boundaries for when to use this skill versus cold-email or onboarding-cro.
Metadata
Slug abm-email-sequence
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Email Sequence?

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... It is an AI Agent Skill for Claude Code / OpenClaw, with 166 downloads so far.

How do I install Email Sequence?

Run "/install abm-email-sequence" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Email Sequence free?

Yes, Email Sequence is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Email Sequence support?

Email Sequence is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Email Sequence?

It is built and maintained by Mario Karras (@mariokarras); the current version is v1.0.0.

💬 Comments