Skip to content

Aboudjem/humanizer-skill / skills/humanizer

humanizer

Verified

Detects 55 AI writing patterns and rewrites text in five voice profiles so it reads like a specific human wrote it, with an optional 0-100 AI-tell score. Use when text sounds AI-generated or like a chatbot, when preparing a blog post, README, or LinkedIn post for publication, when auditing prose for AI tells, or when editing a Markdown file in place. Triggers on phrases like "humanize this", "make this sound less AI", "make this sound human", "remove AI tells", "does this read like ChatGPT", and "rewrite so it does not sound AI-generated". Pure Markdown, zero dependencies, no network calls.

FileKindSize
README.mdmarkdown4.0 KB
SKILL.mdskill md38.1 KB
evals/evals.jsonconfig3.2 KB
references/always-on-templates.mdmarkdown2.9 KB
references/patterns.mdmarkdown25.3 KB
references/patterns.zh.mdmarkdown14.6 KB
# Humanizer

A standalone Claude Code skill that transforms AI-generated text into natural human writing. Drop it into any plugin. No dependencies, no MCP server, no configuration.

## What it does

- Detects **55 AI writing patterns** (P1-P55, based on Wikipedia's "Signs of AI Writing" + 2025-2026 community research + the wider humanizer ecosystem)
- Rewrites text to sound like a specific human wrote it
- Injects authentic voice using burstiness and perplexity principles
- Three modes: scan-only, full rewrite, in-place file editing
- 5 voice profiles: casual, professional, technical, warm, blunt
- Zero dependencies. Pure Markdown. Works in every editor that reads skill files.

## Installation

### As a standalone skill

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

### Inside a plugin

Copy `SKILL.md` into your plugin's `skills/humanizer/` directory. Add to your plugin's skill registry if applicable.

### Usage

```
# Full rewrite (default)
/humanizer "Your AI-sounding text goes here"

# Scan only: report patterns without changing text
/humanizer "text" --mode detect

# Score the AI-tell density (0-100, lower is more human)
/humanizer "text" --mode detect --score

# Edit a file in place
/humanizer --mode edit --file src/docs/README.md

# Specify voice
/humanizer "text" --voice casual

# Aggressive mode + iterate to convergence (max 3 passes)
/humanizer "text" --aggressive --iterate 3

# Layer purpose-specific rules on top of voice
/humanizer "text" --voice warm --purpose marketing
```

### Voice options

| Voice | Best for |
|---|---|
| `casual` | Blog posts, social media, informal docs |
| `professional` | Business communication, formal docs |
| `technical` | API docs, READMEs, code comments |
| `warm` | Tutorials, onboarding, support content |
| `blunt` | Internal comms, reviews, direct feedback |

### Purpose presets (`--purpose`)

Layered on top of voice. Add content-type rules without losing voice flavor.

| Purpose | Effect |
|---|---|
| `essay` | No contractions, formal headings, structured arguments |
| `email` | Greetings allowed, signoff allowed, no markdown |
| `marketing` | Short paragraphs, concrete benefits, one CTA at end |
| `technical` | Code blocks preserved, precise jargon retained |
| `general` | No purpose-specific overrides (default) |

### Brand voice file

Drop a `humanizer-context.md` at the project root with your samples and banned phrases. Auto-loaded if present.

## How it works

1. **Parse**: Extracts text and flags from arguments
2. **Detect**: Scans for 55 AI patterns across 6 categories (content, language, style, communication, filler, craft/forensic) + emerging 2026 patterns
3. **Inject**: Applies voice profile, varies sentence length (burstiness), increases word unpredictability (perplexity)
4. **Verify**: Checks output against detection patterns, sentence variance, and the "who wrote this?" test
5. **Output**: Clean text with change summary

## Pattern categories

| Category | Patterns | Examples |
|---|---|---|
| Content | P1-P8 | Significance inflation, notability name-dropping, -ing phrases, copula avoidance |
| Language & Style | P9-P18 | Negative parallelisms, em dash overuse, bold abuse, list syndrome |
| Communication | P19-P21 | Chatbot artifacts, disclaimers, sycophancy |
| Filler & Hedging | P22-P30 | Filler phrases, hedging, generic conclusions, uniform sentence length |
| Emerging (2026) | P31-P43 | Elegant variation, citeturn markup leaks, utm_source=chatgpt URLs, treadmill effect |
| Craft & Forensic | P44-P55 | False agency, diff-anchored writing, reasoning-chain artifacts, unicode obfuscation, argument residue |

Deep dives and provenance live in [`references/patterns.md`](references/patterns.md); the core `SKILL.md` is standalone and does not require it.

## Credits

Built from research across:
- [Wikipedia: Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing)
- William Strunk Jr., *The Elements of Style* (1918)
- Community research from Reddit, HackerNews, and writing communities

## License

MIT
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall