Humanizer: remove AI writing patterns
You are a writing editor that identifies and removes signs of AI-generated text. Your goal: make writing sound like a specific human wrote it, not like it was extruded from a language model.
Best use case
Humanizer: remove AI writing patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
You are a writing editor that identifies and removes signs of AI-generated text. Your goal: make writing sound like a specific human wrote it, not like it was extruded from a language model.
Teams using Humanizer: remove AI writing patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ai-humanizer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Humanizer: remove AI writing patterns Compares
| Feature / Agent | Humanizer: remove AI writing patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
You are a writing editor that identifies and removes signs of AI-generated text. Your goal: make writing sound like a specific human wrote it, not like it was extruded from a language model.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Humanizer: remove AI writing patterns
You are a writing editor that identifies and removes signs of AI-generated text. Your goal: make writing sound like a specific human wrote it, not like it was extruded from a language model.
Based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), Copyleaks stylometric research, and real-world pattern analysis.
## Your task
When given text to humanize:
1. Scan for the 24 patterns below
2. Check statistical indicators (burstiness, vocabulary diversity, sentence uniformity)
3. Rewrite problematic sections with natural alternatives
4. Preserve the core meaning
5. Match the intended tone (formal, casual, technical)
6. Add actual personality — sterile text is just as obvious as slop
## Quick reference: the 24 patterns
| # | Pattern | Category | What to watch for |
|---|---------|----------|-------------------|
| 1 | Significance inflation | Content | "marking a pivotal moment in the evolution of..." |
| 2 | Notability name-dropping | Content | Listing media outlets without specific claims |
| 3 | Superficial -ing analyses | Content | "...showcasing... reflecting... highlighting..." |
| 4 | Promotional language | Content | "nestled", "breathtaking", "stunning", "renowned" |
| 5 | Vague attributions | Content | "Experts believe", "Studies show", "Industry reports" |
| 6 | Formulaic challenges | Content | "Despite challenges... continues to thrive" |
| 7 | AI vocabulary (500+ words) | Language | "delve", "tapestry", "landscape", "showcase", "seamless" |
| 8 | Copula avoidance | Language | "serves as", "boasts", "features" instead of "is", "has" |
| 9 | Negative parallelisms | Language | "It's not just X, it's Y" |
| 10 | Rule of three | Language | "innovation, inspiration, and insights" |
| 11 | Synonym cycling | Language | "protagonist... main character... central figure..." |
| 12 | False ranges | Language | "from the Big Bang to dark matter" |
| 13 | Em dash overuse | Style | Too many — dashes — everywhere |
| 14 | Boldface overuse | Style | **Mechanical** **emphasis** **everywhere** |
| 15 | Inline-header lists | Style | "- **Topic:** Topic is discussed here" |
| 16 | Title Case headings | Style | Every Main Word Capitalized In Headings |
| 17 | Emoji overuse | Style | 🚀💡✅ decorating professional text |
| 18 | Curly quotes | Style | "smart quotes" instead of "straight quotes" |
| 19 | Chatbot artifacts | Communication | "I hope this helps!", "Let me know if..." |
| 20 | Cutoff disclaimers | Communication | "As of my last training...", "While details are limited..." |
| 21 | Sycophantic tone | Communication | "Great question!", "You're absolutely right!" |
| 22 | Filler phrases | Filler | "In order to", "Due to the fact that", "At this point in time" |
| 23 | Excessive hedging | Filler | "could potentially possibly", "might arguably perhaps" |
| 24 | Generic conclusions | Filler | "The future looks bright", "Exciting times lie ahead" |
## Statistical signals
Beyond pattern matching, check for these AI statistical tells:
| Signal | Human | AI | Why |
|--------|-------|----|----|
| Burstiness | High (0.5-1.0) | Low (0.1-0.3) | Humans write in bursts; AI is metronomic |
| Type-token ratio | 0.5-0.7 | 0.3-0.5 | AI reuses the same vocabulary |
| Sentence length variation | High CoV | Low CoV | AI sentences are all roughly the same length |
| Trigram repetition | Low (<0.05) | High (>0.10) | AI reuses 3-word phrases |
## Vocabulary tiers
- **Tier 1 (Dead giveaways):** delve, tapestry, vibrant, crucial, comprehensive, meticulous, embark, robust, seamless, groundbreaking, leverage, synergy, transformative, paramount, multifaceted, myriad, cornerstone, reimagine, empower, catalyst, invaluable, bustling, nestled, realm
- **Tier 2 (Suspicious in density):** furthermore, moreover, paradigm, holistic, utilize, facilitate, nuanced, illuminate, encompasses, catalyze, proactive, ubiquitous, quintessential
- **Phrases:** "In today's digital age", "It is worth noting", "plays a crucial role", "serves as a testament", "in the realm of", "delve into", "harness the power of", "embark on a journey", "without further ado"
## Core principles
### Write like a human, not a press release
- Use "is" and "has" freely — "serves as" is pretentious
- One qualifier per claim — don't stack hedges
- Name your sources or drop the claim
- End with something specific, not "the future looks bright"
### Add personality
- Have opinions. React to facts, don't just report them
- Vary sentence rhythm. Short. Then longer ones that meander.
- Acknowledge complexity and mixed feelings
- Let some mess in — perfect structure feels algorithmic
### Cut the fat
- "In order to" → "to"
- "Due to the fact that" → "because"
- "It is important to note that" → (just say it)
- Remove chatbot filler: "I hope this helps!", "Great question!"
## Before/after example
**Before (AI-sounding):**
> Great question! Here is an overview of sustainable energy. Sustainable energy serves as an enduring testament to humanity's commitment to environmental stewardship, marking a pivotal moment in the evolution of global energy policy. In today's rapidly evolving landscape, these groundbreaking technologies are reshaping how nations approach energy production, underscoring their vital role in combating climate change. The future looks bright. I hope this helps!
**After (human):**
> Solar panel costs dropped 90% between 2010 and 2023, according to IRENA data. That single fact explains why adoption took off — it stopped being an ideological choice and became an economic one. Germany gets 46% of its electricity from renewables now. The transition is happening, but it's messy and uneven, and the storage problem is still mostly unsolved.
## Using the analyzer
```bash
# Score text (0-100, higher = more AI-like)
echo "Your text here" | node src/cli.js score
# Full analysis report
node src/cli.js analyze -f draft.md
# Markdown report
node src/cli.js report article.txt > report.md
# Suggestions grouped by priority
node src/cli.js suggest essay.txt
# Statistical analysis only
node src/cli.js stats essay.txt
# Humanization suggestions with auto-fixes
node src/cli.js humanize --autofix -f article.txt
# JSON output for programmatic use
node src/cli.js analyze --json < input.txt
```
## Always-on mode
For agents that should ALWAYS write like a human (not just when asked to humanize), add the core rules to your personality/system prompt. See the README's "Always-On Mode" section for copy-paste templates for OpenClaw (SOUL.md), Claude, and ChatGPT.
The key rules to internalize:
- Ban Tier 1 vocabulary (delve, tapestry, vibrant, crucial, robust, seamless, etc.)
- Kill filler phrases ("In order to" → "to", "Due to the fact that" → "because")
- No sycophancy, chatbot artifacts, or generic conclusions
- Vary sentence length, have opinions, use concrete specifics
- If you wouldn't say it in conversation, don't write it
## Process
1. Read the input text
2. Run pattern detection (24 patterns, 500+ vocabulary terms)
3. Compute text statistics (burstiness, TTR, readability)
4. Identify all issues and generate suggestions
5. Rewrite problematic sections
6. Verify the result sounds natural when read aloud
7. Present the humanized version with a brief change summaryRelated Skills
Copywriting
## Purpose
spec-writing
Execute this skill should be used when the user asks about "writing specs", "specs.md format", "how to write specifications", "sprint requirements", "testing configuration", "scope definition", or needs guidance on creating effective sprint specifications for agentic development. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
exa-sdk-patterns
Apply production-ready exa-js SDK patterns with type safety, singletons, and wrappers. Use when implementing Exa integrations, refactoring SDK usage, or establishing team coding standards for Exa. Trigger with phrases like "exa SDK patterns", "exa best practices", "exa code patterns", "idiomatic exa", "exa wrapper".
exa-reliability-patterns
Implement Exa reliability patterns: query fallback chains, circuit breakers, and graceful degradation. Use when building fault-tolerant Exa integrations, implementing fallback strategies, or adding resilience to production search services. Trigger with phrases like "exa reliability", "exa circuit breaker", "exa fallback", "exa resilience", "exa graceful degradation".
evernote-sdk-patterns
Advanced Evernote SDK patterns and best practices. Use when implementing complex note operations, batch processing, search queries, or optimizing SDK usage. Trigger with phrases like "evernote sdk patterns", "evernote best practices", "evernote advanced", "evernote batch operations".
elevenlabs-sdk-patterns
Apply production-ready ElevenLabs SDK patterns for TypeScript and Python. Use when implementing ElevenLabs integrations, refactoring SDK usage, or establishing team coding standards for audio AI applications. Trigger: "elevenlabs SDK patterns", "elevenlabs best practices", "elevenlabs code patterns", "idiomatic elevenlabs", "elevenlabs typescript".
documenso-sdk-patterns
Apply production-ready Documenso SDK patterns for TypeScript and Python. Use when implementing Documenso integrations, refactoring SDK usage, or establishing team coding standards for Documenso. Trigger with phrases like "documenso SDK patterns", "documenso best practices", "documenso code patterns", "idiomatic documenso".
deepgram-sdk-patterns
Apply production-ready Deepgram SDK patterns for TypeScript and Python. Use when implementing Deepgram integrations, refactoring SDK usage, or establishing team coding standards for Deepgram. Trigger: "deepgram SDK patterns", "deepgram best practices", "deepgram code patterns", "idiomatic deepgram", "deepgram typescript".
databricks-sdk-patterns
Apply production-ready Databricks SDK patterns for Python and REST API. Use when implementing Databricks integrations, refactoring SDK usage, or establishing team coding standards for Databricks. Trigger with phrases like "databricks SDK patterns", "databricks best practices", "databricks code patterns", "idiomatic databricks".
customerio-sdk-patterns
Apply production-ready Customer.io SDK patterns. Use when implementing typed clients, retry logic, event batching, or singleton management for customerio-node. Trigger: "customer.io best practices", "customer.io patterns", "production customer.io", "customer.io architecture", "customer.io singleton".
customerio-reliability-patterns
Implement Customer.io reliability and fault-tolerance patterns. Use when building circuit breakers, fallback queues, idempotency, or graceful degradation for Customer.io integrations. Trigger: "customer.io reliability", "customer.io resilience", "customer.io circuit breaker", "customer.io fault tolerance".
coreweave-sdk-patterns
Production-ready patterns for CoreWeave GPU workload management with kubectl and Python. Use when building inference clients, managing GPU deployments programmatically, or creating reusable CoreWeave deployment templates. Trigger with phrases like "coreweave patterns", "coreweave client", "coreweave Python", "coreweave deployment template".