# Humanizer

Humanize text: strip AI-isms and add real voice.

- Repository: https://github.com/mateaix/mateclaw (1176 stars)
- Category: Media
- License: Apache-2.0
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add mateaix/mateclaw --skill humanizer -g -a claude-code -y`
Codex: `npx skills add mateaix/mateclaw --skill humanizer -g -a codex -y`
Cursor: `npx skills add mateaix/mateclaw --skill humanizer -g -a cursor -y`
Gemini CLI: `npx skills add mateaix/mateclaw --skill humanizer -g -a gemini-cli -y`

## Description

Humanize text: strip AI-isms and add real voice.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Humanizer: Remove AI Writing Patterns

Identify and remove signs of AI-generated text to make writing sound natural and human. Based on Wikipedia's "Signs of AI writing" guide (maintained by WikiProject AI Cleanup), derived from observations of thousands of AI-generated text instances.

**Key insight:** LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely completion, which is how the telltale patterns below get baked in.

## When to use this skill

Load this skill whenever the user asks to:
- "humanize", "de-AI", "de-slop", or "un-ChatGPT" a piece of text
- rewrite something so it doesn't sound like it was written by an LLM
- edit a draft (blog post, essay, PR description, docs, memo, email, tweet, resume bullet) to sound more natural
- match their voice in writing they're producing
- review text for AI tells before publishing

Also apply this skill to **your own** output when writing user-facing prose, release notes, PR descriptions, documentation, long-form explanations, summaries. the agent's baseline voice already strips most of these, but a focused pass catches what slips through.

## How to use it in the agent

The text usually arrives one of three ways:
1. **Inline**, user pastes the text directly into the message. Work on it in-place, reply with the rewrite.
2. **File**, user points at a file. Use `read_file` to load it, then `patch` or `write_file` to apply edits. For markdown docs in a repo, a targeted `patch` per section is cleaner than rewriting the whole file.
3. **Voice calibration sample**, user provides an additional sample of their own writing (inline or by file path) and asks you to match it. Read the sample first, then rewrite. See the Voice Calibration section below.

Always show the rewrite to the user. For file edits, show a diff or the changed section, don't silently overwrite.

## Your task

When given text to humanize:

The rest: https://github.com/mateaix/mateclaw/blob/HEAD/mateclaw-server/src/main/resources/skills/humanizer/SKILL.md