email-drafter
Draft and review professional emails that match your personal writing style. Analyzes your sent emails for tone, greeting, structure, and sign-off patterns via WorkIQ, then generates context-aware drafts for any recipient. USE FOR: draft email, write email, compose email, reply email, follow-up emai
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 4bf49e63af9623c0… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
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:
- Recipient(s) — who is the email for?
- Purpose — what is the email about? (proposal, follow-up, technical guidance, introduction, status update, etc.)
- Key points — what needs to be communicated?
- 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:
- Pull 3–5 recent sent emails from the user to the same recipient or similar recipients
- 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
- 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
- Present the draft for review with a brief note on the tone/style applied
- Apply edits as the user requests — iterate until satisfied
- 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
Files
1- SKILL.md
c3324d26f84.5 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from github/awesome-copilot8
Check any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narr
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights,
Use this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS analysis". Do not trigger for campaign plann
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.