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行新註解;超過1,000行的檔案上限為300行)。保留檔案編碼、縮排風格、語法正確性及……
official
adobe-illustrator-scripting
github
使用 ExtendScript (JavaScript/JSX) 編寫、除錯及最佳化 Adobe Illustrator 自動化腳本。適用於建立或修改操控…的腳本時。
official
agent-governance
github
宣告式政策、意圖分類與稽核軌跡,用於控制AI代理工具存取與行為。可組合的治理政策定義允許/封鎖的工具、內容過濾器、速率限制與核准要求——以配置而非程式碼形式儲存。語意意圖分類在工具執行前,透過基於模式的訊號偵測危險提示(資料外洩、權限提升、提示注入)。工具層級治理裝飾器在函式層級強制執行政策……
official