Install This Claude Code Skill to Remove AI Tells from Your Documentation

Install This Claude Code Skill to Remove AI Tells from Your Documentation

The Humanizer skill rewrites Claude-generated text to sound more natural by removing common AI patterns, making your docs and comments more authentic.

3d ago·3 min read·6 views·via hn_claude_code, hn_mcp
Share:

What It Does

The Humanizer skill is a Claude Code skill that rewrites text to remove the distinctive patterns of AI-generated writing. It's based on Wikipedia's "Signs of AI writing" guide from WikiProject AI Cleanup, which was compiled from analyzing thousands of AI-generated text samples.

The skill works by identifying and eliminating common AI tells like:

  • Overly formal or academic phrasing
  • Unnatural transitions and connectors
  • Excessive hedging ("It's important to note that...")
  • Repetitive sentence structures
  • Generic, filler content

After the initial rewrite, the skill performs a second "obviously AI generated" audit pass to catch any lingering AI-isms that might have survived the first draft.

Setup

Installation takes less than a minute:

mkdir -p ~/.claude/skills
git clone https://github.com/blader/humanizer.git ~/.claude/skills/humanizer

If you already have the repository cloned or downloaded the SKILL.md file separately:

mkdir -p ~/.claude/skills/humanizer
cp SKILL.md ~/.claude/skills/humanizer/

Once installed, the skill is immediately available in your Claude Code sessions.

When To Use It

1. Documentation and READMEs

Claude excels at generating comprehensive documentation, but the output often sounds formulaic. Run your generated docs through /humanizer before committing:

/humanizer
[Your AI-generated documentation here]

2. Code Comments

AI-generated comments can be verbose and unnatural. Humanize them to make your codebase feel more authentic:

Please humanize this text: This function processes user input by validating against predefined patterns and returning sanitized output for downstream consumption.

3. Commit Messages and PR Descriptions

Make your version control history sound like it was written by a human, not an AI assistant.

4. Client Communications

When Claude helps draft emails or project updates, use the skill to remove the AI "voice" before sending.

Example Transformation

Before (AI-sounding):
"Great question! Here is an essay on this topic. I hope this helps! AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development."

After (Humanized):
"AI-assisted coding shows how large language models are changing software development."

The skill removes the prefatory fluff ("Great question!"), eliminates the hedging ("I hope this helps!"), and simplifies the overly academic phrasing to something more direct and natural.

How It Works with Your Workflow

You can invoke the skill in two ways:

  1. Direct command: /humanizer followed by pasting your text
  2. Natural language: "Please humanize this text: [your text]"

The skill is particularly useful when you're using Claude Code to generate content that will be read by other humans—whether that's documentation for your team, comments for future maintainers, or communications with stakeholders.

Limitations to Know

  • The skill focuses on prose, not code. It won't "humanize" your actual programming logic.
  • Like any automated rewriting tool, it can sometimes oversimplify or lose nuance. Always review the output.
  • It works best on paragraphs and longer text, not single sentences.

Why This Matters for Claude Code Users

As developers increasingly use AI assistants for writing tasks beyond code, the "AI voice" becomes a tell that can undermine credibility. The Humanizer skill helps bridge the gap between AI efficiency and human authenticity, making your AI-assisted work product more professional and trustworthy.

AI Analysis

Claude Code users should add the Humanizer skill to their toolkit immediately—it addresses a specific pain point that emerges when using AI for writing tasks. The key workflow change: after having Claude generate any non-code text (documentation, comments, emails), run it through `/humanizer` as a final polish step. Specific tip: Create a keyboard shortcut or alias for the humanizer command if you find yourself using it frequently. Since the skill works on any text, you can also use it outside of Claude Code sessions by running the same logic locally. Important distinction: This isn't about "hiding" AI use, but about improving communication quality. AI-generated text often includes unnecessary hedging, repetitive structures, and unnatural transitions that humans don't write. Removing these makes your writing clearer and more effective, whether readers know it was AI-assisted or not.
Original sourcegithub.com

Trending Now