scientific-email-polishing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Scientific Email Polishing

科学类邮件润色

Purpose

用途

This skill helps compose and polish professional scientific correspondence including emails to collaborators, cover letters to journal editors, and responses to peer reviewers. It ensures clear communication, appropriate tone, explicit asks, and professional formatting for academic contexts.

本技能可帮助撰写和润色专业的科学类通信内容，包括给合作者的邮件、给期刊编辑的投稿信，以及给同行审稿人的回复。它能确保学术场景下的沟通清晰、语气恰当、诉求明确，且格式专业。

When to Use

适用场景

Use this skill when:

Professional emails: To collaborators, department heads, funding officers
Journal cover letters: Submitting manuscripts to journals
Response to reviewers: Addressing peer review comments
Editor correspondence: Queries, appeals, resubmission letters
Cold outreach: Potential collaborators, speakers, advisors
Administrative emails: To program officers, committee members

Trigger phrases: "write an email", "cover letter to journal", "response to reviewers", "email to collaborator", "professional email", "polish this email"

Do NOT use for:

Recommendation letters (use
```
academic-letter-architect
```
)
Research statements (use
```
career-document-architect
```
)
Grant proposals (use
```
grant-proposal-assistant
```
)

在以下场景中使用本技能：

专业邮件：给合作者、系主任、基金负责人的邮件
期刊投稿信：向期刊提交稿件时
审稿意见回复：回应同行审稿意见
与编辑的通信：咨询、申诉、返修信
陌生联络：联系潜在合作者、演讲者、导师
行政邮件：给项目负责人、委员会成员的邮件

触发短语："写一封邮件"、"期刊投稿信"、"审稿意见回复"、"给合作者的邮件"、"专业邮件"、"润色这封邮件"

请勿用于：

推荐信（请使用
```
academic-letter-architect
```
）
研究陈述（请使用
```
career-document-architect
```
）
基金申请书（请使用
```
grant-proposal-assistant
```
）

Core Principles

核心原则

1. One email, one purpose: Each email should have a clear, single objective

2. Explicit asks: State exactly what you need from the recipient and by when

3. Context first: Open with enough context for the reader to understand immediately

4. Professional but warm: Formal doesn't mean cold; collegial is appropriate

5. Scannable format: Busy recipients skim; use structure to aid quick reading

1. 一封邮件，一个核心目的：每封邮件都应具备清晰、单一的目标

2. 诉求明确：准确说明你需要收件人做什么，以及截止时间

3. 先讲背景：开头就提供足够的背景信息，让收件人立刻理解邮件内容

4. 专业且亲切：正式不等于生硬；保持同僚间的恰当氛围更为合适

5. 格式易读：忙碌的收件人通常会快速浏览邮件；使用结构化格式帮助其快速获取信息

Workflow

工作流程

Copy this checklist and track your progress:

Email Polishing Progress:
- [ ] Step 1: Identify purpose and desired outcome
- [ ] Step 2: Draft subject line (clear, specific)
- [ ] Step 3: Write opening (context in first sentence)
- [ ] Step 4: Compose body (organized, scannable)
- [ ] Step 5: State explicit ask (what, by when)
- [ ] Step 6: Close professionally (next steps, sign-off)
- [ ] Step 7: Review tone (polite, appropriate)

Step 1: Identify Purpose and Outcome

What action do you want the recipient to take? What decision do you need? By when? If you can't state this clearly, the email isn't ready to send.

Step 2: Draft Subject Line

Subject should preview content and signal urgency/type. Be specific: "Meeting request: Collaboration on X project" not "Quick question". See resources/template.md for examples.

Step 3: Write Opening

First sentence should establish context. Who are you (if unknown), why are you writing, what's this about? No need for extensive pleasantries. See resources/template.md for openers.

Step 4: Compose Body

Organize information logically. Use short paragraphs. Consider bullets for multiple points. Bold key information if needed. Keep under 3-4 paragraphs for most emails.

Step 5: State Explicit Ask

Be clear about what you need. Include timeline if relevant. Make it easy to say yes. Don't bury the ask.

Step 6: Close Professionally

Thank them, indicate next steps, offer to provide more info. Use appropriate sign-off for relationship level. See resources/template.md for sign-offs.

Step 7: Review Tone

Read aloud. Is it polite but efficient? Not too casual, not too stiff? Appropriate for your relationship with recipient? Validate using resources/evaluators/rubric_email.json.

复制以下清单，跟踪你的进度：

邮件润色进度：
- [ ] 步骤1：明确邮件目的与预期结果
- [ ] 步骤2：草拟主题行（清晰、具体）
- [ ] 步骤3：撰写开头（第一句就点明背景）
- [ ] 步骤4：撰写正文（结构清晰、易读）
- [ ] 步骤5：明确提出诉求（内容、截止时间）
- [ ] 步骤6：专业收尾（后续安排、落款）
- [ ] 步骤7：检查语气（礼貌、恰当）

步骤1：明确目的与预期结果

你希望收件人采取什么行动？你需要对方做出什么决定？截止时间是什么？如果你无法清晰说明这些，邮件还未准备好发送。

步骤2：草拟主题行

主题行应提前透露邮件内容，并传递紧急程度或邮件类型。要具体：比如用"会议邀约：关于X项目的合作讨论"而非"快速提问"。示例可参考resources/template.md。

步骤3：撰写开头

第一句就要点明背景。如果你是陌生联系人，说明你的身份、写信原因、邮件主题。无需过多客套话。开头示例可参考resources/template.md。

步骤4：撰写正文

逻辑组织信息。使用短段落。多个要点可采用项目符号。必要时加粗关键信息。大多数邮件的正文段落控制在3-4段以内。

步骤5：明确提出诉求

清晰说明你的需求。如有相关，注明时间线。让对方更容易给出肯定答复。不要把诉求藏在段落深处。

步骤6：专业收尾

表达感谢，说明后续安排，主动提出可提供更多信息。根据你与收件人的关系选择合适的落款。落款示例可参考resources/template.md。

步骤7：检查语气

大声朗读邮件。语气是否礼貌且高效？既不过于随意，也不过于生硬？是否符合你与收件人的关系？可使用resources/evaluators/rubric_email.json进行验证。

Email Types

邮件类型

Journal Cover Letter

期刊投稿信

Purpose: Introduce manuscript, explain significance, suggest reviewers

Structure:

Subject: Submission: [Manuscript Title] - [Type: Original Research/Review/etc.]

Dear Dr. [Editor] / Dear Editors,

[PARAGRAPH 1: What and why]
Please find attached our manuscript entitled "[Title]" for consideration
as a [Article Type] in [Journal Name]. This work [brief significance statement].

[PARAGRAPH 2: What's new]
Our study [key finding/contribution]. This advances the field by [impact].
We believe this work will interest readers of [Journal] because [fit with
journal scope].

[PARAGRAPH 3: Practicalities]
The manuscript is [X] words with [Y] figures. All authors have approved
the submission and there are no conflicts of interest to declare. This
work has not been published elsewhere and is not under consideration
at another journal.

[OPTIONAL: Reviewer suggestions]
We suggest the following potential reviewers: [Names with institutions
and emails].

[CLOSING]
Thank you for your consideration. We look forward to hearing from you.

Sincerely,
[Corresponding Author]

目的：介绍稿件，说明研究意义，推荐审稿人

结构：

主题：投稿：[稿件标题] - [类型：原创研究/综述等]

尊敬的[编辑姓名]博士 / 尊敬的编辑团队：

[第一段：投稿内容与原因]
随信附上我们题为《[标题]》的稿件，恳请考虑将其作为[文章类型]发表于[期刊名称]。本研究[简要说明研究意义]。

[第二段：研究创新点]
我们的研究[关键发现/贡献]。这一成果通过[具体影响]推动了该领域的发展。我们相信本研究将吸引[期刊名称]的读者，因为[契合期刊定位的说明]。

[第三段：相关事宜]
本稿件共[X]字，包含[Y]幅图表。所有作者均已同意投稿，且无利益冲突需声明。本研究未在其他地方发表，也未在其他期刊处于评审阶段。

[可选：推荐审稿人]
我们推荐以下潜在审稿人：[姓名、机构及邮箱]。

[收尾]
感谢您的考虑，期待您的回复。

此致，
[通讯作者]

Response to Reviewers

审稿意见回复

Purpose: Address each point thoroughly and professionally

Structure:

Subject: Revised Manuscript [ID]: [Title]

Dear Dr. [Editor],

Thank you for the opportunity to revise our manuscript "[Title]". We
appreciate the thoughtful comments from the reviewers, which have
significantly improved our work. Below we provide point-by-point
responses to each comment. Reviewer comments are in italics, our
responses in plain text, and changes to the manuscript are noted.

---

REVIEWER 1

*Comment 1: [Quote reviewer comment]*

Response: [Your response]. We have [action taken]. This change appears
on page X, lines Y-Z.

*Comment 2: [Quote reviewer comment]*

Response: [Your response].

[Continue for all comments]

---

REVIEWER 2
[Same format]

---

We hope these revisions address the reviewers' concerns and that the
manuscript is now suitable for publication in [Journal]. Please do not
hesitate to contact us if additional revisions are needed.

Sincerely,
[Corresponding Author]

目的：全面且专业地回应每一条审稿意见

结构：

主题：返修稿件[编号]：[标题]

尊敬的[编辑姓名]博士：

感谢您给予我们返修稿件《[标题]》的机会。我们非常感谢审稿人提出的宝贵意见，这些意见显著提升了我们的研究质量。以下是我们对每条意见的逐条回复。审稿意见以斜体显示，我们的回复为普通字体，稿件中的修改已标注。

---

审稿人1

*意见1：[引用审稿意见]*

回复：[你的回复]。我们已采取[具体行动]。修改内容位于第X页，第Y-Z行。

*意见2：[引用审稿意见]*

回复：[你的回复]。

[依次回复所有意见]

---

审稿人2
[相同格式]

---

我们希望这些修改能解决审稿人的疑虑，使稿件符合[期刊名称]的发表要求。如需进一步修改，请随时与我们联系。

此致，
[通讯作者]

Collaboration Request

合作邀约邮件

Purpose: Propose collaboration with new contact

Structure:

Subject: Collaboration opportunity: [Brief topic description]

Dear Dr. [Name],

I am [Your Name], a [position] at [Institution], working on [research area].
I am reaching out because [why them specifically - be genuine and specific].

[Brief background on your work and why collaboration makes sense]

I would be interested in [specific collaboration proposal]. This could involve
[what you're proposing - be concrete].

Would you be available for a brief call to discuss? I'm flexible on timing
and happy to work around your schedule.

Thank you for considering this. [Optional: note any mutual connection]

Best regards,
[Your Name]

目的：向新联系人提出合作提议

结构：

主题：合作机会：[简要主题描述]

尊敬的[姓名]博士：

我是[你的姓名]，目前在[机构]担任[职位]，研究方向为[研究领域]。我联系您是因为[具体说明为何选择对方，需真诚且具体]。

[简要介绍你的研究工作，以及合作的合理性]

我希望能[具体合作提议]。这可能涉及[具体合作内容，需明确]。

您是否有时间进行简短的电话沟通？我时间灵活，可配合您的日程安排。

感谢您考虑此事。[可选：提及共同联系人]

顺颂时祺，
[你的姓名]

Tone Guidelines

语气指南

Formality Spectrum

正式程度对照表

Recipient	Tone	Example Sign-off
Unknown editor/senior	Formal	"Sincerely," "Respectfully,"
Known colleague (distant)	Professional-warm	"Best regards," "Best,"
Known colleague (close)	Warm-professional	"Best," "Thanks,"
Close collaborator	Friendly-professional	"Thanks," "Cheers,"

收件人	语气	落款示例
陌生编辑/资深人士	正式	"此致，" "敬上，"
认识的同事（关系较远）	专业且亲切	"顺颂时祺，" "祝好，"
认识的同事（关系较近）	亲切且专业	"祝好，" "谢谢，"
密切合作者	友好且专业	"谢谢，" "干杯，"

Professional but Not Stiff

专业但不生硬

Too stiff:

"I am writing to inquire as to whether you might be available to provide guidance regarding..."

Too casual:

"Hey! Quick q - you free to chat about that thing?"

Just right:

"I'm reaching out to see if you'd have time to discuss [topic]. Would a brief call work for you next week?"

过于生硬：

"我写信是为了询问您是否有时间提供关于……的指导？"

过于随意：

"嘿！ quick q - 你有空聊那个事儿吗？"

恰到好处：

"我联系您是想了解您是否有时间讨论[主题]。下周进行简短的电话沟通是否可行？"

Diplomatic Language

委婉表达

When declining:

"Unfortunately, I won't be able to..."
"While I appreciate the opportunity, my current commitments prevent..."
"I'd recommend reaching out to [alternative] who might be better positioned..."

When disagreeing (reviewer response):

"We respectfully disagree with this interpretation because..."
"While we understand the reviewer's concern, our data suggests..."
"We have added clarification to address this point, though we maintain that..."

When following up:

"I wanted to follow up on my previous email..."
"I'm circling back on [topic]..."
"Apologies for the additional email, but I wanted to check..."

拒绝时：

"很遗憾，我无法……"
"虽然我很感谢这个机会，但目前的工作安排让我无法……"
"我建议您联系[替代人选]，他可能更适合……"

提出不同意见（审稿回复时）：

"我们对这一解读持保留意见，原因是……"
"虽然我们理解审稿人的顾虑，但我们的数据表明……"
"我们已补充说明以回应此点，但仍坚持我们的观点……"

跟进时：

"我想跟进一下之前发给您的邮件……"
"我再提及一下[主题]……"
"抱歉再次打扰您，我想确认一下……"

Guardrails

注意事项

Critical requirements:

Clear purpose: Every email needs an identifiable goal
Explicit asks: Don't make recipients guess what you need
Professional tone: Appropriate for academic/scientific context
Proofread: Errors undermine credibility
Appropriate length: Respect recipients' time
Complete information: Include everything needed to respond

Common pitfalls:

❌ Buried ask: Request hidden in paragraph 4
❌ No deadline: "When you get a chance" = never
❌ Wall of text: Long unbroken paragraphs
❌ Too casual: "Hey" to journal editor
❌ Too formal: Stilted language to close colleague
❌ Missing context: Assuming they remember previous exchange
❌ Multiple topics: Should be separate emails

关键要求：

目的明确：每封邮件都要有可识别的目标
诉求清晰：不要让收件人猜测你的需求
语气专业：符合学术/科学场景的要求
校对无误：错误会损害可信度
篇幅合适：尊重收件人的时间
信息完整：包含收件人回复所需的所有信息

常见误区：

❌ 诉求隐藏：把请求放在第4段之后
❌ 无截止时间："有空的时候" = 永远不会
❌ 大段文字：冗长且无分段的段落
❌ 过于随意：给期刊编辑发邮件用"嘿"
❌ 过于生硬：给关系近的同事用刻板的语言
❌ 缺少背景：假设收件人记得之前的交流内容
❌ 多主题混杂：不同主题应分开写邮件

scientific-email-polishing

Original

Translation

Scientific Email Polishing

科学类邮件润色

Table of Contents

目录

Purpose

用途

When to Use

适用场景

Core Principles

核心原则

Workflow

工作流程

Email Types

邮件类型

Journal Cover Letter

期刊投稿信

Response to Reviewers

审稿意见回复

Collaboration Request

合作邀约邮件

Tone Guidelines

语气指南

Formality Spectrum

正式程度对照表

Professional but Not Stiff

专业但不生硬

Diplomatic Language

委婉表达

Guardrails

注意事项

Quick Reference

快速参考