菜单
Use when the user asks to draft, polish, translate, or reply to an email. Produces a clean draft with subject line, greeting, body, and sign-off, plus a pre-send self-check.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/nastorehub/NasDoor --skill email-draft命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | email-draft |
| description | Use when the user asks to draft, polish, translate, or reply to an email. Produces a clean draft with subject line, greeting, body, and sign-off, plus a pre-send self-check. |
| version | 1.0.0 |
| author | Hope Agent |
| license | MIT |
| metadata | {"nastech":{"tags":["office","email","communication","writing","productivity"],"related_skills":["meeting-notes","status-report"]}} |
Trigger phrases: "draft an email", "reply to this email", "polish this email", "翻译这封邮件", "write an email to ".
Don't trigger for: chat messages, Slack DMs, in-app notifications, marketing copy. Those are different formats.
Always produce the draft in this layout. Use a fenced code block so the user can copy it cleanly:
Subject: <concise, action-oriented, ≤60 chars>
Hi <Name>,
<opening line — context or thanks>
<body — one focused paragraph per point, max 3 paragraphs>
<call to action / next step / explicit ask>
Best,
<Sender>
If the language isn't English, adapt greeting and sign-off to the local convention:
<Name>，你好 / 祝好，<Sender><Name>様 / よろしくお願いいたします。<Sender>Bonjour <Name>, / Cordialement, <Sender><Name>님께 / 감사합니다, <Sender>Clarify minimal essentials via ask_user_question if missing:
Subject line first — the subject is what gets read. Make it specific and action-oriented:
Body — three paragraph max:
Pre-Send Self-Check — after producing the draft, run through this checklist out loud (in your reply to the user, before the draft):
If any box fails, revise the draft before showing it.
Subject: 15 min on <topic>?
Hi <Name>,
I'm <role> at <company>. We're working on <one-sentence context>, and I noticed your work on <specific thing>.
Would you have 15 minutes in the next two weeks for a quick call? I'm happy to share <X> in return / send a written question if that's easier.
Either way, thanks for considering.
Best,
<Sender>
Subject: Re: <original subject>
Hi <Name>,
Thanks for thinking of me / sending this.
I've decided to pass for now because <one-sentence reason>. Specifically, <constraint>.
Happy to revisit if <condition>.
Best,
<Sender>
Subject: <Project> blocked on <decision>
Hi <Name>,
Quick heads-up: <project> is blocked on <specific decision> as of <when>.
Context: <2 sentences max — what's happening and what's at stake>.
I'd recommend <option>. Can you confirm by <date>, or shall we discuss live? Open to your input.
Thanks,
<Sender>
Subject: Re: <original subject>
Hi <Name>,
Thanks for the call/email. To make sure we're aligned:
- <decision 1>
- <decision 2>
Action items on my side:
1. <action> — by <date>
2. <action> — by <date>
Action items on your side:
1. <action> — by <date>
Let me know if I missed anything.
Best,
<Sender>
When the user asks to translate an email:
[note] comment outside the draft| Mistake | Fix |
|---|---|
| Generic subject ("Hi", "Followup") | Specific subject naming the topic + action |
| Burying the ask in paragraph 4 | Move to paragraph 1 or 2 |
| "Hope you're well" filler when familiar | Skip — go straight to topic |
| Vague deadline ("when you can") | Specific date or "no rush, just FYI" |
| Mixing 3 unrelated asks | Split into 3 emails |
| Auto-translation kept English greeting | Localize properly (你好, 안녕하세요) |
