humanizer

Detect and rewrite AI-generated writing patterns to produce natural human-sounding text.

Updated May 18, 2024
One-click install
npx skills add https://github.com/joshhornby/dotfiles --skill humanizer-joshhornby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: humanizer
Source: https://github.com/joshhornby/dotfiles/tree/main/.claude/skills/humanizer
Command: npx skills add https://github.com/joshhornby/dotfiles --skill humanizer-joshhornby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated text carries recognizable tells — inflated symbolism, promotional language, negative parallelisms, em dash overuse, and templated phrases — that make writing feel robotic and erode reader trust. This Skill systematically finds and rewrites those patterns so text reads as naturally human. ## Core Features & Use Cases - 29-pattern detection framework: Scans text against a structured index of AI writing tells drawn from Wikipedia's "Signs of AI writing" guide and Blake Stockton's breakdowns, each with words-to-watch and before/after examples. - Mandatory negation sweep: Runs a Grep-based search for negative parallelism constructions ("not just X, it's Y") that survive casual read-throughs, then re-verifies after editing. - Voice restoration: Goes beyond removing bad patterns by adding rhythm variation, first-person perspective, and specific detail so the result has genuine personality rather than sterile neutrality. - Use Case: Paste a draft blog post or product announcement that reads as AI-generated; the Skill flags each pattern instance, rewrites the affected sentences, and returns a humanized version with a summary of changes. ## Quick Start Ask the AI to humanize a piece of text, for example: "Humanize this product announcement draft and remove any AI writing patterns."

Frequently Asked Questions about humanizer

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

FAQPage Schema
How do I remove AI writing patterns from text?

Run the text through a systematic pass against the 29-pattern index, checking for tells like "delve", "tapestry", negative parallelisms, and em dash overuse. Rewrite each flagged section with plain constructions and specific details while preserving the original meaning.

What are the most common signs of AI-generated writing?

The most frequent tells are overused vocabulary like "delve" and "underscore", negative parallelisms ("not just X, it's Y"), superficial -ing phrases, rule-of-three groupings, and vague attributions like "experts argue". The pattern index lists 29 documented signs with examples.

Why does AI text still sound robotic after removing obvious buzzwords?

Removing buzzwords alone leaves sterile, voiceless prose with uniform sentence lengths and no opinions. Natural writing needs varied rhythm, first-person perspective where appropriate, acknowledged uncertainty, and concrete specifics instead of neutral reporting.

How do I detect negative parallelism in a long document?

Use a Grep sweep with a regex covering "not just", "isn't", "rather than", and semicolon-pivot constructions rather than reading by eye, since negation hides in fluent prose. Judge each hit individually, then re-run the sweep after editing to confirm no pivots remain.

When should I not remove an AI writing pattern?

Keep constructions that carry genuine information, such as a factual negative like "the API doesn't support batching" or an em dash used for a real aside. Each flagged instance is a candidate for review, not an automatic deletion.