Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

email-sequences电子邮件序列

Agent Skill

email-sequences 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

259

周安装

11

GitHub Stars

30

下载量

91
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/salesably/salesably-marketplace --skill email-sequences

简介

email-sequences 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。

  • 适用于电子邮件序列相关的代码协作、仓库管理和 Issue 处理等 GitHub 工作流任务。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。
  • 可结合来源仓库路径 skills/email-sequences 继续核验功能细节和使用边界。

SKILL.md

Email Sequences

This skill creates automated email sequences that move subscribers through the customer journey - from stranger to subscriber to customer to advocate.

Objective

Build email sequences that deliver the right message at the right time, nurturing relationships and driving conversions without manual effort.

Intake Questions

Before creating email sequences, gather context:

  1. Entry point: How do people join this sequence? (Lead magnet, purchase, signup)
  2. Desired outcome: What should they do after the sequence? (Buy, book, engage)
  3. Product/Offer: What are you eventually selling or promoting?
  4. Timeline: Over what period should the sequence run?
  5. Audience knowledge: How familiar are they with you/your solution?
  6. Objections: What prevents people from taking the desired action?
  7. Existing sequences: What automation already exists?

The 6 Sequence Types

1. Welcome Sequence

Trigger: New subscriber (lead magnet, newsletter signup) Goal: Build relationship, set expectations, introduce brand Length: 3-7 emails over 1-2 weeks

Email structure:

  1. Email 1 (Immediate): Deliver promised content + set expectations
  2. Email 2 (Day 1-2): Share your story/origin
  3. Email 3 (Day 3-4): Deliver unexpected value (bonus content)
  4. Email 4 (Day 5-7): Social proof + best content
  5. Email 5 (Day 7-10): Soft intro to paid offer (optional)

Key principles:

  • Deliver on lead magnet promise immediately
  • Set email frequency expectations
  • Show personality and build connection
  • Don't hard sell too early

2. Nurture Sequence

Trigger: After welcome sequence ends Goal: Stay top of mind, continue providing value Length: Ongoing, 1-4 emails per week

Content rotation:

  • Educational content
  • Case studies and examples
  • Behind-the-scenes
  • Curated resources
  • Occasional promotional content (20% max)

Key principles:

  • Maintain consistent schedule
  • 80/20 rule: 80% value, 20% promotional
  • Segment based on engagement
  • Re-engage inactive subscribers

3. Conversion Sequence

Trigger: Interest signal (page visit, link click, webinar signup) Goal: Convert interest to purchase Length: 4-7 emails over 5-10 days

Email structure:

  1. Email 1: Acknowledge interest, expand on benefits
  2. Email 2: Handle main objection #1
  3. Email 3: Case study/success story
  4. Email 4: Handle main objection #2
  5. Email 5: FAQ compilation
  6. Email 6: Urgency/scarcity (if real)
  7. Email 7: Last chance + final push

Key principles:

  • One email, one focus
  • Address objections directly
  • Use social proof strategically
  • Create urgency without being sleazy

4. Launch Sequence

Trigger: Product launch or promotion period Goal: Maximize sales during limited window Length: 7-14 emails over launch period

Three phases:

Pre-Launch (3-5 emails):

  • Build anticipation
  • Warm up to the offer
  • Share relevant content
  • Hint at what's coming

Launch Week (4-7 emails):

  1. Doors open + full details
  2. Deep dive on specific benefit
  3. Case study/proof
  4. FAQ + objection handling
  5. Bonuses (if applicable)
  6. Urgency: limited time/spots
  7. Final hours + cart close

Post-Launch (2-3 emails):

  • Thank buyers, onboard them
  • Waitlist for non-buyers
  • Reset expectations

5. Onboarding Sequence

Trigger: New purchase/signup Goal: Help customers succeed and reduce churn Length: 5-10 emails over first 30 days

Email structure:

  1. Email 1 (Immediate): Welcome + quick start guide
  2. Email 2 (Day 1): First milestone to complete
  3. Email 3 (Day 3): Common mistake to avoid
  4. Email 4 (Day 5): Success story inspiration
  5. Email 5 (Day 7): Check-in + support offer
  6. Emails 6-10: Progressive feature introduction

Key principles:

  • Focus on one action per email
  • Celebrate early wins
  • Anticipate confusion points
  • Make support easy to access

6. Re-engagement Sequence

Trigger: Inactive subscriber (30-90 days no opens) Goal: Win back or clean list Length: 3-5 emails over 1-2 weeks

Email structure:

  1. Email 1: "We miss you" + best content
  2. Email 2: "What's changed" + new value
  3. Email 3: Incentive or exclusive offer
  4. Email 4: "Last chance before we part ways"
  5. Email 5: Goodbye + unsubscribe

Key principles:

  • Acknowledge the gap honestly
  • Lead with value, not guilt
  • Give a real reason to re-engage
  • Clean list if no response

Email Structure Template

Each email should follow this structure:

Subject Line

  • See newsletter skill for formulas
  • Test curiosity vs. clarity

Preview Text

  • First 40-90 characters
  • Complement (don't repeat) subject line

Opening Hook (First 1-3 lines)

  • Pattern interrupt
  • Story hook
  • Surprising statement
  • Direct question

Body

  • One main idea
  • Conversational tone
  • Short paragraphs (1-3 sentences)
  • Use "you" more than "I"

Call to Action

  • Single, clear CTA
  • Benefit-focused button text
  • Link multiple times if needed

P.S.

  • Second CTA or curiosity hook
  • High readership area - use it

Timing & Spacing Guidelines

Sequence TypeSpacingBest Send Times
WelcomeDays 0, 1, 3, 5, 7Immediate + morning
Nurture2-3x per weekTue/Wed/Thu morning
ConversionDaily during push10am or 7pm
LaunchDaily + urgency stacks10am + 5pm on close
OnboardingDays 0, 1, 3, 5, 7, 14, 21, 30Matches product usage
Re-engagementDays 0, 3, 7, 10, 14Morning, mid-week

Personalization Triggers

Advanced automation based on behavior:

TriggerAction
Opened 5+ emailsMove to engaged segment
Clicked pricing pageStart conversion sequence
Abandoned cartCart recovery sequence
PurchasedOnboarding sequence
No opens in 30 daysRe-engagement sequence
Clicked specific topicTopic-specific content

Output Format

When creating email sequences, deliver:

  1. Sequence Map: Visual flow showing triggers and emails
  2. Email Briefs: For each email - goal, subject options, key points
  3. Full Email Copy: Complete copy for each email in sequence
  4. Timing Schedule: When each email sends
  5. Success Metrics: What to track (opens, clicks, conversions)
  6. Segmentation Recommendations: How to split audiences

Cross-References

  • Apply brand-voice for consistent tone across all emails
  • Use lead-magnet to inform welcome sequence delivery
  • direct-response-copy techniques apply to conversion emails
  • newsletter handles broadcast vs. automated (this skill)
  • Launch sequences may promote offers from lead-magnet
  • orchestrator routes here for email marketing projects

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.29%
按下载量换算33

Claude

32.67%
按下载量换算30

Cursor

17.44%
按下载量换算16

Gemini CLI

9.21%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills