AI Guides

How to Make AI-Written Emails Sound Human

Mika Reyes
Mika Reyes

Co-founder at King’s Cross Labs · ex-LinkedIn PM & Forbes 30 Under 30

View as MarkdownPaste into Claude or ChatGPT and it will walk you through the steps.

Send this guide to yourself

Get the link in your inbox so you can read it whenever you're ready.

Your email will also be saved for future updates.

Most AI-written emails get spotted in the first line, usually before the reader even reaches the ask. The fix is two-part: learn the six tells that give an email away, then run every draft through a short stack of AI editing skills before you send it. I use four of them, and the whole pass takes under two minutes.

You do not have to stop writing with AI to stop sounding like AI. That would cost you the time savings, which is the entire reason you started.

I write a lot of cold emails, client follow-ups, and partnership pitches. AI gets me to a draft fast, and a fast draft is worth a lot. What it does not get me is a draft anyone would believe I wrote, so I built a repeatable editing pass instead of rewriting from scratch every time.

What gives away an email written by AI?

Six patterns show up in almost every AI-drafted email. Once you can name them, you can find them in ten seconds.

  1. The "it's not X, it's Y" flip. "This isn't just a tool, it's a workflow." AI reaches for this structure constantly because it sounds insightful while saying very little.
  2. Em dashes everywhere. One is fine. Three in a five-sentence email is a signature.
  3. Polished business jargon. "Leverage," "streamline," "circle back," "align on next steps," "seamless." Nobody talks like this in a real email to one person.
  4. The rule of three. "Faster, cleaner, and more reliable." AI loves a three-item list where a human would have written one specific thing.
  5. Throat-clearing openers. "I hope this email finds you well." "Just wanted to reach out." Two sentences before the actual reason you are writing.
  6. Identical sentence rhythm. Every sentence roughly the same length, every paragraph roughly the same shape. Human email is lumpier than that.

Key insight: Readers rarely think "an AI wrote this." They think "this person did not actually write to me." That is the thing costing you the reply.

How do you fix an AI-written email before you send it?

Run the draft past the tell list, then through four editing skills in order. A skill is a saved set of instructions your AI runs on command, so you are not retyping the same editing brief every time. If that is new to you, start with what a skill actually is.

1. Do the tell check yourself first. Read the draft once looking only for the six patterns above. This takes ten seconds and it teaches you the patterns faster than any tool will. Most drafts have three or four of them in the first paragraph.

2. Run the Humanizer pass.

  • What it fixes: the structural tells. Inflated significance, fake-depth verbs like "highlighting" and "underscoring," the rule of three, em dash clusters.
  • Install: download Humanizer SKILL.md, drop it in your skills folder, reload Claude. Or paste the file contents into Claude and ask it to create the skill for you.
  • Full walkthrough: my Humanizer skill guide.

3. Run No AI Slop as a second, separate pass.

  • What it fixes: the same tells, but without flattening you. It protects your blunt lines, your jokes, your uncertainty, the specific numbers you put in. Run it after Humanizer, not merged with it, so you can see what each pass changed.
  • Install: paste this into Claude Code: Install the no-ai-slop skill globally from https://github.com/petergyang/no-ai-slop. Repo: github.com/petergyang/no-ai-slop.
  • Full walkthrough: how to humanize AI text.

4. Review the draft like a Google Doc with Human Review.

  • What it fixes: the tone problems no editing skill catches. You know what you would never say out loud. Highlighting the exact sentence and typing "I would never say this" beats describing the problem in chat and hoping the model finds the line.
  • Install: paste this into Claude Code or Codex: Install the /human-review skill globally from https://github.com/petergyang/human-review. Or run npx -y human-review setup --global in your terminal. Repo: github.com/petergyang/human-review.
  • Full walkthrough: how to edit AI drafts like a Google Doc.
Claude Code chat showing Human Review feedback arriving as a batch: a quoted line with the note "Can you please delete this line?" and a second comment asking to shorten section three
Your inline edits and comments come back to the agent as one batch, quoted line by line, so nothing gets lost in a long chat thread.

5. Use Content Research Writer when the email needs real substance.

  • What it fixes: thin content, which is what sinks cold pitches, investor updates and newsletters more often than tone does. It outlines with you, researches the claim, adds citations, and gives feedback section by section. Use it before the humanizing passes, since it is a drafting tool and the other two are editing tools.
  • Install: download the SKILL.md from Content Research Writer and drop it in your skills folder.
  • Full walkthrough: none yet. If you want to build something like it for your own formats, see creating a custom skill.

6. Put back the one detail only you could have written. Every AI draft is missing something specific: the thing they said on the call, the number from last quarter, the reason you actually thought of them this week. One concrete detail does more for believability than any amount of editing. Storing your standing context so the AI already knows your business and audience cuts down how often you have to add it back manually, which is what your second brain is for.

7. Read it out loud before you hit send. If you would not say the sentence to the person's face, it does not go out. Check names, numbers, and links yourself. This is thirty seconds and it catches the last thing the skills missed.

Additional Reading

Here are some related guides to check out:

  1. Humanizer
  2. How to Humanize AI Text and Make It Sound Like You
  3. How to Edit AI Drafts Like a Google Doc with Human Review
  4. How to Give Claude Memory (Beginner to Advanced)
  5. How to Create Your Own Custom Skill

Frequently asked questions

How can people tell my email was written by AI?
Six patterns give it away: the "it's not X, it's Y" flip, em dashes in clusters, polished business jargon like "leverage" and "circle back", three-item lists where one specific detail belongs, opening lines like "I hope this email finds you well", and sentences that are all the same length. Most AI drafts have several of these in the first paragraph.
What is the fastest way to make an AI email sound like me?
Run two editing passes back to back: Humanizer to strip the structural AI patterns, then No AI Slop to sharpen the draft while protecting your vocabulary and cadence. Then add one specific detail only you would know, such as something the person said on your last call. The whole pass takes under two minutes.
Should I just stop using AI for emails?
No, because the draft is where the time savings live. The problem is sending the first draft, not generating it. Keep the AI for drafting and add a short editing pass plus your own read-through before anything goes out.
What does the Human Review skill actually do?
It opens your draft in a browser so you can edit the text directly and highlight any sentence to leave a comment on it, the way you would in a Google Doc. When you send the batch, every edit and comment goes back to your AI at once and it applies them to the original file. It works on Markdown files, HTML files, and pages running on your local machine.

Want to build your first AI agent?

Build Your First Agent 101 is the next step! You'll get step by step guides, video tutorials and starter prompts to create your first agent in half a day, customized to your own workflow.

Learn more