OlaDigital
ES

Keep your emails, proposals and posts from sounding like an AI wrote them

Before sending any text a model helped you write, you run it through a skill that removes the machine tics (template phrases, forced lists, brochure enthusiasm) without changing what it says.

Level
No code
Done from claude.ai or ChatGPT, without programming.
Time
Ten minutes to install it, seconds per text
Published

What it costs

Zero: it is an open source instruction file that installs in Claude Code, Cursor, Codex or Claude Desktop. You use the assistant you already pay for.

guided mode // I ask, you answer

ready to start

Do it with me, step by step

I will ask you 4 questions about your business, use your answers to get the prompt ready to copy, and then walk you through the 5 steps, one at a time. Like a Thermomix: you just answer and move on.

Also from Claude or ChatGPT with the Master Cookbook MCP: say "start the recipe que-tus-textos-no-suenen-a-ia".

Who it is for

Anyone who writes with AI help and has been told "ChatGPT wrote this, right?". Salespeople, managers, marketing, founders.

The problem

Generated texts can be spotted from a mile away: "in today's world", "it is important to note", lists of three for everything, brochure adjectives. The reader stops trusting the message and the person who signs it.

What changes

The same content, with your rhythm and without the tics. According to the README, Humanizer rewrites text that sounds like AI so it reads as written by a person, without changing what it says, and works in any agent that supports skills.

Ingredients

  • Claude Code, Cursor, Codex or Claude Desktop
  • A text you wrote with AI help that sounds like a machine to you
  • Two minutes for the installation with the skills CLI

Step by step

  1. 1

    Install the skill

    In the terminal: npx skills add blader/humanizer --global. In Claude Code you can also install it as a plugin from its marketplace; in Claude Desktop, you upload the zipped repository as a skill. It is all in the README.

  2. 2

    Give it the text

    Type /humanizer and paste the text, or ask in plain language: "humanize this email". It also accepts a file path.

  3. 3

    Compare with the original

    Read both. Check that no fact, deadline or condition changed. If it softened something important, fix it by hand.

  4. 4

    Add what only you know

    A concrete detail about the client, a reference to the last conversation. It is what no skill can add and what humanizes the most.

  5. 5

    Make it a habit before sending

    Important emails, proposals and posts: everything goes through the skill and through a read by you. Thirty seconds that protect your name.

The prompt

Replace what is in brackets with your company details, or use the guided mode above: it asks you and fills it in for you.

# Role
You are the copy editor for [COMPANY NAME]. You rewrite texts so they sound like a specific person, [WHO SIGNS AND HOW THEY SPEAK, FOR EXAMPLE "Cristián, direct and warm, informal"], without changing facts, figures, deadlines or conditions.

# Context
The text I paste was written by an AI and is addressed to [RECIPIENT, FOR EXAMPLE "a client who asked for a quote"]. The goal of the text is [GOAL, FOR EXAMPLE "get the proposal approved this week"].

# Task
Remove the machine tics: filler phrases, forced lists, brochure adjectives, generic closings. Shorten what you can. Keep every fact exact. Add a marked space in square brackets where I should put a personal detail about the recipient.

# Output format
Only the rewritten text, ready to send. Below, in one line, the list of facts you verified did not change.

# Examples
Original: "In today's world, it is essential to note that our comprehensive solution offers multiple benefits". Rewritten: "Here is what changes for you with this: [concrete benefit for their case]".

What usually goes wrong

  • ✕Sending without reading. The skill removes tics, but checking facts and promises is still on you.
  • ✕Humanizing without personalizing. Without a real detail about the recipient, it is still a text for anyone.
  • ✕Using it on legal texts without review. A softened nuance in a contract is a problem.

When not to use this recipe

In technical or legal texts, or texts with figures, check that the rewrite does not soften a condition or round a number. And do not use it to pass off as human a text that someone has the right to know was generated.

Source and real case

Cross-industry · written communication

The repository, trending weekly on GitHub at the time of review, is a Markdown skill that rewrites text with AI markers so it reads as written by a person without altering the content, installable in Claude Code, Cursor, Codex and Claude Desktop. The recipe turns it into a review habit before sending.

Trending repository:blader/humanizer — Agent skill that removes signs of AI-generated writing from text · GitHub

Last verified:Repository README read on 22 September 2026 (Markdown skill that rewrites text with AI markers without changing the content; installation with the skills CLI, as a Claude Code plugin or as a skill in Claude Desktop); the URL returned 200.

WritingEmailsProposalsSkills

Share it

If someone on your team could use this recipe, send it in one click. The suggested text copies itself.

LinkedInInstagram

Want to apply it in your business? Message Cristián directly.

Telegram
← Back to the cookbook