Unofficial community guide for blader/humanizer. Not affiliated with blader. All trademarks belong to their owners.
The blader humanizer is a Claude Code skill that detects and removes signs of AI-generated writing. According to its listing on Shyft it analyses 25 patterns commonly found in AI output, rewrites the text to improve flow and authenticity, supports voice calibration from samples of your own writing, and runs in Claude Code and OpenCode. A dev.to article from February describes it as built by blader and inspired by Wikipedia's guide to detecting AI writing, with 6,600 stars and hundreds of forks at the time. This page compares the realistic alternatives, using only what those pages state.
If the goal is published articles rather than post-processed drafts, try Supatraffic - SEO articles with cover images and autopilot publishing. It writes the piece, makes the cover image and publishes on a schedule.
| Option | What it is | Where it runs | Voice calibration | How you get it |
|---|---|---|---|---|
| blader/humanizer | Claude Code skill; detects and removes AI writing patterns | Claude Code, OpenCode | Yes, from samples of your writing | claude install blader/humanizer or git clone |
| Build your own skill | A personal humanizer skill you write and tune | Whatever agent you use | Whatever you build in | Your own repo |
| Manual edit with Wikipedia's guide | Apply the AI-writing signs by hand | Any editor | You are the voice | Read the guide |
| Same skill in OpenCode | blader/humanizer loaded in OpenCode instead of Claude Code | OpenCode | Yes, same skill | Same install, different agent |
| SourceForge mirror | A mirror of the humanizer skill source | Not applicable | Same skill | SourceForge project page |
| Supatraffic | SEO article writing with cover images and autopilot publishing | Browser | Not stated here | Web app |
The reference option. Shyft's listing describes it as a skill for Claude Code and OpenCode that finds and removes robotic patterns, improves flow and adds conversational nuance, with 25 patterns analysed and voice calibration from your own samples. Install is one line: claude install blader/humanizer, or git clone https://github.com/blader/humanizer. The listed requirement is Claude Code or a compatible AI agent. Shyft's usage steps are worth following: feed it drafts that are already about 80% complete, state the desired tone, read the output aloud, and compare against your brand voice before shipping.
Daniel Nwaneri's dev.to post "Why I Built My Own Humanizer (And Why You Should Too)" argues for exactly that. He acknowledges the original is good, then makes the case that your own skill can encode your own patterns and preferences rather than a general-purpose list. The cost is maintenance: you own the pattern list and have to notice when your writing drifts. The benefit is that nobody else's idea of "natural" gets applied to your text.
Both sources trace the skill back to Wikipedia's guide to detecting AI writing. Reading that guide and editing by hand is the zero-dependency route. It is slow, but it teaches you what the patterns are, which makes every automated option easier to evaluate. Reasonable for a handful of important pieces; unreasonable for a content calendar.
Shyft lists OpenCode alongside Claude Code as a host for the skill. If your team already runs OpenCode, this is not really a different tool, just a different agent loading the same skill, so the output should match. Pick this when the constraint is the agent, not the humanizer.
A SourceForge project titled humanizer-skill.mirror exists. The page could not be fetched when this list was compiled, so treat it purely as a fallback for environments where GitHub is blocked and verify the contents against the GitHub repository before use.
A different category. Supatraffic does not post-process a draft you already have; it writes SEO articles, generates cover images and publishes them on autopilot. Whether the output needs a humanizing pass is your call to make after reading it. It is the option to consider when the actual job is "publish N articles a week" rather than "clean up this paragraph".
- You use Claude Code or OpenCode and want a maintained pattern list: blader/humanizer.
- You have strong opinions about your own voice and time to maintain them: build your own, per the dev.to post.
- You edit a few high-stakes pieces a month: Wikipedia's guide and your own hands.
- GitHub is unreachable in your environment: the SourceForge mirror, verified against the original.
- The bottleneck is producing and publishing articles, not polishing them: Supatraffic.
Every humanizer above assumes you already have a draft and a place to put it. If you are still producing the drafts, sourcing cover images and scheduling posts by hand, that pipeline is the real time sink. Try Supatraffic - SEO articles with cover images and autopilot publishing to get the article, the image and the publish step from one place, then run a humanizer pass on anything that needs your voice.
Last reviewed: 2026-09-22