email-drafter

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Email Drafter

邮件起草工具

Draft professional emails that match your established writing style and tone. Uses WorkIQ to analyze your sent emails and prior correspondence with recipients, then produces context-aware drafts you can review and refine.

起草符合你既定写作风格和语气的专业邮件。使用WorkIQ分析你已发送的邮件以及与收件人的过往通信记录，然后生成具备上下文感知能力的草稿供你审核和调整。

When to Use

适用场景

"Draft an email to [person] about [topic]"
"Write a follow-up email to [customer] regarding [project]"
"Reply to [person]'s email about [subject]"
"Compose a proposal email for [initiative]"
"Analyze my email tone with [recipient]"

"给[某人]起草一封关于[主题]的邮件"
"给[客户]撰写一封关于[项目]的跟进邮件"
"回复[某人]关于[主题]的邮件"
"为[计划]撰写提案邮件"
"分析我与[收件人]沟通的邮件语气"

Workflow

工作流程

Step 1 — Gather Context

步骤1——收集上下文

Before drafting, collect:

Recipient(s) — who is the email for?
Purpose — what is the email about? (proposal, follow-up, technical guidance, introduction, status update, etc.)
Key points — what needs to be communicated?
Relationship context — use WorkIQ to check prior email history with the recipient if available

If the user provides all of these upfront, proceed directly. Otherwise, ask clarifying questions (max 3).

起草前请收集以下信息：

收件人——邮件的发送对象是谁？
目的——邮件的核心内容是什么？（提案、跟进、技术指导、介绍、状态更新等）
要点——需要传达的核心信息有哪些？
关系上下文——如果有可用数据，使用WorkIQ查看与该收件人的过往邮件历史

如果用户提前提供了所有这些信息，可直接进入下一步。否则，请提出澄清问题（最多3个）。

Step 2 — Analyze Tone

步骤2——分析语气

When drafting for a recipient, use WorkIQ to understand the user's established communication patterns:

Pull 3–5 recent sent emails from the user to the same recipient or similar recipients
Identify patterns:
- Greeting style — formal ("Dear"), standard ("Hello"), casual ("Hi"), or direct (no greeting)
- Structure — short paragraphs vs. bullet lists vs. numbered steps
- Sign-off — what closing and name format the user typically uses
- Formality level — professional, friendly-professional, casual
- Language — which language the user writes in with this recipient
Apply those patterns to the draft

If WorkIQ is unavailable or no prior emails exist, use sensible professional defaults and note that the tone was inferred.

为特定收件人起草邮件时，使用WorkIQ了解用户既定的沟通模式：

提取用户发送给同一收件人或类似收件人的3-5封最近已发送邮件
识别以下模式：
- 问候风格——正式（"Dear"）、标准（"Hello"）、随意（"Hi"）或直接（无问候）
- 结构——短段落、项目符号列表、编号步骤
- 落款——用户通常使用的结束语和姓名格式
- 正式程度——专业、友好专业、随意
- 语言——用户与该收件人沟通时使用的语言
将这些模式应用到草稿中

如果WorkIQ不可用或没有过往邮件记录，使用合理的专业默认设置，并注明语气是推断得出的。

Step 3 — Draft the Email

步骤3——起草邮件

Apply the discovered (or default) style rules:

Greeting:

Match whatever greeting style was found in Step 2
Default: "Hello [FirstName]," for external, "Hi [FirstName]," for internal
For multiple recipients: "Hello [Name1], [Name2],"

Tone:

Direct and concise — no filler language
Friendly but professional
Get to the point quickly
Offer help proactively where appropriate ("Happy to discuss further", "Let me know if you need anything")

Structure:

Short emails (1–2 points): simple paragraphs, no bullets needed
Longer emails (proposals, multi-point updates): use bullet points or numbered lists
Include context from prior conversations when relevant ("Following our recent conversation about...")

Sign-off:

Match the user's established sign-off pattern from Step 2
Default: "Best regards," followed by the user's first name on the next line

Language:

Default to English unless the user specifies otherwise
Match the recipient's language if prior correspondence was in another language

应用已识别（或默认）的风格规则：

问候语：

与步骤2中识别的问候风格保持一致
默认规则：外部联系人使用"Hello [FirstName],"，内部联系人使用"Hi [FirstName],"
多个收件人时使用："Hello [Name1], [Name2],"

语气：

直接简洁——不使用冗余填充语
友好但专业
快速切入主题
适当情况下主动提供帮助（"Happy to discuss further", "Let me know if you need anything"）

结构：

短邮件（1-2个要点）：使用简单段落，无需项目符号
长邮件（提案、多要点更新）：使用项目符号或编号列表
相关情况下加入过往对话的上下文（"Following our recent conversation about..."）

落款：

与步骤2中识别的用户既定落款模式保持一致
默认规则：使用"Best regards,"，下一行跟随用户的名字

语言：

除非用户另有指定，否则默认使用英语
如果过往通信使用其他语言，则与收件人使用的语言保持一致

Step 4 — Output

步骤4——输出

Present the draft for review with a brief note on the tone/style applied
Apply edits as the user requests — iterate until satisfied
Save the final draft to
```
outputs/<year>/<month>/
```
with a descriptive filename (e.g.,
```
2026-03-26-email-acme-followup.md
```
)

展示草稿供审核，并附上所应用的语气/风格的简要说明
根据用户要求进行编辑——反复调整直到用户满意
将最终草稿保存到
```
outputs/<year>/<month>/
```
路径下，使用描述性文件名（例如
```
2026-03-26-email-acme-followup.md
```
）

Important Rules

重要规则

Never send emails — only draft them as files for the user to review and send manually
Always check WorkIQ for prior context with the recipient when available
If the user says "draft email" or "write email", activate this skill automatically
Save drafts using the
```
outputs/<year>/<month>/
```
folder convention
Respect privacy: do not include sensitive information from unrelated email threads

永远不要自动发送邮件——仅将邮件草稿生成为文件，供用户审核后手动发送
有可用数据时，始终通过WorkIQ查看与收件人的过往上下文
如果用户说"draft email"或"write email"，自动激活此技能
按照
```
outputs/<year>/<month>/
```
的文件夹规范保存草稿
尊重隐私：不要包含来自不相关邮件线程的敏感信息

Example Prompts

示例指令

"Draft an email to Sarah about the project timeline"
"Write a follow-up to the customer about their migration questions"
"Compose a proposal email for the new training initiative"
"Reply to John's email — agree with his approach but suggest we add monitoring"
"Analyze my email tone with the Acme team"

"给Sarah起草一封关于项目时间线的邮件"
"给客户撰写一封关于他们迁移问题的跟进邮件"
"为新的培训计划撰写提案邮件"
"回复John的邮件——同意他的方案，但建议我们增加监控环节"
"分析我与Acme团队沟通的邮件语气"

Requirements

要求

WorkIQ MCP tool is recommended for tone analysis and recipient context (Microsoft 365 / Outlook)
Without WorkIQ, the skill still works but uses professional defaults instead of personalized tone matching
Output is saved as markdown files in the workspace

WorkIQ MCP tool 推荐用于语气分析和获取收件人上下文（支持Microsoft 365 / Outlook）
没有WorkIQ的情况下，该技能仍然可用，但会使用专业默认设置，而非个性化的语气匹配
输出内容以markdown文件格式保存到工作区中