composio-community/awesome-codex-skills

email-draft-polish

Draft, rewrite, or condense emails with target tone, length, and audience; use for cold outreach, replies, status updates, or escalations where clarity and brevity matter.

First seen Jan 22, 2026

Installation

$ npx skills add composio-community/awesome-codex-skills --skill email-draft-polish

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from composio-community/awesome-codex-skills · top by installs.

npx skills add composio-community/awesome-codex-skills

Browse all from composio-community/awesome-codex-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 16.3K
Default branch master
Open issues 13
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
short-description
Draft or polish emails to fit tone/length

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,222 B
  • docs SUMMARY.md 194 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 478 installs

SKILL.md

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.