跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 emails

Emails

当用户想要创建或优化电子邮件序列,滴入运动,自动电子邮件流,或生命周期电子邮件程序时. 用户提及"电子邮件序列","打扫运动","内脏序列","登机邮件序列","欢迎邮件序列","重新接触邮件","电子邮件自动化","生命周期邮件","基于触发的邮件","电子邮件漏斗","电子邮件工作流程","我应该发送什么邮件","欢迎邮件系列"或"电子邮件cadence"时也使用. 用于任何多电子邮件自动流 。 电子邮件避免AI告诉像"它不是X,它是Y"揭示,"没有X,没有Y,没有Z"列表,和假'Re:'主题行. 关于冷通和出行序列,参见冷通. 关于上船的应用,参见上船.

76761 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

当用户想要创建或优化电子邮件序列,滴入运动,自动电子邮件流,或生命周期电子邮件程序时. 用户提及"电子邮件序列","打扫运动","内脏序列","登机邮件序列","欢迎邮件序列","重新接触邮件","电子邮件自动化","生命周期邮件","基于触发的邮件","电子邮件漏斗","电子邮件工作流程","我应该发送什么邮件","欢迎邮件系列"或"电子邮件cadence"时也使用. 用于任何多电子邮件自动流 。 电子邮件避免AI告诉像"它不是X,它是Y"揭示,"没有X,没有Y,没有Z"列表,和假'Re:'主题行. 关于冷通和出行序列,参见冷通. 关于上船的应用,参见上船.

何时用

用户提到"电子邮件序列","滴答活动","泌尿序列","登机邮件序列","欢迎邮件序列","重新接触邮件","电子邮件自动化","生命周期邮件","基于触发的邮件","电子邮件漏斗","电子邮件工作流程","我应该发送什么邮件","欢迎邮件序列"

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Email Sequence Design、Reference Routing、Initial Assessment、Core Principles、1. One Email, One Job、2. Value Before Ask。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/sequence-templates.md、references/email-types.md、references/copy-guidelines.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

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," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. Emails avoid AI tells like 'it's not X, it's Y' reveals, 'no X, no Y, no Z' lists, and fake 'Re:' subject lines. For cold outreach and outbound sequences, see cold-email. For in-app onboarding, see onboarding.

Email Sequence DesignReference RoutingInitial AssessmentCore Principles1. One Email, One Job2. Value Before Ask3. Relevance Over Volume4. Clear Path ForwardEmail Sequence StrategySequence LengthTiming/DelaysSubject Line Strategy

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
emails
description
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," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. Emails avoid AI tells like 'it's not X, it's Y' reveals, 'no X, no Y, no Z' lists, and fake 'Re:' subject lines. For cold outreach and outbound sequences, see cold-email. For in-app onboarding, see onboarding.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 3
  • references/sequence-templates.md
  • references/email-types.md
  • references/copy-guidelines.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「emails」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-eec49f68df2ec3f1-Emails.html
请存为 .cursor/skills/emails/SKILL.md 或 .claude/skills/emails/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/coreyhaines31/marketingskills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/coreyhaines31/marketingskills' --list

npx skills add 'https://github.com/coreyhaines31/marketingskills' --skill 'emails'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: emails description: 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," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. Emails avoid AI tells like 'it's not X, it's Y' reveals, 'no X, no Y, no Z' lists, and fake 'Re:' subject lines. For cold outreach and outbound sequences, see cold-email. For in-app onboarding, see onboarding. metadata: version: 2.1.4

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.

Reference Routing

Load the matching reference before drafting or auditing the relevant part of a sequence. Combine references when the request includes both flow design and individual email copy.

| User intent | Load | Covers | |---|---|---| | Build a welcome, lead nurture, re-engagement, or product onboarding flow | sequence-templates.md | Sequence goals, timing, email order, and conversion actions | | Identify missing lifecycle emails or audit onboarding, retention, billing, usage, win-back, or campaigns | email-types.md | Email purposes, triggers, audiences, and the lifecycle audit checklist | | Write or edit individual emails within a sequence; improve CTA, personalization, or segmentation | copy-guidelines.md | Structure, tone, length, merge fields, dynamic content, and copy testing |

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Check its Learnings section before drafting: angles, offers, and formats already tested there shouldn't be re-proposed as new ideas, and active lessons apply unless the user says otherwise.

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

Email Sequence Strategy

Sequence Length

  • Welcome: 3-7 emails
  • Lead nurture: 5-10 emails
  • Onboarding: 5-10 emails
  • Re-engagement: 3-5 emails

Depends on:

  • Sales cycle length
  • Product complexity
  • Relationship stage

Timing/Delays

  • Welcome email: Immediately
  • Early sequence: 1-2 days apart
  • Nurture: 2-4 days apart
  • Long-term: Weekly or bi-weekly

Consider:

  • B2B: Avoid weekends
  • B2C: Test weekends
  • Time zones: Send at local time

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

Preview Text

  • Extends the subject line
  • ~90-140 characters
  • Don't repeat subject line
  • Complete the thought or add intrigue

Sequence Types Overview

Welcome Sequence (Post-Signup)

Length: 5-7 emails over 12-14 days Goal: Activate, build trust, convert

Key emails:

  1. Welcome + deliver promised value (immediate)
  2. Quick win (day 1-2)
  3. Story/Why (day 3-4)
  4. Social proof (day 5-6)
  5. Overcome objection (day 7-8)
  6. Core feature highlight (day 9-11)
  7. Conversion (day 12-14)

Lead Nurture Sequence (Pre-Sale)

Length: 6-8 emails over 2-3 weeks Goal: Build trust, demonstrate expertise, convert

Key emails:

  1. Deliver lead magnet + intro (immediate)
  2. Expand on topic (day 2-3)
  3. Problem deep-dive (day 4-5)
  4. Solution framework (day 6-8)
  5. Case study (day 9-11)
  6. Differentiation (day 12-14)
  7. Objection handler (day 15-18)
  8. Direct offer (day 19-21)

Re-Engagement Sequence

Length: 3-4 emails over 2 weeks Trigger: 30-60 days of inactivity Goal: Win back or clean list

Key emails:

  1. Check-in (genuine concern)
  2. Value reminder (what's new)
  3. Incentive (special offer)
  4. Last chance (stay or unsubscribe)

Onboarding Sequence (Product Users)

Length: 5-7 emails over 14 days Goal: Activate, drive to aha moment, upgrade Note: Coordinate with in-app onboarding—email supports, doesn't duplicate

Key emails:

  1. Welcome + first step (immediate)
  2. Getting started help (day 1)
  3. Feature highlight (day 2-3)
  4. Success story (day 4-5)
  5. Check-in (day 7)
  6. Advanced tip (day 10-12)
  7. Upgrade/expand (day 14+)

For detailed templates: See references/sequence-templates.md


Email Types by Category

Onboarding Emails

  • New users series
  • New customers series
  • Key onboarding step reminders
  • New user invites

Retention Emails

  • Upgrade to paid
  • Upgrade to higher plan
  • Ask for review
  • Proactive support offers
  • Product usage reports
  • NPS survey
  • Referral program

Billing Emails

  • Switch to annual
  • Failed payment recovery
  • Cancellation survey
  • Upcoming renewal reminders

Usage Emails

  • Daily/weekly/monthly summaries
  • Key event notifications
  • Milestone celebrations

Win-Back Emails

  • Expired trials
  • Cancelled customers

Campaign Emails

  • Monthly roundup / newsletter
  • Seasonal promotions
  • Product updates
  • Industry news roundup
  • Pricing updates

For detailed email type reference: See references/email-types.md


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
  • Read it out loud. Does it sound like a person?

No AI Tells

Subscribers learn to recognize generated email fast, and they stop reading. Write from the specific thing you want them to know or do.

Never write these:

  • Contrast reveals: "It's not X, it's Y." "Not because X. Because Y." State Y directly, with the reason.
  • Negation lists: "No X, no Y, no Z." Say what does happen. One plain absence ("No card required") is fine.
  • Trailing pile-ons: a full claim, then a comma and more restating clauses. End the sentence at the claim.
  • Self-answered questions and colon reveals: "The result? 3x faster." "The best part: it learns." FAQ questions and a question in the reader's own voice are fine.
  • Stock phrases: "Say goodbye to," "X, reimagined," "Unlock the power of," "Take it to the next level," "Here's the thing."
  • Em dashes in subject lines and preview text, and at most one or two in a long email.

Email-specific tells:

  • Subject-line bait: fake "Re:" or "Fwd:", "You won't believe...", "🔥 Big news." The subject should hold up if it's the only line they read.
  • Stock openers: "I hope this email finds you well," "Just checking in," "Great news!" Open with the reason you're writing.
  • Sign-off filler: "Feel free to reach out if you have any questions." Ask for one specific action, or end.

For the full blacklist, use the copywriting skill's AI-tells reference.

Length

  • 50-125 words for transactional
  • 150-300 words for educational
  • 300-500 words for story-driven

CTA Guidelines

  • Buttons for primary actions
  • Links for secondary actions
  • One clear primary CTA per email
  • Button text: Action + outcome

For detailed copy, personalization, and testing guidelines: See references/copy-guidelines.md


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


Task-Specific Questions

  1. What triggers entry to this sequence?
  2. What's the primary goal/conversion action?
  3. What do they already know about you?
  4. What other emails are they receiving?
  5. What's your current email performance?

Tool Integrations

For implementation, see the tools registry. Key email tools:

| Tool | Best For | MCP | Guide | |------|----------|:---:|-------| | Customer.io | Behavior-based automation | - | customer-io.md | | Mailchimp | SMB email marketing | ✓ | mailchimp.md | | Nitrosend | AI-native email (sequences via prompts) | ✓ | nitrosend.md | | Resend | Developer-friendly transactional | ✓ | resend.md | | SendGrid | Transactional email at scale | - | sendgrid.md | | Kit | Creator/newsletter focused | - | kit.md |


Related Skills

  • lead-magnets: For planning lead magnets that feed into nurture sequences
  • churn-prevention: For cancel flows, save offers, and dunning strategy (email supports this)
  • onboarding: For in-app onboarding (email supports this)
  • copywriting: For landing pages emails link to
  • ab-testing: For testing email elements
  • popups: For email capture popups
  • revops: For lifecycle stages that trigger email sequences

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…