Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

email-sequence电子邮件序列

Agent Skill

email-sequence 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,327

周安装

57

GitHub Stars

103

下载量

465
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:email-sequence(电子邮件序列)
来源仓库:https://github.com/borghei/claude-skills
仓库路径:skills/email-sequence
安装命令:
npx skills add https://github.com/borghei/claude-skills --skill email-sequence
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill email-sequence

简介

email-sequence 设计端到端电子邮件自动化流,聚焦关系培育与转化动作驱动。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中构建 onboarding、 nurture 与生命周期邮件序列。
  • 每封邮件包含主题行、预览文本、正文、CTA 及时机策略,附带退出条件设定。
  • 安装命令:npx skills add https://github.com/borghei/claude-skills --skill email-sequence。
  • 使用前应确认权限范围、维护状态及是否会触发邮件发送或网络请求操作。

SKILL.md

Email Sequence Design

Category: Marketing Tags: email sequences, drip campaigns, nurture flows, onboarding emails, lifecycle marketing, automation

Overview

Email Sequence Design creates complete, ready-to-implement email automation flows. Every output includes subject lines, preview text, full body copy, CTAs, send timing, and exit conditions. The goal is sequences that nurture relationships and drive specific conversion actions -- not just "stay top of mind" email noise.

This skill writes the sequences. For email HTML templates and rendering infrastructure, use email-template-builder. For tracking email performance, use analytics-tracking.


Sequence Types

TypeTriggerGoalTypical Length
Welcome/OnboardingNew signupActivate user, show core value5-7 emails over 14 days
Trial ExpirationTrial nearing endConvert to paid4-5 emails over 7 days
Lead NurtureContent download, webinarQualify and convert6-8 emails over 30 days
Re-engagementInactive 30+ daysBring back or clean list3-4 emails over 14 days
Post-PurchaseSubscription startReduce churn, expand4-6 emails over 30 days
Event-BasedSpecific user actionDrive next action2-3 emails over 7 days
Sales (Warm)MQL or PQL signalBook meeting or start trial4-5 emails over 14 days

Design Process

Step 1: Define Sequence Architecture

Before writing any email, define the architecture:

Sequence Name:     [Name]
Trigger:           [What starts the sequence]
Primary Goal:      [Single conversion action]
Secondary Goals:   [Relationship building, data collection]
Length:            [Number of emails]
Duration:          [Total time span]
Exit Conditions:   [When they leave the sequence]
Suppression:       [Other sequences to suppress while active]

Step 2: Map the Emotional Journey

Each email serves a purpose in a progression:

EmailEmotional StatePurposeKey Message
1Curious, uncertainWelcome, set expectations"Here's what to expect"
2Exploring, evaluatingDemonstrate core value"Here's the one thing to try first"
3Engaged or dropping offSocial proof"Here's how others succeeded"
4Considering commitmentRemove objections"Common concerns addressed"
5Ready to decideCreate urgency"Your trial ends in X days"

Step 3: Write Each Email

For every email in the sequence, deliver:

Email [#]: [Name/Purpose]
Send:     [Timing from trigger or previous email]
Segment:  [Conditions -- who receives this variant]

Subject:  [Subject line - under 50 characters]
Preview:  [Preview text - 80-120 characters, complements subject]

Body:
[Complete copy -- not an outline, not bullets, the actual words]

CTA:      [Button text] → [Destination URL]
P.S.:     [Optional -- works for urgency or human touch]

Step 4: Define Branching Logic

Not everyone follows the same path. Define branches:

After Email 2:
  IF user activated core feature → Skip to Email 4 (post-activation)
  IF user has not logged in → Send Email 2B (re-engagement variant)
  IF user unsubscribed → Exit sequence

After Email 4:
  IF user converted → Exit sequence, enter post-purchase sequence
  IF user visited pricing 2+ times → Send Email 4B (pricing objection handler)
  ELSE → Continue to Email 5

Sequence Blueprints

Blueprint: SaaS Welcome/Onboarding (7 emails, 14 days)

EmailDaySubjectPurpose
10 (immediate)Welcome to [Product] -- start hereSet expectations, one CTA to activate
21The one feature that changes everythingDrive to core value action
33How [Company] got [Result] in [Timeframe]Social proof, case study
45Quick questionCheck engagement, offer help
573 things you might have missedFeature discovery, breadth
610Your trial is halfway doneProgress report, urgency
713Last day of your trialConvert or lose access

Exit conditions: User converts to paid at any point, user unsubscribes, user explicitly requests removal.

Branching:

  • After Email 2: If user completed core action, skip Email 3, go to Email 4
  • After Email 4: If user has not logged in for 5+ days, switch to re-engagement variant
  • After Email 6: If user visited pricing page, send pricing-focused Email 7 variant

Blueprint: Lead Nurture (6 emails, 30 days)

EmailDaySubjectPurpose
10Your [resource name] is readyDeliver promised content
23The mistake most [role] make with [topic]Educational, establish authority
37[Company] went from [problem] to [result]Case study, social proof
414The [topic] framework we use internallyExclusive value, reciprocity
521Quick question about [their challenge]Personal, segmentation
628See if [Product] is right for youSoft CTA, demo or trial

Exit conditions: Books demo, starts trial, unsubscribes, or completes sequence.

Blueprint: Re-engagement (4 emails, 14 days)

EmailDaySubjectPurpose
10We noticed you've been awayAcknowledge absence, show value
23Here's what you missedProduct updates, new features
37[Exclusive offer or incentive]Incentivize return
414Should we stop emailing you?Clean list, last chance

Critical rule: If no engagement after Email 4, remove from active email list. Sending to unengaged contacts damages sender reputation.

Blueprint: Trial Expiration (5 emails, 7 days)

EmailDay Before ExpirySubjectPurpose
17Your trial ends in one weekAwareness, usage summary
23Here's what you'll lose access toLoss aversion, feature list
31Tomorrow is your last dayUrgency, simple CTA
40Your trial just endedConversion, offer extension option
5+3We saved your data for 30 daysLast chance, data retention

Subject Line Framework

Formulas That Work

FormulaExampleWhy It Works
How [company] [achieved result]"How Stripe reduced churn 23%"Specific, curiosity, social proof
The [number] [thing] [audience] [needs]"The 3 metrics every PM tracks"Specific, relevant, scannable
Quick question about [topic]"Quick question about your trial"Personal, non-threatening
[Name], [action-oriented statement]"Sarah, your dashboard is ready"Personal, action-oriented
Your [asset] is [status]"Your free trial ends tomorrow"Ownership, urgency

Subject Line Rules

  1. Under 50 characters (mobile truncation happens at 35-45)
  2. No ALL CAPS words
  3. No excessive punctuation (!!!)
  4. No spam trigger words in subject: free, guarantee, limited time, act now
  5. Preview text must complement, not repeat, the subject
  6. A/B test subject lines on every sequence (minimum 3 variants per email)

Timing & Cadence

Optimal Send Times (B2B SaaS)

DayTime WindowNotes
Tuesday9-11 AM recipient's timezoneHighest open rates
Wednesday9-11 AMSecond best
Thursday9-11 AMGood for follow-ups
Monday10 AM-12 PMAfter inbox clearing
FridayAvoid for important emailsLow engagement
WeekendAvoid for B2BException: consumer products

Sequence Spacing Rules

  • Welcome email: Immediate (within 5 minutes of trigger)
  • Onboarding emails: Every 1-3 days (maintain momentum)
  • Nurture emails: Every 3-7 days (avoid fatigue)
  • Re-engagement: Every 3-5 days (test urgency vs respect)
  • Trial expiration: Accelerating cadence (7 days, 3 days, 1 day, 0, +3)

Metrics & Benchmarks

Expected Performance by Sequence Type

MetricWelcomeNurtureRe-engagementTrial Expiration
Open rate50-70%25-40%15-25%40-60%
Click rate10-20%3-8%2-5%8-15%
Conversion rate5-15%1-3%3-8%10-25%
Unsubscribe rate<0.5%<0.3%1-3%<0.5%

Health Indicators

SignalMeaningAction
Open rate declining across sequenceFatigue or irrelevanceShorten sequence or improve subject lines
High opens, low clicksSubject works, body/CTA doesn'tRewrite body copy, simplify CTA
High click rate, low conversionLanding page problemAudit post-click experience
Rising unsubscribes after Email 3Too frequent or too salesyIncrease spacing, add more value
Email 1 open rate below 40%Deliverability issueCheck sender reputation, authentication

Segmentation Strategy

Behavioral Segments

SegmentDefinitionSequence Adjustment
Power usersUsed core feature 5+ timesSkip beginner content, focus on advanced features
Window shoppersSigned up, never activatedMore hand-holding, simpler first steps
Pricing page visitorsViewed pricing 2+ timesAddress pricing objections directly
Feature explorersUsed 3+ featuresHighlight integration and workflow value
Ghost usersNo login in 7+ daysRe-engagement sequence

Personalization Tiers

TierEffortImpactExample
1: Name + companyLowModerate"Hi Sarah, how's the Acme team finding..."
2: BehavioralMediumHigh"Since you set up your first project..."
3: Segment-specific copyHighHighestEntirely different email body per segment

Implementation Checklist

  • Sequence architecture documented (trigger, goal, length, exits)
  • All emails written with subject, preview, body, CTA
  • Branching logic defined for key decision points
  • Subject line A/B variants created (minimum 3 per email)
  • UTM parameters configured for all links
  • Suppression rules set (no overlapping sequences)
  • Unsubscribe handling confirmed (one-click, CAN-SPAM compliant)
  • Plain text version created for each email
  • Send time optimized for recipient timezone
  • Metrics dashboard configured (opens, clicks, conversions, unsubs)
  • 30-day post-launch review scheduled

Proactive Triggers

  • User mentions low trial-to-paid conversion: ask about trial expiration email sequence before recommending pricing changes
  • User reports high open rates but low clicks: diagnose body copy and CTA before blaming subject lines
  • User wants to "do email marketing": clarify sequence type before writing anything
  • User has a product launch coming: recommend coordinating launch email sequence with in-app messaging
  • User mentions list going cold: suggest re-engagement sequence before recommending acquisition spend

Related Skills

SkillUse When
email-template-builderBuilding HTML email templates and rendering infrastructure
analytics-trackingSetting up email click tracking and UTM attribution
launch-strategyCoordinating email sequences around product launches
content-creatorWriting landing page copy that email CTAs point to
ab-test-setupDesigning statistically valid email A/B tests

Troubleshooting

SymptomLikely CauseFix
Welcome email open rate below 40%Deliverability issue or weak subject lineCheck sender reputation and SPF/DKIM/DMARC. Test subject variants.
Open rates declining across sequenceFatigue or irrelevanceShorten sequence, improve subject lines, or add more value per email.
High opens, low clicksBody copy or CTA is weakRewrite body with stronger benefit and simplify CTA to one action.
High click rate, low conversionLanding page problemAudit post-click experience: message match, page speed, form friction.
Rising unsubscribes after email 3Too frequent or too salesyIncrease spacing between emails and add more educational content.
Emails clipped by GmailHTML template over 102KBUse render_size_analyzer.py from email-template-builder to reduce size.
Sequence not triggeringAutomation platform misconfigurationVerify trigger events, check suppression rules for conflicts.

Success Criteria

  • Welcome sequence open rate above 50% (benchmark: 50-70%)
  • Nurture sequence click-through rate above 3% (benchmark: 3-8%)
  • Trial expiration conversion rate above 10% (benchmark: 10-25%)
  • Unsubscribe rate below 0.5% per email (below 0.3% for nurture)
  • Every email has 3+ subject line A/B variants tested
  • Branching logic covers at least 2 behavioral segments per sequence
  • Sequence-level conversion rate (total conversions / initial sends) above 5%

Scope & Limitations

In Scope: Lifecycle email sequence design, copy, timing, branching logic, segmentation, and performance optimization for SaaS/B2B.

Out of Scope: Email HTML rendering (use email-template-builder), cold outreach sequences (use cold-email), marketing automation platform setup, transactional email infrastructure.

Limitations: Benchmarks are SaaS/B2B focused. Adjust thresholds for e-commerce, consumer, or other verticals.


Python Automation Tools

1. Subject Line Scorer (scripts/subject_line_scorer.py)

Scores sequence email subject lines for open-rate potential and auto-detects sequence type (welcome, trial, nurture, re-engagement).

python scripts/subject_line_scorer.py "Your trial ends tomorrow"
python scripts/subject_line_scorer.py --file subjects.txt --json

2. Sequence Mapper (scripts/sequence_mapper.py)

Generates a visual sequence map with timing, branching logic, and exit conditions from a sequence definition.

python scripts/sequence_mapper.py sequence_def.json
python scripts/sequence_mapper.py --sample --json

3. Performance Analyzer (scripts/performance_analyzer.py)

Analyzes email sequence metrics against benchmarks, identifies bottlenecks, and recommends optimizations.

python scripts/performance_analyzer.py metrics.json
python scripts/performance_analyzer.py --sample --json

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.74%
按下载量换算162

Claude

30.2%
按下载量换算140

Cursor

17.77%
按下载量换算83

Gemini CLI

9.31%
按下载量换算43

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills