Email Polish
Purpose
Take a rough or blunt email draft and return a version that reads as friendly but professional — warm, clear, and respectful — while preserving the original meaning exactly.
Hard rules (never break)
- Preserve intent. Do not add promises, commitments, dates, prices, or requests that were not in the original.
- Preserve facts. Keep every name, date, number, link, and specific detail unchanged.
- No invented content. If a detail is missing (e.g. a meeting time), leave a clearly marked placeholder like
[time] rather than guessing.
- Keep it the owner's message. Improve tone and flow, not the substance or the decision.
- Match length sensibly. A short note stays short. Don't pad a two-line email into five paragraphs.
Tone target
- Warm opening, but not gushing. One friendly line max before the point.
- Direct and clear in the middle — say what's needed without hedging.
- Courteous close ("Thanks", "Appreciate it", "Best") calibrated to the recipient.
- Contractions are fine (it's, I'll). Avoid corporate filler ("per my last email", "circling back", "synergy").
- Never passive-aggressive. If the draft is frustrated, soften the edge while keeping the point firm.
Formality calibration
- Unknown / senior / external recipient → slightly more formal: full greeting ("Hi Dr. Lee,"), no slang.
- Known colleague / friendly → relaxed: "Hey Sam," casual sign-off.
- If
recipient is not provided, default to a safe, universally-appropriate friendly-professional register.
Workflow
- Read
raw_email. Identify: the core ask, key facts, and the emotional register.
- Rewrite paragraph by paragraph, keeping structure unless it's genuinely unclear.
- Fix grammar, spelling, and awkward phrasing.
- Ensure a clear subject line exists — if none, propose one prefixed with
Subject:.
- Return the polished email only. If any placeholder was inserted, list them in a short
Notes: line below.
Output format
Subject: <line>
<polished email body>
Notes: <only if placeholders or judgment calls were made; omit otherwise>
Example
Input (raw):
hey need the report by friday its late again. send it.
Output:
Subject: Report — Friday deadline
Hi [name],
Hope you're doing well. Just a quick note — could you get the report over to me by Friday? It's slipped a couple of times now, so I want to make sure we stay on track this week.
Thanks a lot,
[Your name]
1---2name: email-polish-23description: Rewrite the owner's raw email drafts into a warm, friendly-but-professional tone without changing intent, facts, names, dates, or requests.4---56# Email Polish78## Purpose9Take a rough or blunt email draft and return a version that reads as **friendly but professional** — warm, clear, and respectful — while preserving the original meaning exactly.1011## Hard rules (never break)121. **Preserve intent.** Do not add promises, commitments, dates, prices, or requests that were not in the original.132. **Preserve facts.** Keep every name, date, number, link, and specific detail unchanged.143. **No invented content.** If a detail is missing (e.g. a meeting time), leave a clearly marked placeholder like `[time]` rather than guessing.154. **Keep it the owner's message.** Improve tone and flow, not the substance or the decision.165. **Match length sensibly.** A short note stays short. Don't pad a two-line email into five paragraphs.1718## Tone target19- Warm opening, but not gushing. One friendly line max before the point.20- Direct and clear in the middle — say what's needed without hedging.21- Courteous close ("Thanks", "Appreciate it", "Best") calibrated to the recipient.22- Contractions are fine (it's, I'll). Avoid corporate filler ("per my last email", "circling back", "synergy").23- Never passive-aggressive. If the draft is frustrated, soften the edge while keeping the point firm.2425## Formality calibration26- **Unknown / senior / external recipient** → slightly more formal: full greeting ("Hi Dr. Lee,"), no slang.27- **Known colleague / friendly** → relaxed: "Hey Sam," casual sign-off.28- If `recipient` is not provided, default to a safe, universally-appropriate friendly-professional register.2930## Workflow311. Read `raw_email`. Identify: the core ask, key facts, and the emotional register.322. Rewrite paragraph by paragraph, keeping structure unless it's genuinely unclear.333. Fix grammar, spelling, and awkward phrasing.344. Ensure a clear subject line exists — if none, propose one prefixed with `Subject:`.355. Return the polished email only. If any placeholder was inserted, list them in a short `Notes:` line below.3637## Output format38```39Subject: <line>4041<polished email body>4243Notes: <only if placeholders or judgment calls were made; omit otherwise>44```4546## Example47**Input (raw):**48> hey need the report by friday its late again. send it.4950**Output:**51```52Subject: Report — Friday deadline5354Hi [name],5556Hope you're doing well. Just a quick note — could you get the report over to me by Friday? It's slipped a couple of times now, so I want to make sure we stay on track this week.5758Thanks a lot,59[Your name]60```