Token导航 LogoToken导航

Agent Skill · 研究检索

email-drafter(电子邮件起草者)

email-drafter 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

email-drafter 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 8,312。

总安装 16,671周安装 681GitHub Stars 89下载 5,394核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:email-drafter(电子邮件起草者)
来源仓库:https://github.com/claude-office-skills/skills
仓库路径:skills/email-drafter
安装命令:
npx skills add https://github.com/claude-office-skills/skills --skill email-drafter
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/claude-office-skills/skills --skill email-drafter

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于各类商务邮件起草,包括回复、跟进、请求与冷启动沟通。能根据关系亲疏、目的强弱调整语气并保持专业表达规范。支持多语言输出,覆盖客户维护、内部协调与对外联络场景。使用时应提供收件人背景、核心诉求与关键信息点以确保准确。正式法律或财务事项仍需人工复核后再发送。

email-drafter 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/email-drafter

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/claude-office-skills/skills --skill email-draf…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

email-drafter 怎么安装?

在终端执行 npx skills add https://github.com/claude-office-skills/skills --skill email-drafter。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

email-drafter 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

email-drafter 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

email-drafter 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

email-drafter 用的人多吗?

公开数据是累计安装 16,671 次,近一周安装 681 次,下载 5,394 次,GitHub 89 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

email-drafter 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
email-drafter

电子邮件起草者 · 本页

16,67189只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Email Drafter

Overview

This skill helps you draft professional emails for various business scenarios. It understands context, maintains appropriate tone, and follows email best practices for different situations.

Use Cases:

  • Responding to client inquiries
  • Following up on meetings
  • Requesting information or approvals
  • Delivering difficult news professionally
  • Cold outreach and introductions
  • Thank you and appreciation emails

How to Use

  1. Tell me the email scenario (reply, new message, follow-up, etc.)
  2. Provide context: recipient, relationship, purpose
  3. Share any specific points to include
  4. I'll draft an appropriate email

Example prompts:

  • "Draft a follow-up email after our sales meeting with Acme Corp"
  • "Write a polite reminder for an overdue invoice"
  • "Help me decline this meeting request professionally"
  • "Draft a cold outreach email to a potential partner"

Email Templates & Structures

Professional Email Structure

Subject: [Clear, specific, action-oriented]

[Greeting - appropriate to relationship]

[Opening - context/reference]

[Body - main message, organized by priority]

[Call to action - clear next steps]

[Closing - appropriate sign-off]

[Signature]

Tone Guidelines

ScenarioToneKey Elements
Client communicationProfessional, warmRespect, clarity, helpfulness
Internal teamDirect, friendlyEfficiency, collaboration
Executive/SeniorConcise, respectfulBottom-line first, data-driven
Cold outreachEngaging, value-focusedHook, relevance, clear ask
Difficult newsEmpathetic, clearAcknowledge, explain, next steps
Follow-upPolite, persistentReference, value add, easy response

Subject Line Best Practices

Good subject lines:

  • "Action Required: Q4 Budget Approval by Friday"
  • "Meeting Follow-up: Next Steps for Project Alpha"
  • "Quick Question: Your Availability Next Week"
  • "Thank You - Great Meeting Today"

Avoid:

  • Vague: "Hello" or "Quick question"
  • Too long: More than 50 characters
  • ALL CAPS or excessive punctuation
  • Misleading clickbait

Common Email Scenarios

1. Meeting Follow-up
Subject: Follow-up: [Meeting Topic] - Next Steps

Hi [Name],

Thank you for taking the time to meet [today/yesterday]. I enjoyed our discussion about [topic].

As discussed, here are the key action items:
• [Action 1] - [Owner] - [Deadline]
• [Action 2] - [Owner] - [Deadline]

I'll [your next action] by [date]. Please let me know if I missed anything or if you have questions.

Looking forward to our continued collaboration.

Best regards,
[Your name]
2. Request/Ask Email
Subject: Request: [Specific Ask]

Hi [Name],

I hope this message finds you well.

I'm reaching out because [brief context]. Would you be able to [specific request]?

To give you more context:
• [Relevant detail 1]
• [Relevant detail 2]

If possible, I'd appreciate your response by [date]. Please let me know if you need any additional information.

Thank you for your time.

Best,
[Your name]
3. Polite Decline
Subject: RE: [Original Subject]

Hi [Name],

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

After careful consideration, I won't be able to [participate/attend/take on] at this time due to [brief, honest reason].

[Optional: Alternative suggestion or future possibility]

I appreciate your understanding and hope we can [connect/collaborate] in the future.

Best regards,
[Your name]
4. Apology/Issue Resolution
Subject: Apology: [Brief Issue Description]

Dear [Name],

I want to sincerely apologize for [specific issue]. I understand this [caused inconvenience/affected your work/etc.].

Here's what happened: [Brief explanation without excuses]

To make this right, I have [action taken/will take]:
• [Corrective action 1]
• [Corrective action 2]

I'm committed to ensuring this doesn't happen again by [preventive measure].

Please let me know if there's anything else I can do.

Sincerely,
[Your name]

Output Format

When I draft an email, I'll provide:

## Email Draft

**Subject:** [Suggested subject line]

**To:** [Recipient]
**CC:** [If applicable]

---

[Email body]

---

## Notes
- [Any considerations or alternatives]
- [Suggested timing for sending]

Customization Options

Tell me your preferences:

  • Tone: Formal, semi-formal, casual
  • Length: Brief (2-3 sentences), standard, detailed
  • Style: Direct, diplomatic, enthusiastic
  • Sign-off: Best, Regards, Thanks, Cheers, etc.

Limitations

  • Cannot send emails (draft only)
  • May not know your organization's specific communication norms
  • Should be reviewed for accuracy of names, dates, and details
  • Not suitable for legal or highly sensitive communications without review

Examples

Example 1: Follow-up After Interview

User: "Draft a thank-you email after my job interview at TechCorp for a Product Manager role. I met with Sarah Chen, VP of Product."

Output:

Subject: Thank You - Product Manager Interview

Dear Sarah,

Thank you for taking the time to meet with me today about the Product Manager position at TechCorp. I thoroughly enjoyed learning about the team's vision for expanding into enterprise markets.

Our conversation reinforced my excitement about this opportunity. I'm particularly drawn to the challenge of building the analytics dashboard you mentioned, and I believe my experience leading similar initiatives at my current role would translate well.

I'm very interested in joining the TechCorp team and contributing to your product strategy. Please don't hesitate to reach out if you need any additional information from me.

Thank you again for the opportunity. I look forward to hearing from you.

Best regards, [Your name]

平台分布

Codex

35.88%
按下载量换算1,935

Claude

31.71%
按下载量换算1,710

Cursor

20.76%
按下载量换算1,120

Gemini CLI

8.47%
按下载量换算457

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills