/ Directory / Playground / humanizer
● Community blader ⚡ Instant

humanizer

by blader · blader/humanizer

Rewrite AI-generated prose to lose the em-dashes, tricolons, and hedged claims that scream "ChatGPT wrote this".

Humanizer is a Claude Code skill that identifies and removes the telltale markers of AI writing: aggressive em-dash use, rule-of-three cadence, unnecessary hedging ("It's important to note"), and generic emphatic adjectives ("delve", "navigate", "robust"). Works on your drafts before you ship.

Why use it

Key features

Live Demo

What it looks like in practice

ready

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "humanizer-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/blader/humanizer",
        "~/.claude/skills/humanizer"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "humanizer-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/blader/humanizer",
        "~/.claude/skills/humanizer"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "humanizer-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/blader/humanizer",
        "~/.claude/skills/humanizer"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "humanizer-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/blader/humanizer",
        "~/.claude/skills/humanizer"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "humanizer-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/blader/humanizer",
        "~/.claude/skills/humanizer"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "humanizer-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/blader/humanizer",
          "~/.claude/skills/humanizer"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add humanizer-skill -- git clone https://github.com/blader/humanizer ~/.claude/skills/humanizer

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use humanizer

Strip AI tells from a draft blog post before publishing

👤 Writers who use AI assistance but don't want to sound like everyone else ⏱ ~20 min beginner

When to use: You drafted a post with Claude, and it reads like every LinkedIn thought-leader post from 2025.

Prerequisites
  • Skill installed — git clone https://github.com/blader/humanizer ~/.claude/skills/humanizer
Flow
  1. Diagnose
    Use humanizer. Analyze /drafts/post.md. List the AI tells — em-dashes, rule-of-three, hedged opener, generic adjectives — with counts.✓ Copied
    → Concrete tell inventory, not vibes
  2. Rewrite conservatively
    Rewrite paragraph by paragraph. Change only the AI tells. Keep my voice. Show diff.✓ Copied
    → Minimal diff, voice preserved
  3. Spot-check
    Read the revised version aloud (just the first 200 words). Does it still sound like me?✓ Copied
    → Sampled read; flag anything that drifted

Outcome: A post that doesn't trigger the AI-detection reflex in readers.

Pitfalls
  • Over-aggressive rewrite flattens your actual voice — Run conservatively first; only escalate sentence-by-sentence on problem areas
Combine with: filesystem

Make technical docs sound written, not generated

👤 Teams auto-generating README/API docs ⏱ ~45 min intermediate

When to use: Your auto-generated docs all have "This comprehensive guide will navigate you through..." — and users hate it.

Flow
  1. Scan a batch
    Use humanizer on every .md under /docs. For each, report the tell density (tells per 100 words).✓ Copied
    → Doc-by-doc density report
  2. Fix worst offenders
    Rewrite the 5 with highest density. Stay technical — no vibes, just strip the filler.✓ Copied
    → Diffs show removed fluff without losing substance

Outcome: Docs that read like a human wrote them, which in technical writing means "read like they have something to say".

Pitfalls
  • Stripping hedging where it was actually a safety note — Review diffs — if a "note that..." was a real warning, keep it
Combine with: filesystem

Combinations

Pair with other MCPs for X10 leverage

humanizer-skill + filesystem

Bulk-humanize a folder of drafts

Run humanizer on every .md under /blog/drafts.✓ Copied
humanizer-skill + github

Humanize a PR's auto-generated description

Humanize the description of PR #2341 and push the update.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
diagnose text: str Before rewriting, to see what's wrong 0
rewrite text: str, intensity: conservative|aggressive Apply the fix 0
compare_voice sample_a, sample_b Check voice preservation after rewrite 0

Cost & Limits

What this costs to run

API quota
N/A
Tokens per call
Proportional to text length
Monetary
Free
Tip
Diagnose first — cheap. Rewrite only what needs it.

Security

Permissions, secrets, blast radius

Credential storage: None
Data egress: None — skill is prompt-level

Troubleshooting

Common errors and fixes

Rewrite sounds just as AI as before

You're in conservative mode. Switch to aggressive, and provide 3–5 sample paragraphs of your actual voice as reference.

Skill not activating

Mention it explicitly: "use humanizer". Auto-activation depends on skill metadata.

Voice drifts after rewrite

Pin your voice with a sample: "rewrite to match this paragraph's voice"

Alternatives

humanizer vs others

AlternativeWhen to use it insteadTradeoff
Humanizer-zhYou're writing in ChineseChinese-tuned patterns
Manual editingShort piece; faster to just editNo systematic pattern catch

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills