- Home
- Skills
- Composiohq
- Awesome Codex Skills
- Email Draft Polish
email-draft-polish_skill
- Python
- Official
223
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill composiohq/awesome-codex-skills --skill email-draft-polish- SKILL.md1.2 KB
Overview
This skill drafts, rewrites, or condenses emails to match a specific goal, audience, tone, and length. It’s designed for cold outreach, replies, status updates, or escalations where clarity, brevity, and a clear call-to-action matter. Outputs include subject line, greeting, body, and a closing/signature placeholder. Optional TL;DR and bullet summaries are provided for chat channels.
How this skill works
I ask for the email goal (inform, persuade, apologize, escalate), audience, desired tone and length, must-include points, taboo topics, and the intended call-to-action. For replies, I request the full thread and whether to quote or paraphrase. I produce an outline of key points and the CTA, then draft the email with short paragraphs and an early CTA, offer 2–3 variants when appropriate, and run QA to remove jargon, check names/links, and avoid over-promising.
When to use it
- Preparing cold outreach that must be concise and persuasive
- Rewriting a reply to de-escalate or clarify responsibility
- Summarizing a long thread into a brief status update with clear next steps
- Condensing technical details for a non-technical audience
- Creating escalation emails that require a firm, professional tone
Best practices
- Provide the explicit goal, audience, and desired CTA before drafting
- Supply any required facts, names, dates, or links to ensure accuracy
- Specify taboo topics or phrases to avoid and preferred tone examples
- Request variants when unsure about tone or length to compare options
- Use the outline step to confirm missing facts before finalizing
Example use cases
- Cold sales outreach with a one-line hook and a clear meeting request
- Customer apology that acknowledges harm and proposes a remediation path
- Internal status email that lists blockers and requested decisions
- Reply to a stakeholder that reframes expectations and sets next steps
- Escalation to leadership that documents impact, action taken, and requested support
FAQ
Yes. Provide the thread and indicate whether to paraphrase key points or include selective quotes; I’ll produce a concise reply that references prior context.
How many tone variants do you provide?
Typically 2–3 variants (e.g., concise/formal, warm/informal, bullet-only) when the request is vague or you ask for alternatives.