email-drafter

par github

Rédige et révise des courriels professionnels qui correspondent à votre style d'écriture personnel. Analyse vos courriels envoyés pour en déterminer le ton, la formule de salutation, la structure et les modèles de signature via…

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

Plus de skills de github

console-rendering
github
Instructions pour utiliser le système de rendu console basé sur les tags de struct en Go
official
acquire-codebase-knowledge
github
Utilisez cette compétence lorsque l'utilisateur demande explicitement de cartographier, documenter ou s'intégrer dans une base de code existante. Déclenchez-la pour des requêtes comme "cartographier cette base de code", "documenter…
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
Génère des fichiers d'instructions d'agent IA personnalisés via la commande d'instructions AgentRC. Produit .github/copilot-instructions.md (par défaut, recommandé pour Copilot dans VS…
official
acreadiness-policy
github
Aider l'utilisateur à choisir, rédiger ou appliquer une politique AgentRC. Les politiques personnalisent le score de préparation en désactivant les vérifications non pertinentes, en remplaçant l'impact/niveau, en définissant…
official
add-educational-comments
github
Ajouter des commentaires pédagogiques aux fichiers de code pour les transformer en ressources d'apprentissage efficaces. Adapte la profondeur et le ton des explications à trois niveaux de connaissances configurables : débutant, intermédiaire et avancé. Demande automatiquement un fichier si aucun n'est fourni, avec une liste numérotée pour une sélection rapide. Étend les fichiers jusqu'à 125 % en utilisant uniquement des commentaires pédagogiques (limite stricte : 400 nouvelles lignes ; 300 pour les fichiers de plus de 1 000 lignes). Préserve l'encodage du fichier, le style d'indentation, la correction syntaxique et...
official
adobe-illustrator-scripting
github
Rédigez, déboguez et optimisez des scripts d'automatisation Adobe Illustrator en utilisant ExtendScript (JavaScript/JSX). Utilisez lors de la création ou de la modification de scripts qui manipulent…
official
agent-governance
github
Politiques déclaratives, classification d'intention et pistes d'audit pour contrôler l'accès et le comportement des outils d'agents IA. Des politiques de gouvernance composables définissent les outils autorisés/bloqués, les filtres de contenu, les limites de débit et les exigences d'approbation — stockées en tant que configuration, pas de code. La classification d'intention sémantique détecte les invites dangereuses (exfiltration de données, escalade de privilèges, injection d'invite) avant l'exécution des outils à l'aide de signaux basés sur des motifs. Le décorateur de gouvernance au niveau des outils applique les politiques au niveau de la fonction...
official