Email Drafter
Compose customer, partner, and follow-up emails that match your real tone instead of generic AI copy.
Overview
Email Drafter is an agent skill most often used in Grow (also Validate, Launch) that drafts and reviews professional emails matching your personal style via WorkIQ tone and correspondence context.
Install
npx skills add https://github.com/github/awesome-copilot --skill email-drafterWhat is this skill?
- Two-step workflow: gather recipient, purpose, and key points (max 3 clarifying questions), then analyze tone before draf
- WorkIQ pulls sent-mail patterns and prior threads with each recipient for context-aware drafts
- Covers proposals, follow-ups, replies, introductions, status updates, and tone analysis per recipient
- Trigger phrases: draft/write/compose/reply/follow-up email and analyze email tone
- Outputs reviewable drafts aligned to greeting, structure, and sign-off habits from your sent mail
- Workflow Step 1 limits clarifying questions to a maximum of 3 when context is incomplete
- Two main workflow steps: Gather Context and Analyze Tone before drafting
Adoption & trust: 1.1k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to send important email fast but AI drafts sound nothing like you and ignore how you usually talk to that person.
Who is it for?
Solo builders who write high-stakes email to customers or partners and want drafts that sound like them, not a template.
Skip if: Teams without WorkIQ or sent-mail access, bulk cold outreach at scale, or cases where you only need a one-off generic blurb with no style matching.
When should I use this skill?
User asks to draft, write, compose, or reply to email, send a follow-up, or analyze email tone with a recipient (WorkIQ-backed).
What do I get? / Deliverables
You get a context-aware draft grounded in your sent-mail patterns and prior threads, ready to review and send.
- Context-aware professional email draft
- Tone analysis summary for a recipient when requested
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow because most installs are lifecycle email—renewals, onboarding, support threads—where tone consistency matters most. Lifecycle covers ongoing recipient relationships and follow-ups that the skill optimizes via prior correspondence and WorkIQ tone analysis.
Where it fits
Draft personalized outreach to waitlist signups after analyzing how you usually greet early testers.
Compose a partnership or press follow-up that matches your prior thread tone with that contact.
Reply to a customer issue email using context from earlier support exchanges.
Write a renewal or onboarding follow-up aligned to your established sign-off and structure.
How it compares
Use for style-matched drafting with inbox context—not as a substitute for a full CRM or marketing automation stack.
Common Questions / FAQ
Who is email-drafter for?
Solo and indie builders who send professional email regularly and want agent drafts that reflect their tone and prior conversations with each recipient.
When should I use email-drafter?
Use it when you need to draft, reply, or follow up by email—for example validate outreach to early users, launch notes to press or affiliates, or grow lifecycle messages to customers—and when you want tone checked against how you usually write to that person.
Is email-drafter safe to install?
It is designed to read your email context through WorkIQ for tone and history; review the Security Audits panel on this page and your org’s mail-access policies before enabling it.
SKILL.md
READMESKILL.md - 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 abou