MCPInstall

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 "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.

Installs
69
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/kimny1143/claude-code-template --skill email-sequence
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads email-sequence automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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
  • 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

Sequence Templates

Welcome Sequence (Post-Signup)

Email 1: Welcome (Immediate)

  • Subject: Welcome to [Product] — here's your first step
  • Deliver what was promised (lead magnet, access, etc.)
  • Single next action
  • Set expectations for future emails

Email 2: Quick Win (Day 1-2)

  • Subject: Get your first [result] in 10 minutes
  • Enable small success
  • Build confidence
  • Link to helpful resource

Email 3: Story/Why (Day 3-4)

  • Subject: Why we built [Product]
  • Origin story or mission
  • Connect emotionally
  • Show you understand their problem

Email 4: Social Proof (Day 5-6)

  • Subject: How [Customer] achieved [Result]
  • Case study or testimonial
  • Relatable to their situation
  • Soft CTA to explore

Email 5: Overcome Objection (Day 7-8)

  • Subject: "I don't have time for X" — sound familiar?
  • Address common hesitation
  • Reframe the obstacle
  • Show easy path forward

Email 6: Core Feature (Day 9-11)

  • Subject: Have you tried [Feature] yet?
  • Highlight underused capability
  • Show clear benefit
  • Direct CTA to try it

Email 7: Conversion (Day 12-14)

  • Subject: Ready to [upgrade/buy/commit]?
  • Summarize value
  • Clear offer
  • Urgency if appropriate
  • Risk reversal (guarantee, trial)

Lead Nurture Sequence (Pre-Sale)

Email 1: Deliver + Introduce (Immediate)

  • Deliver the lead magnet
  • Brief intro to who you are
  • Preview what's coming

Email 2: Expand on Topic (Day 2-3)

  • Related insight to lead magnet
  • Establish expertise
  • Light CTA to content

Email 3: Problem Deep-Dive (Day 4-5)

  • Articulate their problem deeply
  • Show you understand
  • Hint at solution

Email 4: Solution Framework (Day 6-8)

  • Your approach/methodology
  • Educational, not salesy
  • Builds toward your product

Email 5: Case Study (Day 9-11)

  • Real results from real customer
  • Specific and relatable
  • Soft CTA

Email 6: Differentiation (Day 12-14)

  • Why your approach is different
  • Address alternatives
  • Build preference

Email 7: Objection Handler (Day 15-18)

  • Common concern addressed
  • FAQ or myth-busting
  • Reduce friction

Email 8: Direct Offer (Day 19-21)

  • Clear pitch
  • Strong value proposition
  • Specific CTA
  • Urgency if available

Re-Engagement Sequence

Email 1: Check-In (Day 30-60 of inactivity)

  • Subject: Is everything okay, [Name]?
  • Genuine concern
  • Ask what happened
  • Easy win to re-engage

Email 2: Value Reminder (Day 2-3 after)

  • Subject: Remember when you [achieved X]?
  • Remind of past value
  • What's new since they left
  • Quick CTA

Email 3: Incentive (Day 5-7 after)

  • Subject: We miss you — here's something special
  • Offer if appropriate
  • Limited time
  • Clear CTA

Email 4: Last Chance (Day 10-14 after)

  • Subject: Should we stop emailing you?
  • Honest and direct
  • One-click to stay or go
  • Clean the list if no response

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
  • Match your brand but lean friendly
  • Read it out loud—does it sound human?

Length

  • Shorter is usually better
  • 50-125 words for transactional
  • 150-300 words for educational
  • 300-500 words for story-driven
  • If it's long, it better be good

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]"

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


Related Skills

  • onboarding-cro: For in-app onboarding (email supports this)
  • copywriting: For landing pages emails link to
  • ab-test-setup: For testing email elements

FAQ

What does the email-sequence skill do?

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," or "lifecycle emails." For in-app onboarding, see onboarding-cro.

How do I install email-sequence?

Run npx skills add https://github.com/kimny1143/claude-code-template --skill email-sequence in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/email-sequence/ (personal) or .claude/skills/email-sequence/ (project).

Which AI agents can use email-sequence?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is email-sequence safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains email-sequence?

It is published by kimny1143 in kimny1143/claude-code-template. It has 69 recorded installs.

More from kimny1143/claude-code-template

View all →

ui-ux-pro-max

kimny1143/claude-code-template

UI/UX design intelligence. Plan, build, design, implement, review, improve UI/UX code. Styles: image-first, editorial design, minimalism, dark mode, responsive. Projects: landing page, dashboard, SaaS, mobile app.

Frontend & Design4.7K installs

remotion

kimny1143/claude-code-template

Open the skill to read its SKILL.md instructions.

Media & Creative162 installs

ux-psychology

kimny1143/claude-code-template

Open the skill to read its SKILL.md instructions.

Frontend & Design114 installs

copywriting

kimny1143/claude-code-template

Open the skill to read its SKILL.md instructions.

Marketing & SEO89 installs

ios-app-store-submission

kimny1143/claude-code-template

Open the skill to read its SKILL.md instructions.

Mobile88 installs

marketing-psychology

kimny1143/claude-code-template

Open the skill to read its SKILL.md instructions.

Marketing & SEO82 installs

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。