humanizer

Rewrites prose to remove AI writing artifacts and apply natural human voice patterns.

2|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Arasz/ai-badger --skill humanizer-arasz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: humanizer
Source: https://github.com/Arasz/ai-badger/tree/main/features/common/skills/humanizer
Command: npx skills add https://github.com/Arasz/ai-badger --skill humanizer-arasz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated drafts carry recognizable tells: uniform sentence lengths, overused vocabulary like "delve" and "leverage", em dashes, copula avoidance, and forced bullet structures. This Skill detects and strips those artifacts so documentation, blog posts, release notes, and PR descriptions read as natural human writing. ## Core Features & Use Cases - Anti-Vocabulary Purge: Removes overused AI words and n-grams ("delve", "testament", "robust", "tapestry") and enforces a zero em dash rule. - Statistical Humanization Levers: Injects burstiness (mixing 3-word and 35-word sentences), converts copula phrases like "serves as" to active verbs, and replaces abstract claims with concrete specifics. - Two-Pass Self-Audit: Runs an explicit second pass asking "What makes this still sound like an LLM?" to catch tells the first rewrite missed. - Use Case: Before publishing a release note drafted by an AI assistant, run this Skill to strip filler connectors, flatten artificial bullet lists, and ground vague claims in concrete numbers. ## Quick Start Humanize this draft blog post to remove AI writing patterns and make it sound natural.

Frequently Asked Questions about humanizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI-generated text sound more human?

Apply statistical humanization levers: vary sentence length between 3 and 35 words, purge overused AI vocabulary like "delve" and "leverage", eliminate em dashes, and replace abstract claims with concrete specifics. A second audit pass catches remaining tells.

What words reveal that text was written by AI?

Common AI vocabulary markers include "delve", "leverage", "utilize", "robust", "comprehensive", "pivotal", "nuanced", "tapestry", "testament", and "underscores". Structural tells include uniform sentence pacing, em dashes, and forced bold bullet lists.

Can I use this for documentation and release notes?

Yes, the Skill targets documentation, READMEs, tutorials, release notes, PR descriptions, and emails. It preserves technical precision, code snippets, and exact parameters while removing empty buzzwords and filler connectors.

Why does AI text still sound robotic after one editing pass?

The model that wrote the original draft often misses its own AI tells during a single edit. The Skill requires an explicit second pass asking "What makes this still sound like an LLM?" to catch lingering artifacts like em dashes that sneak back in.

Does humanizing text remove technical accuracy?

No, the Skill explicitly preserves required technical terms, code snippets, and precise parameters. It only removes empty buzzwords and vague generalizations, replacing them with concrete details like specific latency numbers.