email-drafter

tarafından github

Kişisel yazım stilinize uygun profesyonel e-postalar taslaklayın ve gözden geçirin. Gönderdiğiniz e-postaları ton, selamlama, yapı ve imza kalıpları açısından analiz eder…

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 tarafından daha fazla skill

console-rendering
github
Go'da struct etiketi tabanlı konsol renderlama sistemini kullanma talimatları
official
acquire-codebase-knowledge
github
Bu beceriyi, kullanıcı açıkça mevcut bir kod tabanını haritalamayı, belgelemeyi veya bu kod tabanına dahil olmayı istediğinde kullanın. "Bu kod tabanını haritala", "belgele…" gibi ifadeler için tetikleyin.
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 talimatları komutu aracılığıyla özelleştirilmiş AI ajan talimat dosyaları oluşturur. .github/copilot-instructions.md dosyasını üretir (varsayılan, VS'de Copilot için önerilir…
official
acreadiness-policy
github
Kullanıcının bir AgentRC politikası seçmesine, yazmasına veya uygulamasına yardımcı olun. Politikalar, ilgisiz kontrolleri devre dışı bırakarak, etki/seviyeyi geçersiz kılarak, ayarlayarak…
official
add-educational-comments
github
We need to translate the given English text into Turkish, preserving the name "add-educational-comments" if it appears. The text is a description of an agent skill. We must not add any extra commentary, labels, or formatting. The translation should be accurate and natural in Turkish. The text: "Add educational comments to code files to transform them into effective learning resources. Adapts explanation depth and tone to three configurable knowledge levels: beginner, intermediate, and advanced Automatically requests a file if none is provided, with numbered list matching for quick selection Expands files by up to 125% using educational comments only (hard limit: 400 new lines; 300 for files over 1,000 lines) Preserves file encoding, indentation style, syntax correctness, and..." It seems cut off at the end. The original might have more, but we only have this. We'll translate what's given. Note: The name "add-educational-comments" does not appear in the text, so we don't include it. Translation: "Kod dosyalarına
official
adobe-illustrator-scripting
github
ExtendScript (JavaScript/JSX) kullanarak Adobe Illustrator otomasyon betiklerini yazın, hata ayıklayın ve optimize edin. Oluştururken veya değiştirirken kullanın…
official
agent-governance
github
Yapay zeka aracı erişimi ve davranışını kontrol etmek için bildirimsel politikalar, niyet sınıflandırması ve denetim izleri. Birleştirilebilir yönetişim politikaları, izin verilen/engellenen araçları, içerik filtrelerini, hız sınırlarını ve onay gereksinimlerini tanımlar — kod değil yapılandırma olarak saklanır. Anlamsal niyet sınıflandırması, araç yürütülmeden önce desen tabanlı sinyaller kullanarak tehlikeli istemleri (veri sızdırma, ayrıcalık yükseltme, istem enjeksiyonu) tespit eder. Araç düzeyinde yönetişim dekoratörü, politikaları işlevde u
official