Proofread and clean tracking from email drafts

Email Issue Fixer cleans small mistakes in an email draft while preserving the writer's voice and what the message promises or requests. It returns the corrected text with a change list rather than sending, scheduling, or filing the email. Corrections stay focused on objective errors unless the user explicitly requests a broader rewrite.

The correctness pass handles duplicated words, wrong articles, subject-verb agreement, wrong-word slips, capitalization, doubled spaces, and missing or repeated punctuation. Article choices follow sound, including cases such as an hour and a university. Common word confusions include your and you're, its and it's, than and then, affect and effect, and their and there.

Fragments, contractions, short paragraphs, lowercase greetings and sign-offs, chosen slang, informal phrasing, and emphasis through repetition remain intact. Names, numbers, dates, quoted material, and commitments also stay unchanged. When an apparent error may be an intentional choice, the skill leaves it and explains that judgment.

Use this skill for requests to fix an email, check grammar before sending, or proofread a draft. It is also applicable when the writer explicitly asks to remove tracking parameters from links.

Normal proofreading does not alter URLs. The skill is unsuitable for unsolicited tone makeovers, length changes, or structural restyling. If the user wants those changes, the desired direction needs clarification. The writer remains responsible for the email's facts, tone, timing, and final send decision.

The input is the email draft in its existing format and layout, plus any explicit link-cleaning instruction. The output preserves that layout and includes Changes made with one entry per change and Left alone for intentional voice or ambiguous links. If nothing needs correction, it says so without inventing work.

Requested link cleanup removes only the named tracking keys: utm_source, utm_medium, utm_campaign, utm_term, utm_content, mc_cid, mc_eid, fbclid, gclid, igshid, _hsenc, and _hsmi. Other parameters remain, including identifiers, page selectors, versions, and queries. Generic ref and ref_src keys require evidence that they are attribution rather than application state, or a decision from the writer.

Whole links and repeated links remain intact because signature links and calls to action may be deliberate. Shortened URLs, unfamiliar domains, and possible credentials or session identifiers are flagged rather than silently treated as tracking. Sensitive parameter values are replaced with a placeholder such as [REDACTED], never repeated in the output. The change list records the redaction and asks the writer to restore the real value before sending, with rotation suggested when preferred.