email-write

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Email Write Sub-Skill

Email Write Sub-Skill

Purpose

用途

Generate professional, high-converting email copy using proven copywriting frameworks. Produces subject line variants with scoring, responsive HTML templates with dark mode support, plain-text fallback, and preheader recommendations.
使用成熟的文案撰写框架生成专业、高转化率的邮件文案。生成带评分的主题变体、支持深色模式的响应式HTML模板、纯文本备选方案以及预标题建议。

Activation

触发方式

This sub-skill is invoked by the main
/email
skill when the user needs to compose a new email.
当用户需要撰写新邮件时,主技能
/email
会调用此子技能。

Workflow

工作流程

1. Gather Context

1. 收集上下文

First, check if
email-profile.md
exists in the project directory. If yes, load business type, tone preferences, and target audience from the profile.
If no profile exists or user provides new context, ask for:
  • Email Purpose: cold outreach, newsletter, product launch, promotional, re-engagement, welcome, feature announcement, etc.
  • Recipient: name, role, relationship (new lead, existing customer, subscriber, team member)
  • Tone: professional, friendly, casual, authoritative, empathetic, enthusiastic
  • Business Type: (from profile or ask) SaaS, e-commerce, service business, agency, creator, B2B, B2C
  • Key Message: what action should the recipient take?
  • Additional Context: product details, promotion details, deadline, personalization data
首先检查项目目录中是否存在
email-profile.md
文件。若存在,则从该文件中加载业务类型、语气偏好和目标受众信息。
若不存在该文件,或用户提供了新的上下文,则询问以下信息:
  • 邮件用途:陌生开发信、新闻通讯、产品发布、促销活动、重新激活用户、欢迎邮件、功能公告等
  • 收件人:姓名、职位、关系(新潜在客户、现有客户、订阅者、团队成员)
  • 语气:专业、友好、随意、权威、共情、热情
  • 业务类型:(从配置文件获取或询问)SaaS、电商、服务型企业、代理机构、创作者、B2B、B2C
  • 核心信息:收件人需要执行什么操作?
  • 额外上下文:产品详情、促销信息、截止日期、个性化数据

2. Select Copy Framework

2. 选择文案框架

Based on the email purpose, choose the appropriate framework from
references/copy-frameworks.md
:
Email PurposeRecommended FrameworkWhy
Cold outreachPASEmpathy-driven, addresses pain points
Product launchAIDABuilds excitement, drives action
NewsletterBAB or AIDAAspirational or engaging storytelling
Feature announcementFABClear value proposition for features
Promotional/saleAIDACreates desire and urgency
Re-engagementPASIdentifies problem of disengagement
Welcome emailBABShows transformation journey
Case study4PsProof-heavy, testimonial-driven
Review requestPASEmpathetic ask for feedback
Appointment reminderDirectNo framework needed
If uncertain, default to AIDA for marketing emails or PAS for relationship emails.
根据邮件用途,从
references/copy-frameworks.md
中选择合适的框架:
邮件用途推荐框架原因
陌生开发信PAS共情导向,直击痛点
产品发布AIDA营造兴奋感,推动行动
新闻通讯BAB 或 AIDA富有吸引力的愿景式或故事化表达
功能公告FAB清晰呈现功能价值主张
促销/折扣活动AIDA激发欲望与紧迫感
用户重新激活PAS定位用户流失的问题
欢迎邮件BAB展示用户成长路径
案例研究4Ps重证据,依赖证言驱动
评价请求PAS共情式请求反馈
预约提醒直接表述无需使用框架
若不确定,营销类邮件默认使用AIDA,关系维护类邮件默认使用PAS

3. Generate Subject Lines

3. 生成主题行

Create 3 subject line variants using these strategies:
  1. Curiosity-Driven: Creates intrigue, open loop, question, teaser
  2. Benefit-Driven: Clear value proposition, outcome, result
  3. Urgency-Driven: Time-sensitive, scarcity, FOMO (but not spammy)
Subject Line Rules:
  • Optimal length: 6-10 words / 30-50 characters
  • Never use ALL CAPS
  • Maximum 1 exclamation mark per subject line
  • Avoid spam triggers: "FREE!!!", "Act Now", "Limited Time Only", "Guaranteed", "Cash", "No obligation"
  • Include personalization where possible (beyond first name: behavior, location, purchase history)
  • Use power words: exclusive, secret, insider, proven, breakthrough, transform, discover
Scoring Methodology (0-100):
CriteriaWeightScoring
Length20100 if 30-50 chars, -10 per 5 chars over/under
Power Words20+20 per power word (max 2)
Personalization25+25 if personalized beyond first name
Spam Triggers-50-50 if contains spam word
Clarity20100 if benefit/topic is clear
Curiosity15+15 if creates open loop
Minimum passing score: 70
使用以下策略创建3个主题行变体
  1. 好奇心驱动:制造悬念、开放式结尾、提问式、预告式
  2. 利益驱动:清晰的价值主张、成果导向
  3. 紧迫感驱动:限时、稀缺性、FOMO(但避免垃圾邮件风格)
主题行规则:
  • 最佳长度:6-10个单词 / 30-50个字符
  • 禁止全大写
  • 每个主题行最多使用1个感叹号
  • 避免垃圾邮件触发词:"FREE!!!"、"Act Now"、"Limited Time Only"、"Guaranteed"、"Cash"、"No obligation"
  • 尽可能加入个性化内容(不止于名字:行为、位置、购买历史)
  • 使用强力词汇:exclusive、secret、insider、proven、breakthrough、transform、discover
评分方法(0-100分):
评分标准权重评分规则
长度2030-50字符得100分,每超出/不足5字符扣10分
强力词汇20每个强力词汇加20分(最多2个)
个性化25若包含名字以外的个性化内容加25分
垃圾邮件触发词-50若包含触发词扣50分
清晰度20利益/主题清晰得100分
好奇心15制造开放式悬念加15分
合格最低分:70分

4. Write Preheader Text

4. 撰写预标题文本

Generate preheader recommendation (30-80 characters):
  • Must complement (not repeat) the subject line
  • Include secondary value proposition or CTA preview
  • Avoid generic text like "View this email in your browser"
Example:
  • Subject: "Your personalized SEO roadmap is ready"
  • Preheader: "3 quick wins to boost your rankings this week"
生成预标题建议(30-80字符):
  • 必须补充(而非重复)主题行内容
  • 包含次要价值主张或CTA预览
  • 避免通用文本如"在浏览器中查看此邮件"
示例:
  • 主题:"您的个性化SEO路线图已就绪"
  • 预标题:"本周提升排名的3个快速技巧"

5. Compose Email Body

5. 撰写邮件正文

Apply the chosen framework structure. Load full framework details from
references/copy-frameworks.md
before writing.
General Email Writing Rules:
  • Opening: Hook in first sentence, address recipient by name if available
  • Body: Use short paragraphs (2-3 sentences max), bullet points for scannability
  • Tone: Match requested tone from profile or user input
  • Personalization: Use merge tags like
    {{firstName}}
    ,
    {{company}}
    ,
    {{productName}}
  • CTA: One primary CTA, clear and action-oriented ("Get Your Free Audit", "Claim Your Spot", "Start Your Trial")
  • Social Proof: Include if available (testimonial, stat, case study result)
  • Signature: Professional sign-off with name, title, company
Framework-Specific Structure:
Load the full structure from
references/copy-frameworks.md
and apply. Each framework has:
  • Section breakdown (e.g., PAS: Problem → Agitate → Solve)
  • Transition phrases
  • Example templates
应用选定的框架结构。撰写前从
references/copy-frameworks.md
加载完整的框架细节。
通用邮件撰写规则:
  • 开头:第一句吸引注意力,若有可用信息则称呼收件人姓名
  • 正文:使用短段落(最多2-3句),用项目符号提升可读性
  • 语气:匹配配置文件或用户要求的语气
  • 个性化:使用合并标签如
    {{firstName}}
    {{company}}
    {{productName}}
  • CTA:一个主CTA,清晰且行动导向("获取免费审计"、"抢占名额"、"开始试用")
  • 社交证明:若有则包含(证言、数据、案例研究结果)
  • 签名:专业落款,包含姓名、职位、公司
框架特定结构:
references/copy-frameworks.md
加载完整结构并应用。每个框架包含:
  • 段落划分(如PAS:问题 → 激化 → 解决方案)
  • 过渡短语
  • 示例模板

6. Generate HTML Version

6. 生成HTML版本

Create a responsive, dark-mode compatible HTML email using these specifications:
HTML Template Structure:
html
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="color-scheme" content="light dark">
  <meta name="supported-color-schemes" content="light dark">
  <title>{{emailSubject}}</title>
  <style>
    /* Inline critical CSS */
    body { margin: 0; padding: 0; font-family: Arial, Helvetica, sans-serif; }
    table { border-collapse: collapse; }
    .email-container { max-width: 600px; margin: 0 auto; }
    .body-text { font-size: 16px; line-height: 1.6; color: #333333; }
    .cta-button {
      display: inline-block;
      padding: 14px 28px;
      background-color: #0066cc;
      color: #ffffff;
      text-decoration: none;
      border-radius: 4px;
      font-weight: bold;
      min-height: 44px;
      min-width: 44px;
    }

    /* Dark mode styles */
    @media (prefers-color-scheme: dark) {
      body { background-color: #1a1a1a !important; }
      .body-text { color: #e0e0e0 !important; }
      .email-container { background-color: #2a2a2a !important; }
    }

    /* Mobile responsive */
    @media only screen and (max-width: 600px) {
      .body-text { font-size: 14px !important; }
      .headline { font-size: 22px !important; }
      .cta-button { display: block !important; width: 100% !important; }
    }
  </style>
</head>
<body>
  <!-- Email content goes here -->
</body>
</html>
HTML Rules:
  • Use table-based layout (not CSS Grid/Flexbox for email client compatibility)
  • Max width: 600px
  • Inline critical CSS (some clients strip
    <style>
    tags)
  • Web-safe fonts with fallbacks: Arial, Helvetica, Georgia, Times New Roman
  • Minimum 14px body text, 22px headlines on mobile
  • CTA button: minimum 44x44px touch target, high contrast ratio (4.5:1)
  • Include
    color-scheme: light dark
    meta tag
  • Dark mode CSS using
    @media (prefers-color-scheme: dark)
  • Alt text on all images (describe content, not "image" or "photo")
  • Always include plain-text MIME part for accessibility
CTA Button Best Practices:
  • One primary CTA per email (secondary CTAs okay as text links)
  • Use
    <a>
    tag with
    role="button"
    for accessibility
  • Padding: 14px vertical, 28px horizontal minimum
  • Background color with 4.5:1 contrast ratio against text
  • Include fallback for dark mode (lighter background or inverted colors)
创建支持响应式布局和深色模式的HTML邮件,需遵循以下规范:
HTML模板结构:
html
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="color-scheme" content="light dark">
  <meta name="supported-color-schemes" content="light dark">
  <title>{{emailSubject}}</title>
  <style>
    /* Inline critical CSS */
    body { margin: 0; padding: 0; font-family: Arial, Helvetica, sans-serif; }
    table { border-collapse: collapse; }
    .email-container { max-width: 600px; margin: 0 auto; }
    .body-text { font-size: 16px; line-height: 1.6; color: #333333; }
    .cta-button {
      display: inline-block;
      padding: 14px 28px;
      background-color: #0066cc;
      color: #ffffff;
      text-decoration: none;
      border-radius: 4px;
      font-weight: bold;
      min-height: 44px;
      min-width: 44px;
    }

    /* Dark mode styles */
    @media (prefers-color-scheme: dark) {
      body { background-color: #1a1a1a !important; }
      .body-text { color: #e0e0e0 !important; }
      .email-container { background-color: #2a2a2a !important; }
    }

    /* Mobile responsive */
    @media only screen and (max-width: 600px) {
      .body-text { font-size: 14px !important; }
      .headline { font-size: 22px !important; }
      .cta-button { display: block !important; width: 100% !important; }
    }
  </style>
</head>
<body>
  <!-- Email content goes here -->
</body>
</html>
HTML规则:
  • 使用基于表格的布局(为兼容邮件客户端,避免使用CSS Grid/Flexbox)
  • 最大宽度:600px
  • 内联关键CSS(部分客户端会移除
    <style>
    标签)
  • 网页安全字体及备选字体:Arial、Helvetica、Georgia、Times New Roman
  • 移动端正文最小字体14px,标题最小22px
  • CTA按钮:最小触摸目标44x44px,高对比度(4.5:1)
  • 包含
    color-scheme: light dark
    元标签
  • 使用
    @media (prefers-color-scheme: dark)
    实现深色模式CSS
  • 所有图片添加Alt文本(描述内容,而非仅写"image"或"photo")
  • 始终包含纯文本MIME版本以保障可访问性
CTA按钮最佳实践:
  • 每封邮件一个主CTA(次要CTA可作为文本链接)
  • 使用
    <a>
    标签并添加
    role="button"
    以保障可访问性
  • 内边距:最小垂直14px、水平28px
  • 背景色与文本对比度达4.5:1
  • 包含深色模式备选方案(浅色背景或反转颜色)

7. Generate Plain-Text Version

7. 生成纯文本版本

Create a plain-text fallback with:
  • No HTML tags
  • Line breaks for readability (max 70 characters per line)
  • CTA as full URL on separate line
  • Signature block with contact info
创建纯文本备选版本,要求:
  • 无HTML标签
  • 添加换行以提升可读性(每行最多70字符)
  • CTA以完整URL形式单独成行
  • 包含带联系信息的签名块

8. Output Format

8. 输出格式

Present the final email composition in this structure:
markdown
undefined
最终邮件内容按以下结构呈现:
markdown
undefined

Email Composition

邮件内容

Framework: [chosen framework name] Purpose: [email purpose] Tone: [tone] Recipient Type: [recipient type]

框架: [所选框架名称] 用途: [邮件用途] 语气: [语气] 收件人类型: [收件人类型]

Subject Line Options

主题行选项

#SubjectScoreTypeNotes
1[subject line 1]87Curiosity[why this works]
2[subject line 2]82Benefit[why this works]
3[subject line 3]79Urgency[why this works]
Recommended: #1 (highest score)
Preheader Text: [30-80 char preheader recommendation]

#主题评分类型说明
1[主题行1]87好奇心驱动[优势说明]
2[主题行2]82利益驱动[优势说明]
3[主题行3]79紧迫感驱动[优势说明]
推荐: #1(最高分)
预标题文本: [30-80字符的预标题建议]

Email Body (Plain Text)

邮件正文(纯文本)

[Full email body using framework structure]
[Include merge tags like {{firstName}}, {{company}}]
[CTA]
[Signature]

[遵循框架结构的完整邮件正文]
[包含
{{firstName}}
{{company}}
等合并标签]
[CTA]
[签名]

HTML Version

HTML版本

html
[Complete HTML email code with inline CSS, dark mode support, responsive design]

html
[包含内联CSS、深色模式支持、响应式设计的完整HTML邮件代码]

Plain Text Version

纯文本版本

[Plain text fallback with line breaks, CTA as full URL]

[带换行、CTA为完整URL的纯文本备选内容]

Email Metadata

邮件元数据

  • Word Count: [body word count]
  • Reading Time: [estimated reading time]
  • Character Count (with spaces): [count]
  • CTA Count: [number of CTAs]

  • 字数: [正文字数]
  • 阅读时长: [预估阅读时长]
  • 字符数(含空格): [统计数]
  • CTA数量: [CTA个数]

Next Steps

后续步骤

  • Review and edit copy
  • Choose subject line variant
  • Test HTML rendering in email client preview tool
  • Send as draft via MCP (if available) or copy to email platform
  • A/B test subject lines if sending to large list
undefined
  • 审阅并编辑文案
  • 选择主题行变体
  • 在邮件客户端预览工具中测试HTML渲染效果
  • 通过MCP(若可用)发送草稿,或复制到邮件平台
  • 若发送给大量收件人,对主题行进行A/B测试
undefined

Quality Gates

质量校验

Before delivering the email, verify:
  1. Subject line scores: At least one variant scores 70+
  2. Preheader length: 30-80 characters
  3. Framework alignment: Body follows chosen framework structure
  4. CTA clarity: Primary CTA is clear and action-oriented
  5. Mobile readability: Paragraphs are 2-3 sentences max
  6. HTML validity: Table-based layout, inline CSS, dark mode support
  7. Accessibility: Alt text on images, plain-text fallback included
  8. Spam check: No spam trigger words in subject or body
  9. Personalization: Merge tags used where appropriate
  10. Tone match: Email tone matches requested tone from profile
If any gate fails, revise before output.
交付邮件前需验证以下内容:
  1. 主题行评分: 至少一个变体得分≥70
  2. 预标题长度: 30-80字符
  3. 框架匹配: 正文遵循所选框架结构
  4. CTA清晰度: 主CTA清晰且行动导向
  5. 移动端可读性: 段落最多2-3句
  6. HTML有效性: 基于表格的布局、内联CSS、深色模式支持
  7. 可访问性: 图片含Alt文本、提供纯文本备选
  8. 垃圾邮件检查: 主题和正文无触发词
  9. 个性化: 合理使用合并标签
  10. 语气匹配: 邮件语气与配置文件要求一致
若任何校验项不通过,需修改后再输出。

Error Handling

错误处理

  • If
    references/copy-frameworks.md
    is missing, warn user and use basic AIDA structure
  • If
    email-profile.md
    is missing, prompt user for context (don't fail)
  • If subject line scores are all below 70, generate new variants
  • If HTML template fails validation, fall back to plain-text only and warn user
  • references/copy-frameworks.md
    缺失,向用户发出警告并使用基础AIDA结构
  • email-profile.md
    缺失,提示用户提供上下文(不终止流程)
  • 若所有主题行得分均低于70,重新生成变体
  • 若HTML模板验证失败,退回到仅纯文本版本并向用户发出警告

Resources

资源

  • references/copy-frameworks.md
    - Full framework structures and examples
  • email-profile.md
    - User's business context and preferences (optional)
  • references/copy-frameworks.md
    - 完整框架结构及示例
  • email-profile.md
    - 用户业务上下文及偏好(可选)

Example Invocation

调用示例

User: "Write a cold outreach email to a SaaS founder about my SEO audit service"
Agent:
  1. Loads email-profile.md (if exists)
  2. Selects PAS framework (cold outreach)
  3. Generates 3 subject line variants with scores
  4. Writes email body following PAS structure
  5. Creates HTML template with dark mode
  6. Creates plain-text fallback
  7. Outputs full email composition with metadata and next steps
用户: "撰写一封给SaaS创始人的陌生开发信,推广我的SEO审计服务"
Agent:
  1. 加载email-profile.md(若存在)
  2. 选择PAS框架(陌生开发信)
  3. 生成3个带评分的主题行变体
  4. 遵循PAS结构撰写邮件正文
  5. 创建支持深色模式的HTML模板
  6. 创建纯文本备选版本
  7. 输出包含元数据和后续步骤的完整邮件内容

Notes

注意事项

  • This sub-skill focuses on composition only (no sending/scheduling)
  • For sending emails, use
    email-send
    sub-skill or MCP email tools
  • For A/B testing, generate multiple variants using different frameworks
  • Always adapt tone and complexity to recipient type (B2B vs B2C, technical vs non-technical)
  • 此子技能仅聚焦于邮件撰写(不包含发送/排期功能)
  • 发送邮件需使用
    email-send
    子技能或MCP邮件工具
  • 如需A/B测试,使用不同框架生成多个变体
  • 需根据收件人类型(B2B vs B2C、技术型 vs 非技术型)调整语气和内容复杂度