humanize-emaillisted

# /humanize-email, the prose pass Usage: `/humanize-email "<Person Name>/drafts/2026-08-25-space42.md"` Applies the Humanizer method (https://github.com/blader/humanizer), which the user's global instructions require as the final prose pass on anything user-facing. Cold emails are the highest-stakes case: a recipient who thinks an email was machine-written stops reading, and the whole research effort is wasted. ## Steps 1. **Read the draft and count the body words.** 2. **Cut first.** Length reduction removes most tells for free. Over 150 words: delete a whole paragraph, not a bit from each. The paragraph to delete is almost always the one listing a second project or explaining why internships are valuable. 3. **Run the tell sweep.** Full list in `rules/email_format.md`. The high-frequency offenders: - More than one em dash. Replace with full stops - `I hope this email finds you well` · `I am reaching out to` · `I am writing to express my interest` - `passionate about` · `leverage` · `utilize` · `delve` · `robust` · `seamless` · `cutting-edge` · `at the intersection of` - Rule-of-three lists that are not genuinely three things - `It's not just X, it's Y` - Uniform sentence length. This is the subtlest and most reliable tell. Break the rhythm with one short sentence - A tidy summarising sentence before the sign-off. Delete it — the ask should be the last thing - No contractions anywhere. Add two or three 4. **Fix the ask.** One ask, answerable in