Email Polish
Rewrite emails to be clearer, kinder, and shorter — without sounding fake.
Rating
Votes
0
score
Downloads
0
total
Price
Free
No login needed
Works With
About
Paste in any email draft and this skill rewrites it to be clear and warm without losing your voice. Three tones to pick from: direct, warm-professional, or apologetic. Cuts the throat-clearing. Keeps the soul.
Don't lose this
Three weeks from now, you'll want Email Polish again. Will you remember where to find it?
Save it to your library and the next time you need Email Polish, it’s one tap away — from any AI app you use. Group it into a bench with the rest of the team for that kind of task and you can pull the whole stack at once.
⚡ Pro tip for geeks: add a-gnt 🤵🏻♂️ as a custom connector in Claude or a custom GPT in ChatGPT — one click and your library is right there in the chat. Or, if you’re in an editor, install the a-gnt MCP server and say “use my [bench name]” in Claude Code, Cursor, VS Code, or Windsurf.
a-gnt's Take
Our honest review
Think of this as teaching your AI a new trick. Once you add it, rewrite emails to be clearer, kinder, and shorter — without sounding fake — no extra apps or complicated setup needed. It's verified by the creator and completely free. This one just landed in the catalog — worth trying while it's fresh.
Tips for getting started
Save this as a .md file in your project folder, or paste it into your CLAUDE.md file. Your AI will automatically use it whenever the skill is relevant.
Soul File
---
name: email-polish
description: Rewrite an email to be clearer, kinder, and shorter — without sounding like a chatbot. The user picks the tone.
---
The user pastes in an email draft. Your job: rewrite it so it's clear, warm, and easy to read.
## Step 1 — Ask the tone
If they didn't say, ask:
> "What tone do you want? **direct** (busy, just the point), **warm-professional** (friendly but appropriate for work), or **apologetic** (you're making up for something)?"
Default to **warm-professional**.
## Step 2 — Read what they wrote
Identify:
- The actual ask (what do they want the recipient to do?)
- Any context that's actually necessary (vs. throat-clearing)
- Anything that sounds defensive, anxious, or passive-aggressive
## Step 3 — Rewrite
Rules across all tones:
- **One ask per email.** If there are three asks, suggest splitting into three emails.
- **Cut the throat-clearing.** Delete: "I hope this finds you well," "Just wanted to reach out," "Sorry to bother you," "Quick question," "Touching base."
- **Subject line first.** Six words max. The recipient should know what's inside before opening.
- **The ask in the first sentence.** Not paragraph 3.
- **No "circle back," no "synergies," no "leverage."**
- **Active voice.**
- **Short paragraphs.** Two sentences each, max.
### direct
- 3-5 sentences total.
- Greeting + ask + minimum context + sign-off.
- Friendly but not gushy.
### warm-professional
- 4-7 sentences.
- Start with one specific human note ("Loved your talk last week" — but only if true).
- Then the ask.
- Brief context if needed.
- Warm sign-off.
### apologetic
- Acknowledge what happened in the first sentence — specifically, no "any inconvenience caused."
- Take responsibility without grovelling.
- State what you're doing to fix it.
- One sentence on what you'll do differently.
- No future promises you can't keep.
## Step 4 — Output
Show the rewritten email in a code block. Then below, briefly note what you changed and why (1-2 lines):
> Cut the opening "I hope you're well" — it adds nothing. Moved your ask to the first sentence. Trimmed the explanation in paragraph 3 because the recipient already knows the context.
## Never
- Never make up facts the user didn't include.
- Never sound like LinkedIn.
- Never use "essentially," "basically," or "literally."
- Never start with "I" — start with "Thanks for," "Quick update," or the ask itself.What's New
Initial release
Ratings & Reviews
0.0
out of 5
0 ratings
No reviews yet. Be the first to share your experience.