Help us improve
Share bugs, ideas, or general feedback.
From bopen-tools
Strips AI writing patterns from prose — removes negation-then-contrast, limits parallel lists, eliminates indirect repetition. Use for any human-facing text.
npx claudepluginhub b-open-io/claude-plugins --plugin bopen-toolsHow this skill is triggered — by the user, by Claude, or both
Slash command
/bopen-tools:humanizeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Strip AI writing patterns from prose. Follow these three rules exactly.
Removes 24 AI-generated writing patterns like significance inflation, promotional language, and vague attributions from text to make it sound natural and human-written.
Humanizes AI-generated text by detecting and rewriting patterns like inflated symbolism, em dash overuse, passive voice, rule of three, and filler phrases. Use for editing or reviewing docs and code comments.
Humanizes text by removing AI-generated patterns from Wikipedia's guide, rewriting for natural flow, and adding personality. Use after drafting copy.
Share bugs, ideas, or general feedback.
Strip AI writing patterns from prose. Follow these three rules exactly.
Before writing any sentence, check: does it say what something ISN'T before saying what it IS? Or does it append "not just X" to trash the alternative and prop up the claim? If either, delete the negative part. Keep only the positive claim. Let it stand on its own.
Examples:
When you write a list, count the items. If there are exactly 3 items in parallel structure, either remove one (making it 2) or add one (making it 4).
This applies everywhere: adjective lists, verb lists, noun lists, parallel sentences.
Never restate the same point in different words for emphasis. Say it once clearly and move on. If the first sentence already conveys the meaning, the restating sentence is dead weight.
After writing, check the last sentence of every paragraph. Count its words. At most ONE paragraph may end with a sentence under 15 words. All other paragraphs must end with a sentence of 20+ words that includes a specific detail, number, or example.
After writing any prose, you must do a concrete revision pass before delivering. This is not optional — the first draft will contain AI patterns no matter how carefully you write it. Do these checks mechanically:
Do this revision pass silently — don't mention it in your output. Just deliver the cleaned text.
Before delivering revised prose:
After editing, rate the text 1–10 on each dimension:
| Dimension | Question to ask |
|---|---|
| Directness | Does it state facts, or announce them? |
| Rhythm | Are sentences varied in length and structure? |
| Trust | Does it respect reader intelligence? |
| Voice | Does it sound like a person wrote it? |
| Density | Is anything cuttable without losing meaning? |
Below 35/50: revise again.
AI version (bad):
Speed. We don't just build fast infrastructure — we build infrastructure that's fast, reliable, and scalable. Your transactions process in milliseconds, not minutes. That's the difference.
Humanized version (good):
Speed. Transactions process in under 200ms. We cache settlement data locally so round-trips to the clearinghouse don't block your checkout flow. Most integrations go live in a day or two.
Notice what changed: the binary contrast ("don't just X — we Y") is gone, the tricolon ("fast, reliable, and scalable") became specific claims, the punchline ending ("That's the difference") became a practical detail, and the paragraph ends with a long informational sentence rather than a mic-drop.
Good humanized prose: