Email Issue Fixer

← Back to skills

Fix the small mistakes that make an email look careless, without touching the writer's voice or what the email commits to. Always return the corrected draft plus a list of what changed.

Category: AI & Intelligent Agents
Repo: antigravity-awesome-skills
Path: skills/email-issue-fixer/SKILL.md
Updated: 9/7/2026, 7:23:33 AM
Open on GitHubHow to Install

AI Summary

Fix the small mistakes that make an email look careless, without touching the writer's voice or what the email commits to. Always return the corrected draft plus a list of what changed. It is useful for LLM applications, agent orchestration, RAG pipelines, AI evaluation, and multi-agent workflows. Source: antigravity-awesome-skills (skills/email-issue-fixer/SKILL.md).

Email Issue Fixer

Fix the small mistakes that make an email look careless, without touching the writer's voice or what the email commits to. Always return the corrected draft plus a list of what changed.

When to Use

  • Use when the user asks to "fix my email", "check the grammar before I send", "proofread this email", or any pre-send cleanup of a draft.
  • Use when the user also asks to "clean the links" or remove tracking from the URLs in an email. Link cleaning is never automatic.
  • Do not use for casual rewrites, tone makeovers, or structural restyling that the user did not ask for.

Pass 1: correctness only

Fix these:

  • Duplicated words ("a a", "the the") and wrong articles. Choose a/an by sound, not spelling: "an hour", "a university", "a one-time offer".
  • Subject-verb agreement ("the reports is done" becomes "the reports are done").
  • Wrong-word slips: your/you're, its/it's, than/then, affect/effect, their/there.
  • Capitalization, doubled spaces, missing or doubled punctuation.

Leave these alone. They are voice, not errors:

  • Sentence fragments, contractions, one-line paragraphs.
  • Lowercase greetings and sign-offs, informal phrasing, slang the writer chose.
  • Repetition used for emphasis.

If you cannot tell whether something is a mistake or a choice, leave it and mention it in the summary instead of changing it.

Never change names, numbers, dates, quoted text, or anything that alters what the email promises or asks for.

Pass 2: links (only when the user asks)

Do not touch links during a normal proofread. Clean them only when the user asks for it.

When asked, remove only these unambiguous tracking keys:

  • utm_source, utm_medium, utm_campaign, utm_term, utm_content, mc_cid, mc_eid, fbclid, gclid, igshid, _hsenc, _hsmi

Keep every other parameter. Values like id, page, v, q, or anything unfamiliar are often what makes the link work. When in doubt, keep it.

Treat ref, ref_src, and similarly generic keys as ambiguous: they are sometimes attribution, sometimes application state the link needs to work. Do not strip them automatically. Only remove them when context confirms they are attribution, or ask the writer first.

Do not delete whole links. Do not delete a link because it appears twice; signature links and repeated calls to action are usually deliberate.

Flag rather than fix: shortened links (bit.ly and similar), unfamiliar domains, and any query string that looks like a token, session ID, or credential. Point them out and let the writer decide.

If a query parameter looks like a credential, token, or session ID, do not echo its value anywhere in the output. Keep the link only by replacing the sensitive value with a placeholder such as [REDACTED] (for example ?auth=[REDACTED]), list the redaction in "Changes made", and tell the writer to re-enter the real value before sending. If they prefer, advise rotating the leaked value first.

Always return

  • The corrected email, in the same format and layout it arrived in.
  • A "Changes made" list, one line per change.
  • A "Left alone" list for anything you judged to be voice or an ambiguous link.
  • If nothing needed fixing, say so plainly rather than inventing changes.

Never

  • Send, schedule, or file the email. Hand the draft back for the writer to send.
  • Repeat credentials, tokens, or personal details found inside links.
  • Rewrite for tone, length, or structure unless asked. If the user wants that, ask what direction they want first.

Examples

Articles and agreement

Input:

Please find attached a a copy of the report. Our sales team achieved a amazing quarter.

Output:

Please find attached a copy of the report. Our sales team achieved an amazing quarter.

Changes made:

  • a a to a (duplicated word)
  • a amazing to an amazing (vowel sound)

Link cleaning

Input:

https://app.example.com/reports?utm_source=newsletter&utm_medium=email&id=123

Output:

https://app.example.com/reports?id=123

Changes made:

  • Removed 2 tracking parameters (utm_source, utm_medium)
  • Kept id=123, which the link needs to open the right report

Limitations

This reads and edits text only. It cannot judge whether the email's facts, tone, or timing are right. That stays with the writer.

Related skills