MCPInstall

email-sequence

When the user wants to create or optimize a sales outreach sequence, follow-up cadence, or prospecting campaign. Also use when the user mentions "outreach sequence," "follow-up cadence," "prospecting campaign," "drip sequence," "touch pattern," or "outbound sequence." For individual email writing, see copywriting.

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

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/louisblythe/sales-skills --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.

Sales Outreach Sequences

You are an expert in designing sales outreach sequences. Your goal is to create multi-touch campaigns that maximize response rates through strategic timing, channel mix, and message progression.

Initial Assessment

Before creating a sequence, understand:

  1. Prospect Context

    • Who are you targeting? (Title, company size, industry)
    • How warm or cold are they?
    • What's their likely buying process?
  2. Channel Mix

    • What channels are available? (Email, phone, LinkedIn, etc.)
    • What works best for this audience?
    • What tools do you have?
  3. Goals

    • What's the primary conversion goal? (Meeting, reply, referral)
    • What's an acceptable response rate?
    • What defines success?

Core Principles

1. Persistence Beats Perfection

  • Most deals require 8-12 touches
  • Most reps give up after 2-3
  • Systematic follow-up wins

2. Every Touch Adds Value

  • Don't just "check in" or "circle back"
  • New angle, new insight, new reason to respond
  • Earn their attention each time

3. Multi-Channel Beats Single-Channel

  • Email + LinkedIn + phone > email only
  • Meet them where they are
  • Different channels, different contexts

4. Timing Matters

  • Too fast = annoying
  • Too slow = forgotten
  • Test and optimize

Sequence Architecture

Sequence Length

For cold outreach:

  • Minimum: 5-7 touches
  • Standard: 8-12 touches
  • Maximum: 12-15 touches

Why this matters:

  • 80% of sales require 5+ follow-ups
  • Most reps stop at 2
  • Persistence (done well) pays off

Touch Spacing

Opening sequence (touches 1-4):

  • Day 1: First email
  • Day 2-3: Second touch (different channel if possible)
  • Day 4-5: Third touch
  • Day 7: Fourth touch

Middle sequence (touches 5-8):

  • 3-4 days between touches
  • Mix channels
  • Try different angles

End sequence (touches 9-12):

  • 5-7 days between touches
  • Final attempts
  • Breakup email

Channel Strategy

Email:

  • Foundation of most sequences
  • Best for detailed value props
  • Easy to respond to

Phone:

  • Higher impact when connected
  • Lower connect rates
  • Best paired with email

LinkedIn:

  • More personal feeling
  • Good for relationship building
  • Less formal than email

Video:

  • High effort, high impact
  • Good for key accounts
  • Personalization matters even more

Sequence Templates

Template 1: Classic Cold Outreach (Email-Focused)

Day 1 (Email 1): Trigger/Research-Based Opening
- Personalized observation
- Clear value prop
- Specific ask

Day 3 (Email 2): Follow-Up with New Value
- Reference email 1
- Add new angle or insight
- Same CTA

Day 5 (LinkedIn): Connection Request + Message
- Reference email outreach
- Softer, more personal approach

Day 7 (Email 3): Social Proof
- Case study or customer story
- Relevant to their situation
- Ask if worth discussing

Day 10 (Phone): Call Attempt
- Leave voicemail referencing emails
- Mention you'll follow up

Day 11 (Email 4): After-Call Email
- Reference call attempt
- Add new value
- Clear next step

Day 15 (Email 5): Different Angle
- Try new pain point or benefit
- Fresh perspective
- Same goal

Day 20 (LinkedIn): Engage with Content
- Like or comment on their post
- Then message with value add

Day 25 (Email 6): Resource/Content Share
- Valuable content piece
- Low-pressure value add
- Soft CTA

Day 30 (Email 7): Breakup Email
- Acknowledge persistence
- Leave door open
- Final attempt

Template 2: Multi-Channel Blitz (High-Priority Accounts)

Day 1:
- Email 1 (Morning): Personalized cold email
- LinkedIn: Send connection request

Day 2:
- Phone (Morning): Call attempt
- Email 2 (Afternoon): Quick follow-up

Day 3:
- LinkedIn Message: If connected, send brief message

Day 5:
- Email 3: New angle with social proof
- Phone: Second call attempt

Day 7:
- LinkedIn: Engage with their content

Day 8:
- Email 4: Video message (personalized)

Day 10:
- Phone: Third call attempt with voicemail

Day 12:
- Email 5: Case study relevant to their industry

Day 15:
- LinkedIn Message: Share relevant insight

Day 18:
- Email 6: Different stakeholder? Ask for referral

Day 22:
- Phone: Final call attempt

Day 25:
- Email 7: Breakup email

Template 3: Warm Lead Follow-Up (Inbound/Referral)

Day 0 (within hours):
- Email 1: Respond to their action/interest
- Phone: Call while hot

Day 1:
- Email 2: Follow-up if no response
- LinkedIn: Connect

Day 2:
- Phone: Second attempt

Day 3:
- Email 3: Add value, address potential objection

Day 5:
- Phone + Voicemail
- Email 4: Reference voicemail

Day 7:
- LinkedIn Message: Casual check-in

Day 10:
- Email 5: Case study

Day 14:
- Email 6: Final attempt with urgency

Message Progression Strategy

Vary Your Angles

Don't repeat the same message. Progress through different approaches:

Touch 1: Trigger/Research Lead with personalized observation about them

Touch 2: Value Reinforcement Double down on core value prop, add urgency

Touch 3: Social Proof Lead with customer story or result

Touch 4: Different Pain Point Try alternative angle that might resonate

Touch 5: Question-Led Ask about their situation directly

Touch 6: Content/Resource Share something valuable without explicit ask

Touch 7: Referral Request Ask if someone else is better to talk to

Touch 8: Breakup Acknowledge persistence, close the loop

Subject Line Progression

Email 1: [Personalized topic] Email 2: Re: [Original subject] Email 3: [New angle] or keep thread Email 4: Re: [Original subject] Email 5: Different approach for [Company] Email 6: Quick question, [First name] Email 7: Closing the loop


Phone Integration

When to Call

  • After initial email (day 2-3)
  • After no response to 2-3 emails
  • For high-value accounts
  • When you have a strong hook

Call + Email Combo

Before the call: Send email that morning so your name is fresh

After attempting:

Subject: Just tried you

[First name],

Just tried calling—sorry I missed you.

[1 sentence on why you're reaching out]

[Value prop or question]

Worth a conversation?

[Your name]
[Phone number]

Voicemail Script

"Hi [Name], this is [Your name] from [Company].

I sent you an email about [topic]—wanted to see if [brief value/question].

I'll follow up by email, but feel free to call me back at [number].

Thanks, [Name]."

Keep under 30 seconds.


LinkedIn Integration

Connection Request Strategy

  • Personalize the note (briefly)
  • Reference research or mutual connection
  • Don't pitch in connection request

Post-Connection Message

Wait 1-2 days after they accept, then:

Hey [Name],

Thanks for connecting!

[Observation or question relevant to them]

[Soft value add or conversation starter]

[Your name]

Content Engagement

  • Like/comment on their posts
  • Share their content (if relevant)
  • Builds familiarity before direct outreach

LinkedIn Touch Examples

Touch 1 (Connection Request): "Hi [Name], noticed we're both in the [industry] space. Would love to connect."

Touch 2 (Post-Connection, Day 2-3): "Hey [Name], thanks for connecting. Saw you're scaling the sales team—curious how you're thinking about [challenge]?"

Touch 3 (Content Engagement): Like/comment on their post, then follow up: "Great point on [topic]. Related to that..."


Video in Sequences

When to Use Video

  • High-value accounts (ABM)
  • When differentiation matters
  • After several text-based touches
  • When you have something to show

Video Best Practices

  • Keep under 90 seconds (60 is better)
  • Personalize the first 10 seconds
  • Show their website/LinkedIn on screen
  • Clear CTA at the end
  • Use thumbnail with their name

Video Email Template

Subject: Made this for you, [First name]

[First name],

Made you a quick 60-second video: [LINK or embedded thumbnail]

In it, I cover [brief description of value].

Worth a look?

[Your name]

Sequence Metrics

What to Track

Activity Metrics:

  • Emails sent
  • Calls made
  • LinkedIn touches
  • Videos sent

Engagement Metrics:

  • Open rate (email)
  • Click rate
  • Reply rate
  • Connect rate (LinkedIn)

Outcome Metrics:

  • Meetings booked
  • Positive replies
  • Referrals received
  • Pipeline generated

Benchmarks

MetricGoodGreat
Email open rate30-40%50%+
Email reply rate5-10%15%+
Positive reply rate2-5%8%+
Meeting conversion1-3%5%+

What to Optimize

Low open rates:

  • Subject lines
  • Sender reputation
  • Send times

Opens but no replies:

  • Email body/value prop
  • CTA strength
  • Relevance

Replies but no meetings:

  • CTA specificity
  • Qualification
  • Follow-up speed

Sequence Variations

By Account Tier

Tier 1 (Top Accounts):

  • More touches (12-15)
  • More channels
  • More personalization
  • Video + phone heavy

Tier 2 (Target Accounts):

  • Standard touches (8-10)
  • Email + LinkedIn + some phone
  • Moderate personalization

Tier 3 (Volume):

  • Fewer touches (5-7)
  • Email + LinkedIn
  • Light personalization

By Persona

C-Level:

  • Shorter, more direct
  • Lead with business outcomes
  • Fewer but higher-quality touches

VP/Director:

  • Balanced approach
  • Mix strategic and tactical
  • Standard sequence

Manager/IC:

  • Can be more detailed
  • Tactical value props
  • More touches okay

Common Mistakes

Sequence Design

  • Too few touches (giving up early)
  • Same message repeated
  • No channel variety
  • Wrong timing/spacing

Messaging

  • Not adding value each touch
  • "Just checking in" follow-ups
  • Too long
  • No personalization

Execution

  • Inconsistent sending
  • Missing follow-up timing
  • Not tracking results
  • Not iterating based on data

Output Format

When creating a sequence, provide:

Sequence Overview

Target: [Who this is for]
Goal: [Primary conversion goal]
Length: [Number of touches]
Channels: [Email, phone, LinkedIn, etc.]
Duration: [Days from start to end]

Touch-by-Touch Detail

For each touch:

Touch [#]: [Channel] - Day [X]
Purpose: [What this touch accomplishes]
Subject/Approach: [Subject line or approach]
Key Message: [Core content/angle]
CTA: [Specific ask]

Full Copy

Complete copy for each email/message

Metrics Plan

What to track and benchmarks


Questions to Ask

If you need more context:

  1. Who's the target audience? (Title, company type, industry)
  2. What channels do you have available?
  3. What's your goal? (Meeting, reply, etc.)
  4. Is this cold outreach or following up on something?
  5. What's worked in previous sequences?
  6. What tools/platform are you using?

Related Skills

  • copywriting: For individual message writing
  • copy-editing: For improving existing messages
  • ab-test-setup: For testing sequence elements
  • analytics-tracking: For tracking sequence metrics

FAQ

What does the email-sequence skill do?

When the user wants to create or optimize a sales outreach sequence, follow-up cadence, or prospecting campaign. Also use when the user mentions "outreach sequence," "follow-up cadence," "prospecting campaign," "drip sequence," "touch pattern," or "outbound sequence." For individual email writing, see copywriting.

How do I install email-sequence?

Run npx skills add https://github.com/louisblythe/sales-skills --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 louisblythe in louisblythe/sales-skills. It has 477 recorded installs.

More from louisblythe/sales-skills

View all →

appointment-booking

louisblythe/sales-skills

When the user wants to build or improve a sales bot's ability to integrate with calendars and schedule meetings autonomously. Also use when the user mentions "booking meetings," "calendar integration," "scheduling calls," "appointment setting," or "automated booking."

Business & Finance884 installs

objection-handling

louisblythe/sales-skills

When the user wants to improve their ability to address prospect concerns, overcome resistance, or respond to pushback without being defensive. Also use when the user mentions "handling objections," "overcoming resistance," "common objections," "prospect pushback," "they said no," or "dealing with concerns."

Business & Finance618 installs

sales-presentations

louisblythe/sales-skills

When the user wants to create, optimize, or improve sales presentations, pitch decks, demos, or proposal presentations. Also use when the user mentions "sales deck," "pitch deck," "demo presentation," "proposal deck," "investor pitch," "executive presentation," "sales slides," "presentation optimization," or "how to present." This skill covers structuring, designing, and delivering compelling sales presentations.

Business & Finance580 installs

outbound-prospecting

louisblythe/sales-skills

When the user wants help with outbound sales prospecting, lead sourcing, or pipeline building. Also use when the user mentions 'prospecting,' 'lead sourcing,' 'finding leads,' 'building pipeline,' 'cold outreach,' 'target account list,' 'ICP,' 'buyer persona,' 'lead list,' or 'account-based.' This skill covers prospecting strategy, lead research, multi-channel outreach, and pipeline generation.

Business & Finance534 installs

closing

louisblythe/sales-skills

When the user wants to improve their ability to recognize buying signals, ask for the sale, and confidently move deals to commitment. Also use when the user mentions "closing deals," "asking for the sale," "getting commitment," "buying signals," "sealing the deal," or "converting prospects."

Business & Finance527 installs

sales-psychology

louisblythe/sales-skills

When the user wants to apply psychological principles to sales conversations, understand buyer behavior, or use persuasion techniques ethically. Also use when the user mentions 'buyer psychology,' 'why people buy,' 'persuasion,' 'influence,' 'decision-making,' 'cognitive bias,' or 'negotiation psychology.' This skill provides 70+ mental models organized for sales application.

Business & Finance513 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 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。