email-composer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Email Composer

邮件撰写工具

Overview

概述

Draft clear, effective professional emails with appropriate tone, structure, and purpose. This skill covers business correspondence, cold outreach, follow-ups, escalations, apologies, negotiations, internal communications, and stakeholder updates. Includes tone calibration, cultural sensitivity, and templates for common business scenarios.
Apply this skill whenever professional email communication needs to be drafted, refined, or strategized.
起草清晰、高效的专业邮件,匹配恰当的语气、结构和目标。本技能覆盖商务信函、陌生开发信、跟进邮件、升级上报邮件、道歉邮件、谈判邮件、内部沟通邮件及利益相关方更新邮件,包含语气校准、文化适配及常见商务场景模板。
当你需要起草、优化或规划专业邮件沟通时均可使用本技能。

Multi-Phase Process

多阶段流程

Phase 1: Context Assessment

阶段1:上下文评估

  1. Identify the recipient(s) and their relationship to the sender
  2. Determine the email's primary purpose (inform, request, persuade, respond)
  3. Assess the appropriate formality level (see tone matrix)
  4. Consider cultural and organizational norms
  5. Identify any sensitive topics requiring careful framing
STOP — Do NOT begin drafting without knowing the recipient, purpose, and tone level.
  1. 明确收件人及与发件人的关系
  2. 确定邮件核心目标(告知、请求、说服、回应)
  3. 评估合适的正式度等级(参考语气矩阵)
  4. 考量文化和组织规范
  5. 识别需要谨慎表述的敏感话题
停止操作 — 未明确收件人、目的和语气等级前,请勿开始起草邮件。

Phase 2: Structure Planning

阶段2:结构规划

  1. Craft a clear, specific subject line
  2. Plan the opening (context-setting or relationship acknowledgment)
  3. Organize the body (one idea per paragraph, most important first)
  4. Define the call to action or next steps
  5. Choose an appropriate sign-off
STOP — Do NOT draft the full email without a subject line and clear CTA defined.
  1. 撰写清晰、明确的主题行
  2. 设计开头(铺垫上下文或致谢过往关联)
  3. 组织正文结构(每段一个核心观点,重要内容前置)
  4. 明确行动号召或后续步骤
  5. 选择合适的落款
停止操作 — 未确定主题行和清晰行动号召前,请勿撰写完整邮件。

Phase 3: Drafting

阶段3:起草

  1. Write using the selected tone and formality level
  2. Keep paragraphs short (2-4 sentences maximum)
  3. Use bullet points for multiple items or action items
  4. Bold or highlight key dates, deadlines, or decisions
  5. Include all necessary context without over-explaining
STOP — Do NOT send without completing the review phase.
  1. 按照选定的语气和正式度撰写
  2. 保持段落简短(最多2-4句话)
  3. 多项目或行动项使用项目符号列表
  4. 加粗或高亮关键日期、截止时间或决策内容
  5. 包含所有必要上下文,避免过度解释
停止操作 — 未完成审核阶段前请勿发送邮件。

Phase 4: Review

阶段4:审核

  1. Read aloud for natural flow and tone
  2. Check that the subject line matches the content
  3. Verify all names, dates, and attachments are correct
  4. Ensure the CTA is clear and actionable
  5. Consider how the email reads if forwarded out of context
  1. 通读检查流畅度和语气是否合适
  2. 确认主题行与内容匹配
  3. 核实所有姓名、日期、附件均正确
  4. 确保行动号召清晰可执行
  5. 考虑邮件被无上下文转发时的可读性

Email Type Decision Table

邮件类型决策表

SituationStructureToneKey Element
Status update to stakeholdersInverted PyramidProfessionalBold status indicator, bullet points
Request for approval/decisionBLUFProfessionalRecommendation first, supporting data
Delivering bad newsSandwichFormalEmpathy, explanation, constructive close
Meeting requestDirectProfessional-FriendlyAgenda items, time options
Cold outreachPersonalized HookProfessionalSpecific observation about recipient
Follow-up (no response)Gentle ReminderProfessionalEasy options, graceful out
EscalationStructured ReportFormalImpact, attempts made, specific ask
ApologyAcknowledgment + ActionFormalHonest explanation, preventive measures
Internal team updateQuick UpdateFriendly ProfessionalBrevity, action items highlighted
NegotiationCollaborativeProfessionalShared interests, multiple options
场景结构语气核心元素
向利益相关方同步状态更新倒金字塔专业加粗状态标识、项目符号列表
请求审批/决策BLUF专业建议前置,附带支撑数据
传递坏消息三明治结构正式同理心、解释说明、建设性收尾
会议请求直接式友好专业议程项、可选时间
陌生开发信个性化钩子专业针对收件人的具体观察内容
未获回复的跟进邮件温和提醒专业简便选项、体面的退出空间
升级上报邮件结构化报告正式影响范围、已尝试的解决措施、明确诉求
道歉邮件致歉+行动说明正式坦诚解释、预防措施
内部团队更新快速更新友好专业简洁、高亮行动项
谈判邮件协作式专业共同利益、多选项方案

Tone Calibration Matrix

语气校准矩阵

Tone LevelWhen to UseCharacteristicsExample Opening
FormalC-suite, legal, first contact with executivesNo contractions, full titles, structured"Dear Ms. Chen, I am writing to formally request..."
ProfessionalStandard business, cross-team, clientsContractions ok, warm but focused"Hi Sarah, I wanted to follow up on our conversation..."
Friendly ProfessionalFamiliar colleagues, regular collaboratorsCasual openings, personality shows"Hey team, quick update on the launch timeline..."
CasualClose teammates, informal updatesConversational, emoji acceptable"Just a heads up — the deploy is going out at 3pm"
语气等级适用场景特点开头示例
正式高管层、法律相关、首次对接高管不使用缩写、使用完整头衔、结构严谨"Dear Ms. Chen, I am writing to formally request..."
专业标准商务场景、跨团队协作、客户沟通可使用缩写、语气温和但聚焦目标"Hi Sarah, I wanted to follow up on our conversation..."
友好专业熟悉的同事、长期合作伙伴轻松的开头、可展现个人风格"Hey team, quick update on the launch timeline..."
随意关系密切的队友、非正式更新口语化、可使用表情符号"Just a heads up — the deploy is going out at 3pm"

Tone Adjustment Signals

语气调整信号

SignalShift Toward
Bad news, rejection, complaintMore formal, more empathetic
Good news, congratulationsWarmer, more enthusiastic
Urgency, deadlineMore direct, shorter sentences
Sensitive/political topicMore formal, more careful word choice
Follow-up after no responseSlightly more formal, provide easy out
信号调整方向
坏消息、拒绝、投诉更正式、更具同理心
好消息、祝贺更温暖、更有热情
紧急事项、截止时间临近更直接、更短的句子
敏感/涉及内部博弈的话题更正式、措辞更谨慎
未获回复的二次跟进略微提高正式度、提供简便的退出选项

Email Structure Patterns

邮件结构模式

The Inverted Pyramid (Default)

倒金字塔(默认)

Subject: [Action Required] Q3 Budget Approval — Due Friday

Hi Maria,

[BOTTOM LINE FIRST]
I need your approval on the Q3 budget by Friday, March 19.

[CONTEXT]
The finance team reviewed our proposal and approved the
$240K allocation with one change: marketing spend shifted
from Q3 to Q4.

[DETAILS]
Key changes from the original proposal:
- Marketing: $80K → $60K (Q3), $20K moved to Q4
- Engineering: unchanged at $120K
- Operations: $40K (new line item for tooling)

[ACTION]
Could you review the attached spreadsheet and reply with
your approval? Happy to jump on a quick call if you have
questions.

Thanks,
Alex
Subject: [Action Required] Q3 Budget Approval — Due Friday

Hi Maria,

[BOTTOM LINE FIRST]
I need your approval on the Q3 budget by Friday, March 19.

[CONTEXT]
The finance team reviewed our proposal and approved the
$240K allocation with one change: marketing spend shifted
from Q3 to Q4.

[DETAILS]
Key changes from the original proposal:
- Marketing: $80K → $60K (Q3), $20K moved to Q4
- Engineering: unchanged at $120K
- Operations: $40K (new line item for tooling)

[ACTION]
Could you review the attached spreadsheet and reply with
your approval? Happy to jump on a quick call if you have
questions.

Thanks,
Alex

The BLUF (Bottom Line Up Front)

BLUF(核心信息前置)

Subject: Decision Needed: Vendor Selection for Auth Service

Hi team,

RECOMMENDATION: Go with Auth0 (Option B).

Here's why:
1. 40% lower total cost over 3 years
2. Better compliance certifications (SOC2, HIPAA)
3. Faster integration timeline (2 weeks vs. 6 weeks)

Full comparison attached. Please reply by Thursday with
your vote or concerns.
Subject: Decision Needed: Vendor Selection for Auth Service

Hi team,

RECOMMENDATION: Go with Auth0 (Option B).

Here's why:
1. 40% lower total cost over 3 years
2. Better compliance certifications (SOC2, HIPAA)
3. Faster integration timeline (2 weeks vs. 6 weeks)

Full comparison attached. Please reply by Thursday with
your vote or concerns.

The Sandwich (Difficult Messages)

三明治结构(用于传递难开口的信息)

[Positive/Neutral Opening]
Thank you for the thorough proposal on the new dashboard.
The data visualization approach is exactly what we needed.

[Difficult Content]
After reviewing with the team, we've identified some concerns
with the timeline and resource allocation that we need to
address before moving forward...

[Constructive/Forward-Looking Close]
I'd love to schedule 30 minutes this week to work through
these together. I'm confident we can find an approach that
works for everyone.
[Positive/Neutral Opening]
Thank you for the thorough proposal on the new dashboard.
The data visualization approach is exactly what we needed.

[Difficult Content]
After reviewing with the team, we've identified some concerns
with the timeline and resource allocation that we need to
address before moving forward...

[Constructive/Forward-Looking Close]
I'd love to schedule 30 minutes this week to work through
these together. I'm confident we can find an approach that
works for everyone.

Templates for Common Scenarios

常见场景模板

Meeting Request

会议请求

Subject: Meeting Request: [Topic] — [Suggested Date/Time]

Hi [Name],

I'd like to schedule [duration] to discuss [topic].

Specifically, I'd like to cover:
- [Agenda item 1]
- [Agenda item 2]

Would [date/time option 1] or [date/time option 2] work
for you? Happy to adjust to your availability.

Best,
[Name]
Subject: Meeting Request: [Topic] — [Suggested Date/Time]

Hi [Name],

I'd like to schedule [duration] to discuss [topic].

Specifically, I'd like to cover:
- [Agenda item 1]
- [Agenda item 2]

Would [date/time option 1] or [date/time option 2] work
for you? Happy to adjust to your availability.

Best,
[Name]

Project Status Update

项目状态更新

Subject: [Project Name] Status Update — Week of [Date]

Hi [stakeholders],

**Status: On Track** (or At Risk / Blocked)

**Completed this week:**
- [Accomplishment 1]
- [Accomplishment 2]

**In progress:**
- [Task 1] — expected completion [date]
- [Task 2] — expected completion [date]

**Blockers/Risks:**
- [Blocker] — [mitigation plan or help needed]

**Next week's priorities:**
- [Priority 1]
- [Priority 2]

Let me know if you have questions or want to discuss any
of these items.

[Name]
Subject: [Project Name] Status Update — Week of [Date]

Hi [stakeholders],

**Status: On Track** (or At Risk / Blocked)

**Completed this week:**
- [Accomplishment 1]
- [Accomplishment 2]

**In progress:**
- [Task 1] — expected completion [date]
- [Task 2] — expected completion [date]

**Blockers/Risks:**
- [Blocker] — [mitigation plan or help needed]

**Next week's priorities:**
- [Priority 1]
- [Priority 2]

Let me know if you have questions or want to discuss any
of these items.

[Name]

Escalation Email

升级上报邮件

Subject: [Escalation] [Issue] — Impact on [Project/Deadline]

Hi [Manager/Stakeholder],

I'm escalating [issue] because [reason — timeline impact,
blocked dependencies, unresolved after N attempts].

**Background:**
[2-3 sentences of context]

**Impact if unresolved:**
- [Consequence 1 with timeline]
- [Consequence 2]

**What I've tried:**
- [Attempt 1 — outcome]
- [Attempt 2 — outcome]

**What I need:**
[Specific ask — decision, resource, intervention]

**Recommended next step:**
[Your suggestion]

I'm available to discuss this at your earliest convenience.

[Name]
Subject: [Escalation] [Issue] — Impact on [Project/Deadline]

Hi [Manager/Stakeholder],

I'm escalating [issue] because [reason — timeline impact,
blocked dependencies, unresolved after N attempts].

**Background:**
[2-3 sentences of context]

**Impact if unresolved:**
- [Consequence 1 with timeline]
- [Consequence 2]

**What I've tried:**
- [Attempt 1 — outcome]
- [Attempt 2 — outcome]

**What I need:**
[Specific ask — decision, resource, intervention]

**Recommended next step:**
[Your suggestion]

I'm available to discuss this at your earliest convenience.

[Name]

Apology / Mistake Acknowledgment

道歉/错误确认邮件

Subject: Regarding [Issue] — Our Apology and Next Steps

Hi [Name],

I want to apologize for [specific issue]. This fell short
of the standard you should expect from us.

**What happened:**
[Brief, honest explanation — no excuses]

**What we're doing about it:**
- [Immediate fix]
- [Preventive measure for the future]

**What this means for you:**
[Any impact, compensation, or timeline adjustment]

I take full responsibility for this and am committed to
making it right. Please don't hesitate to reach out if
you have any concerns.

Sincerely,
[Name]
Subject: Regarding [Issue] — Our Apology and Next Steps

Hi [Name],

I want to apologize for [specific issue]. This fell short
of the standard you should expect from us.

**What happened:**
[Brief, honest explanation — no excuses]

**What we're doing about it:**
- [Immediate fix]
- [Preventive measure for the future]

**What this means for you:**
[Any impact, compensation, or timeline adjustment]

I take full responsibility for this and am committed to
making it right. Please don't hesitate to reach out if
you have any concerns.

Sincerely,
[Name]

Cold Outreach

陌生开发信

Subject: [Personalized hook — reference their work/company]

Hi [Name],

I noticed [specific observation about their company/role/content].
[One sentence connecting their situation to your offering.]

[Company/Product] helps [target audience] [achieve outcome].
For example, [brief case study or metric].

Would you be open to a 15-minute call to explore whether
this could help [their company]? No pressure either way.

Best,
[Name]
[Title, Company]
Subject: [Personalized hook — reference their work/company]

Hi [Name],

I noticed [specific observation about their company/role/content].
[One sentence connecting their situation to your offering.]

[Company/Product] helps [target audience] [achieve outcome].
For example, [brief case study or metric].

Would you be open to a 15-minute call to explore whether
this could help [their company]? No pressure either way.

Best,
[Name]
[Title, Company]

Follow-Up After No Response

未获回复的跟进邮件

Subject: Re: [Original Subject]

Hi [Name],

I wanted to follow up on my email from [date] about [topic].

I understand you're busy — would it help if I:
- [Simplified option A]
- [Alternative option B]
- [Easy opt-out: "Let me know if this isn't a priority
   right now and I'll circle back later"]

[Name]
Subject: Re: [Original Subject]

Hi [Name],

I wanted to follow up on my email from [date] about [topic].

I understand you're busy — would it help if I:
- [Simplified option A]
- [Alternative option B]
- [Easy opt-out: "Let me know if this isn't a priority
   right now and I'll circle back later"]

[Name]

Subject Line Best Practices

主题行最佳实践

Formula

公式

[Action Tag] + [Specific Topic] + [Context/Deadline]

Examples:
"[Action Required] Q3 Budget Approval — Due March 19"
"[FYI] New Deploy Process Starting Monday"
"[Decision Needed] Vendor Selection by EOW"
"[Update] Sprint 12 Retro Notes"
"[Blocked] API Integration — Need Access Keys"
[Action Tag] + [Specific Topic] + [Context/Deadline]

Examples:
"[Action Required] Q3 Budget Approval — Due March 19"
"[FYI] New Deploy Process Starting Monday"
"[Decision Needed] Vendor Selection by EOW"
"[Update] Sprint 12 Retro Notes"
"[Blocked] API Integration — Need Access Keys"

Subject Line Rules

主题行规则

RuleGoodBad
Be specific"Q3 Marketing Budget: $80K Reallocation""Budget Update"
Include action if needed"[Review Required] PR #342""Please look at this"
Keep under 50 chars"Launch timeline shifted to April 3""Update regarding the potential shift in our product launch timeline"
No ALL CAPS"[Urgent] Server outage in prod""URGENT SERVER DOWN!!!"
Match the content"Meeting recap: 3 action items""Great chat today!"
规则正面示例反面示例
内容具体"Q3 Marketing Budget: $80K Reallocation""Budget Update"
如需行动则明确说明"[Review Required] PR #342""Please look at this"
长度控制在50字符以内"Launch timeline shifted to April 3""Update regarding the potential shift in our product launch timeline"
不要全大写"[Urgent] Server outage in prod""URGENT SERVER DOWN!!!"
与邮件内容匹配"Meeting recap: 3 action items""Great chat today!"

Cultural Considerations

文化注意事项

ContextAdjustment
East Asian business cultureMore formal, acknowledge hierarchy, indirect negative feedback
German business cultureDirect and precise, titles important (Herr/Frau), structured
US startup cultureCasual, first names, brief, action-oriented
UK business culturePolite hedging ("I wonder if...", "Perhaps we might...")
Cross-timezoneState timezone explicitly, suggest multiple options
Non-native English speakersSimpler vocabulary, shorter sentences, avoid idioms
场景调整建议
东亚商务文化更正式、尊重层级、负面反馈采用间接表述
德国商务文化直接精准、重视头衔(Herr/Frau)、结构严谨
美国创业公司文化随意、直呼其名、简短、以行动为导向
英国商务文化礼貌委婉的表述("I wonder if...", "Perhaps we might...")
跨时区沟通明确说明时区、提供多个可选时间
收件人为非英语母语者使用更简单的词汇、更短的句子、避免使用习语

Anti-Patterns / Common Mistakes

反模式/常见错误

Anti-PatternWhy It FailsWhat To Do Instead
Burying the ask at the bottomReader may never reach itLead with the request (BLUF)
Reply-all unnecessarilyClutters inboxes, annoys recipientsReply only to those who need to act
Passive-aggressive toneDamages relationships and trustBe direct and professional
Long emails requiring mobile scrollingRecipients skip or deferKeep to 5-8 sentences for mobile
Vague subject lines ("Quick question")Gets deprioritized or lostInclude topic and action needed
Too many asks for too many peopleDiffusion of responsibilityOne primary ask per email
No deadline ("when you get a chance")Means neverSpecify date and time
CC-ing manager without telling recipientPerceived as hostile escalationMention it in the email or tell them first
Humor or sarcasm in textMisinterpreted without vocal toneSave humor for in-person
Sending emotional emails immediatelyRegret and reputation damageWait 30 minutes before sending
反模式问题原因正确做法
将诉求埋在邮件末尾收件人可能看不到核心请求前置(BLUF结构)
不必要的全部回复挤占收件箱、惹恼收件人仅回复需要采取行动的对象
阴阳怪气的语气损害关系和信任直接且专业地表述
长邮件需要在移动端滚动多次收件人会跳过或延后处理移动端适配的内容控制在5-8句话
模糊的主题行("小问题请教")会被降低优先级或遗漏包含主题和需要的行动
一封邮件向多个人提多个诉求责任分散每封邮件仅提一个核心诉求
没有截止时间("有空的时候看下")等于没有要求明确指定日期和时间
未告知收件人就抄送给对方经理会被视为恶意上报在邮件中说明或提前告知对方
文字中使用幽默或讽刺没有语音语调容易被误解幽默留到面对面沟通时使用
情绪激动时立刻发邮件事后后悔、损害个人声誉发送前等待30分钟冷静

Anti-Rationalization Guards

反合理化防护规则

  • Do NOT skip the context assessment because "it's just a quick email" -- every email represents you.
  • Do NOT draft without a defined CTA -- even "FYI" emails should state what you expect.
  • Do NOT send without the read-aloud review, especially for sensitive emails.
  • Do NOT use a casual tone with someone you haven't corresponded with before.
  • Do NOT send an escalation email without documenting what you have already tried.
  • 不要因为"这只是一封短邮件"就跳过上下文评估——每一封邮件都代表你的个人形象。
  • 不要没有明确行动号召就起草邮件——即使是"周知"类邮件也应该说明你期望收件人做什么。
  • 发送前一定要通读检查,敏感邮件尤其要遵守这条规则。
  • 不要和从未有过沟通的人使用随意的语气。
  • 发送升级上报邮件前一定要记录你已经尝试过的解决措施。

Integration Points

集成点

SkillHow It Connects
content-creator
Brand voice and copywriting frameworks apply to marketing emails
content-research-writer
Research summaries inform executive briefing emails
docx-processing
Generated documents attach to emails
pdf-processing
Generated PDF reports attach to emails
xlsx-processing
Spreadsheet attachments accompany data-driven emails
llm-as-judge
Evaluate email tone and clarity against rubric
技能关联方式
content-creator
品牌声量和文案框架可应用于营销类邮件
content-research-writer
研究总结可用于高管简报类邮件
docx-processing
生成的文档可作为邮件附件
pdf-processing
生成的PDF报告可作为邮件附件
xlsx-processing
数据类邮件可附带表格附件
llm-as-judge
可按照评估规则校验邮件的语气和清晰度

Skill Type

技能类型

FLEXIBLE — Adapt tone, structure, and formality to the relationship, organizational culture, and communication purpose. The BLUF structure and clear subject line practices are strongly recommended for all professional correspondence.
灵活适配——可根据沟通双方关系、组织文化和沟通目的调整语气、结构和正式度。BLUF结构和清晰主题行规范强烈建议应用于所有专业通信场景。