Email Draft PolishSAFE
A curated list of practical Codex skills for automating workflows across the Codex CLI and API.
Overview
A curated list of practical Codex skills for automating workflows across the Codex CLI and API.
f10a5237c0bdOBSERVED · 2026-10-26What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: email-draft-polish description: 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. metadata: short-description: Draft or polish emails to fit tone/length --- # 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.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
f10a5237c0bdfull audit observations/trust-audit/skill/composiohq__email-draft-polish.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-26 | f10a5237c0bd | SAFE | B | 89 | first audit |
Questions
What does the email-draft-polish — composiohq/awesome-codex-skills skill do?
A curated list of practical Codex skills for automating workflows across the Codex CLI and API.
Is email-draft-polish — composiohq/awesome-codex-skills safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can email-draft-polish — composiohq/awesome-codex-skills access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (f10a5237c0bd), read on 2026-10-26. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/composiohq/email-draft-polish/)
Not your listing, or something out of date? Claim or update your listing.