Email Draft Polish
- 373 installs
- 15.6k repo stars
- Updated July 26, 2026
- composiohq/awesome-codex-skills
Polish outbound emails for sales follow-ups, support replies, partnership outreach, and lifecycle campaigns before sending from Codex.
About
The email-draft-polish skill from composiohq/awesome-codex-skills helps refine rough email drafts into clear, persuasive messages suited to business communication. It improves structure, tone, and calls-to-action for outreach, support, and lifecycle emails without leaving the Codex workflow.
- Rewrites drafts for clarity and professional tone
- Tightens subject lines and opening hooks
- Aligns messaging with audience and intent
- Suggests stronger CTAs and next steps
- Flags ambiguity, jargon, and passive phrasing
Email Draft Polish by the numbers
- 373 all-time installs (skills.sh)
- Ranked #174 of 688 Office & Documents skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/composiohq/awesome-codex-skills --skill email-draft-polishAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 373 |
|---|---|
| repo stars | ★ 15.6k |
| Last updated | July 26, 2026 |
| Repository | composiohq/awesome-codex-skills ↗ |
What it does
Polish outbound emails for sales follow-ups, support replies, partnership outreach, and lifecycle campaigns before sending from Codex.
Files
Email Draft & Polish
Create or refine emails with precise tone and constraints.
Inputs to ask for
- Goal (inform, persuade, apologize, escalate), audience, tone (warm/formal/direct), desired length, must-include points, taboo topics, and call-to-action.
- If replying: include full thread and whether to quote or paraphrase.
Workflow
1) Outline: list the key points, questions, and CTA; confirm any missing facts. 2) Draft: write a concise body with subject line; keep paragraphs short; surface CTA early. 3) Variants: offer 2–3 tone/length variants if the ask is vague (e.g., “concise,” “detailed,” “bullet-only”). 4) QA: check for hedging vs. directness as requested, remove jargon, ensure names/links are correct, and guard against over-promising.
Output format
- Subject line, greeting, body, closing/signature placeholder.
- Optional TL;DR (1–2 sentences) and bullet summary for chat channels.
Related skills
Lark DocGenerate, update, and maintain structured documentation directly inside Lark/Feishu using natural language and agentic workflows.494kLark DriveLet their coding agents read, create, update and search documents stored in Lark (Feishu) Drive directly from prompts.493kLark SheetsConnect Claude, Cursor or other agents directly to Feishu/Lark spreadsheets for live data reads, writes, and structured automation.493kLark WikiGenerate, update, and sync structured knowledge bases inside Lark (Feishu) directly from code, specs, or agent output.493kLark WhiteboardGenerate, edit, and collaborate on visual diagrams and flowcharts directly inside Claude, Cursor or other agents.493kLark SlidesInstantly generate polished, professional slide decks from specs, roadmaps, or meeting notes using Lark/Feishu.493k