email-draft-polish
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
- Outline: list the key points, questions, and CTA; confirm any missing facts.
- Draft: write a concise body with subject line; keep paragraphs short; surface CTA early.
- Variants: offer 2–3 tone/length variants if the ask is vague (e.g., “concise,” “detailed,” “bullet-only”).
- 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.
More from composiohq/awesome-codex-skills
spreadsheet-formula-helper
Write and debug spreadsheet formulas (Excel/Google Sheets), pivot tables, and array formulas; translate between dialects; use when users need working formulas with examples and edge-case checks.
126meeting-notes-and-actions
Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate share-ready outputs.
91webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
78create-plan
Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
75support-ticket-triage
Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.
69gh-fix-ci
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD checks on GitHub Actions and wants a plan + code changes; for external checks (e.g., Buildkite), only report the details URL and mark them out of scope.
69