email-drafter

作者: github

起草并审阅符合您个人写作风格的专业邮件。通过分析您已发送邮件的语气、问候语、结构和结尾模式……

npx skills add https://github.com/github/awesome-copilot --skill email-drafter

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.

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

Before drafting, collect:

  1. Recipient(s) — who is the email for?
  2. Purpose — what is the email about? (proposal, follow-up, technical guidance, introduction, status update, etc.)
  3. Key points — what needs to be communicated?
  4. 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).

Step 2 — Analyze Tone

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

  1. Pull 3–5 recent sent emails from the user to the same recipient or similar recipients
  2. 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
  3. 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.

Step 3 — Draft the Email

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

Step 4 — Output

  1. Present the draft for review with a brief note on the tone/style applied
  2. Apply edits as the user requests — iterate until satisfied
  3. Save the final draft to outputs/<year>/<month>/ with a descriptive filename (e.g., 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

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"

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

来自 github 的更多技能

console-rendering
github
在Go中使用基于结构体标签的控制台渲染系统的说明
official
acquire-codebase-knowledge
github
当用户明确要求映射、记录或熟悉现有代码库时使用此技能。触发词如“映射此代码库”、“记录…
official
acreadiness-assess
github
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc…
official
acreadiness-generate-instructions
github
通过AgentRC指令命令生成定制化的AI代理指令文件。生成.github/copilot-instructions.md(默认,推荐用于VS Code中的Copilot…
official
acreadiness-policy
github
帮助用户选择、编写或应用AgentRC策略。策略通过禁用无关检查、覆盖影响/级别、设置…来定制就绪评分。
official
add-educational-comments
github
为代码文件添加教育性注释,将其转化为有效的学习资源。根据三个可配置的知识水平(初级、中级、高级)调整解释深度和语气。若未提供文件,自动请求文件,并附带编号列表以便快速选择。仅通过教育性注释将文件扩展最多125%(硬性限制:新增400行;超过1000行的文件限制为300行)。保留文件编码、缩进风格、语法正确性以及...
official
adobe-illustrator-scripting
github
使用ExtendScript(JavaScript/JSX)编写、调试和优化Adobe Illustrator自动化脚本。在创建或修改操作…的脚本时使用。
official
agent-governance
github
声明式策略、意图分类及审计追踪,用于控制AI代理工具访问与行为。可组合的治理策略定义允许/禁止的工具、内容过滤器、速率限制及审批要求——以配置而非代码形式存储。语义意图分类在执行工具前通过基于模式的信号检测危险提示(数据泄露、权限提升、提示注入)。工具级治理装饰器在函数层面强制执行策略...
official