Overview

Remove signs of AI-generated writing from any text output — emails, briefs, reports. Covers the full checklist: inflated symbolism, promotional language, AI vocabulary, em dash overuse, rule of three, passive voice, negative parallelisms, and filler phrases.

Use cases

Cold emails that don't scream 'AI wrote this'
Every email draft passes through the humanizer checklist before delivery. No 'I hope this finds you well', no 'leverage/synergy', no em dash chains. Contractions, short sentences, one idea per paragraph — the way humans actually write when they're busy.
Briefs and reports your team trusts to send externally
The same discipline applies to account briefs, QBR pre-reads, and executive summaries. Remove the tell-tale AI patterns — inflated symbolism, promotional hedging, superficial -ing analyses — so the output reads like an analyst wrote it, not a chatbot.

View full skill

Humanizer

When to use

Drafting or reviewing any text that will be read by humans (emails, briefs, reports, summaries)
Final pass before delivering output to the user
Any workflow step that produces prose (especially email drafting)

The checklist

Apply every rule below to all prose output. If a draft violates any rule, rewrite the offending passage before presenting it.

1. Inflated symbolism

Pattern: Treating ordinary business events as profound turning points.
Fix: State facts plainly. "They adopted Snowflake in Q3" — not "This pivotal shift signals a transformative reimagining of their data strategy."

2. Promotional language

Pattern: Reading like marketing copy or a press release.
Fix: Remove superlatives and hype words. Say what happened, not how amazing it is.

3. Superficial -ing analyses

Pattern: Gerund-heavy sentences that sound analytical but say nothing. "Leveraging their existing infrastructure while optimizing for cloud-native architectures..."
Fix: Use concrete verbs. Who did what, when, with what result.

4. Vague attributions

Pattern: "Many experts believe..." / "Studies show..." / "It is widely recognized..."
Fix: Name the source or drop the claim. If you can't cite it, don't assert it.

5. Em dash overuse

Pattern: Multiple em dashes (—) per paragraph, used as dramatic pauses.
Fix: One em dash per paragraph maximum. Use commas, periods, or parentheses instead.

6. Rule of three

Pattern: Every list has exactly three items. "Speed, efficiency, and reliability." "Innovation, collaboration, and excellence."
Fix: Use the actual number of items. Two is fine. Four is fine. Avoid the artificial triple.

7. AI vocabulary words

Banned words and replacements:

Don't use	Use instead
leverage	use
synergy	overlap, shared benefit
game-changing	significant, important
revolutionary	new, improved
unlock potential	improve, enable
holistic	complete, full
robust	strong, reliable
cutting-edge	new, advanced
paradigm shift	change
deep dive	detailed look
landscape	market, space, field
navigate	handle, manage
ecosystem	system, network
seamless	smooth
empower	help, enable

8. Passive voice

Pattern: "The platform was adopted by the team." "It was determined that..."
Fix: Use active voice. "The team adopted the platform." "We determined..."

9. Negative parallelisms

Pattern: "This is not just X — it's Y." "Not merely a tool, but a transformation."
Fix: State what it IS. Drop the "not just" construction entirely.

10. Filler phrases

Remove entirely:

"It's worth noting that..."
"It's important to remember that..."
"I hope this email finds you well"
"I wanted to reach out because..."
"At the end of the day..."
"In today's fast-paced world..."
"Moving forward..."
"Going forward..."
"As we move into..."
"On a broader note..."
"That said..."
"That being said..."

11. Contractions

Use them. "Don't" not "do not." "It's" not "it is." "Can't" not "cannot." Formal writing without contractions reads robotic.

12. Sentence length

Target: 80–120 words per email body. Mix short and medium sentences. No sentence over 30 words. No paragraph over 3 sentences.

13. Opening lines

Never start with a greeting + filler. Start mid-thought with something specific.

BAD: "Hi Sarah, I hope this finds you well. I wanted to reach out because..."
GOOD: "Sarah — your HCLTech cloud contract expires in 122 days with 50% renewal odds."

Skill: Humanizer