mcpField
E
email-composer

email-composer

github.com/davila7生产力33.0k406 次安装今天更新
代码仓库

关于 email-composer

email-composer 是用于起草专业邮件的技能,面向需要根据目的、收件人关系、要点和语气组织邮件的人。它提供多种常见场景模板及邮件礼仪和校对清单。

主要功能

  1. 01按目的和语气起草邮件
  2. 02提供多类邮件模板
  3. 03指导主题行与邮件结构
  4. 04包含礼仪和发送前检查清单

适用场景

  1. 01撰写信息请求或跟进邮件
  2. 02准备技术更新或客户支持回复
  3. 03编写会议邀请、婉拒或道歉邮件

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/davila7/claude-code-templates --skill email-composer

安装后在 Claude Code 中输入/email-composer确认已加载。

详细介绍

邮件撰写

快速开始

提供背景和目的,我会为你起草一封合适的邮件。

我需要的信息:

  • 邮件目的(请求、跟进、通知等)
  • 收件人关系(同事、客户、经理、供应商)
  • 需要包含的要点
  • 期望的语气(正式、随意、紧急、友好)

邮件结构

标准商务邮件格式:

Subject: [Clear, specific subject line]

[Greeting],

[Opening - context/purpose]

[Body - main points]

[Closing - call to action]

[Sign-off]
[Your name]

常见邮件类型

信息请求
Subject: Question about Q4 project timeline

Hi [Name],

I hope this email finds you well. I'm reaching out regarding the Q4 product launch timeline.

Could you provide an update on:
- Current progress on feature development
- Expected completion date for testing phase
- Any blockers or dependencies we should be aware of

This will help us coordinate with the marketing team for the launch materials.

Thanks in advance for your help!

Best regards,
[Your name]
跟进邮件
Subject: Following up: Proposal for new payment system

Hi [Name],

I wanted to follow up on the payment system proposal I sent last week. I understand you're busy, so I wanted to make sure it didn't get lost in your inbox.

To recap, the proposed system would:
- Reduce transaction fees by 30%
- Integrate with existing accounting software
- Improve customer checkout experience

I'd be happy to schedule a brief call to discuss any questions you might have.

Looking forward to hearing from you.

Best,
[Your name]
技术更新
Subject: API Maintenance Window - [Date]

Team,

This is a reminder that we'll be performing scheduled maintenance on our API infrastructure on [Date] from [Time] to [Time] [Timezone].

During this window:
- API endpoints will be unavailable
- Database will be upgraded to v14
- SSL certificates will be renewed

Expected downtime: 2 hours

What you need to do:
- Notify your users of the planned downtime
- Ensure retry logic is in place for API calls
- Monitor your application after maintenance completes

If you have any concerns or conflicts with this schedule, please let me know by [Date].

Technical details available in our status page: [link]

Thanks,
[Your name]
客户支持
Subject: Re: Issue with order #12345

Hi [Customer name],

Thank you for reaching out about your order. I'm sorry to hear you're experiencing this issue.

I've looked into your order (#12345) and found the following:

[Explanation of the issue]

To resolve this, I've:
- [Action taken 1]
- [Action taken 2]

You should see [expected outcome] within [timeframe].

If you continue to experience any problems, please don't hesitate to reply to this email or call us at [phone number].

We appreciate your patience and understanding.

Best regards,
[Your name]
Customer Support Team
会议请求
Subject: Meeting request: Discuss database migration strategy

Hi [Name],

I'd like to schedule a meeting to discuss our approach for the upcoming database migration.

Agenda items:
- Review migration timeline and milestones
- Discuss rollback strategy
- Identify potential risks and mitigation plans
- Assign team responsibilities

Estimated duration: 45 minutes

I'm available:
- Monday 2-4 PM
- Wednesday 10 AM - 12 PM
- Friday 1-3 PM

Please let me know what works best for you, or feel free to suggest alternative times.

Best,
[Your name]

语气指南

正式语气
  • 使用完整句子
  • 避免缩略形式
  • 使用专业用语
  • 使用恰当称谓(Dr.、Mr.、Ms.)
随意语气
  • 可以使用缩略形式
  • 使用口语化表达
  • 仍然保持专业
  • 直呼其名
紧急语气
  • 主题行明确标注 [URGENT] 或 [ACTION REQUIRED]
  • 加粗关键要点
  • 明确截止日期
  • 直接给出行动号召

主题行最佳实践

好的主题行:

  • "Action required: Submit timesheet by Friday"
  • "Q4 Sales Report - Review needed"
  • "Meeting rescheduled: Project kickoff now Thursday"
  • "Quick question about deployment process"

不好的主题行:

  • "Update"
  • "Question"
  • "Hello"
  • "Following up"

邮件礼仪

要做的:

  • 在 24 小时内回复(即使只是确认收到)
  • 使用清晰、具体的主题行
  • 保持简洁
  • 发送前校对
  • 包含相关背景信息
  • 多个事项时使用项目符号
  • 以明确的行动号召结尾

不要做的:

  • 全部使用大写字母
  • 过度使用感叹号!!!
  • 把所有事情都标为紧急
  • 除非必要,不要回复全部
  • 情绪激动时发送
  • 包含不必要的收件人
  • 忘记邮件中提到的附件

按场景分类的模板

礼貌拒绝请求
Subject: Re: [Original subject]

Hi [Name],

Thank you for thinking of me for [request/opportunity].

Unfortunately, I won't be able to [participate/help/attend] due to [brief reason - optional]. However, I'd recommend [alternative suggestion if applicable].

I appreciate your understanding, and I hope we can collaborate on future opportunities.

Best regards,
[Your name]
为错误道歉
Subject: Apology and correction: [Issue]

Hi [Name],

I'm writing to apologize for [specific mistake]. This was an error on my part, and I take full responsibility.

To correct this:
- [Action 1 already taken]
- [Action 2 in progress]
- [Preventive measure for future]

I understand this may have caused [impact], and I'm committed to ensuring it doesn't happen again.

If you have any concerns or questions, please don't hesitate to reach out.

Sincerely,
[Your name]
分享好消息
Subject: Great news: [Achievement/milestone]

Team,

I'm excited to share that we've [accomplished goal]!

This success is thanks to:
- [Team/person contribution 1]
- [Team/person contribution 2]

Impact:
- [Metric improvement]
- [Business benefit]

Thank you all for your hard work and dedication. Let's keep up the momentum!

Cheers,
[Your name]

按语境分类的结尾用语

正式:

  • Sincerely
  • Best regards
  • Respectfully
  • Cordially

专业:

  • Best
  • Thanks
  • Kind regards
  • Regards

随意:

  • Cheers
  • Thanks!
  • Talk soon
  • Best

邮件撰写检查清单

  • 清晰、具体的主题行
  • 恰当的称呼
  • 开头说明目的
  • 用项目符号/编号组织关键要点
  • 明确的行动号召或后续步骤
  • 适合受众的语气
  • 校对拼写错误
  • 包含附件(如有提及)
  • 收件人正确(To、CC、BCC)
  • 专业的签名

评论

支持 Markdown