Token导航 LogoToken导航TokenDH.com
开发只读github未标认证来源可访问clear审计通过

email-sequence电子邮件序列

Agent Skill

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

总安装

1,665

周安装

68

GitHub Stars

3

下载量

539
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

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

简介

email-sequence 处理 GitHub 仓库、Issue 和 Pull Request 信息,适合协作事项整理。

  • 适用于围绕代码变更、仓库状态和团队协作进行信息梳理的场景。
  • 通过 npx skills add 命令安装,需结合原始 README 核验具体用法。
  • 安装前建议确认权限范围、维护状态及是否触发联网或文件操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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

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

  1. Audience Context

- Who are they? - What triggered them into this sequence? - What do they already know/believe? - What's their current relationship with you?

  1. 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

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

Claude Code

27.16%
按下载量换算146

windsurf

21.96%
按下载量换算118

trae

20.13%
按下载量换算109

OpenCode

13.04%
按下载量换算70

Codex

8.42%
按下载量换算45

Antigravity

3.84%
按下载量换算21

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills