Why I Built My Own Humanizer (And Why You Should Too)

There's a tool called humanizer a Claude Code skill built by blader, inspired by Wikipedia's guide to detecting AI writing. It's good. 4,100 stars, hundreds of forks, an active community adding patterns and language support. If you want to strip AI tells from any text, it does that well. I used it. Then I built something different. The problem isn't that humanizer is wrong. It's that it's solving a slightly different problem than the one I actually have. Humanizer checks your writing against a generic human baseline. It knows what AI writing looks like and flags the patterns, significance inflation, copula avoidance, the rule of three, em dash overuse. Twenty-four patterns derived from Wikipedia's AI cleanup guide. Run your draft through it, find the tells, rewrite. That works if your goal is writing that doesn't look AI-generated. My goal is writing that sounds like me. Those are related but not the same thing. I can write a draft that passes every humanizer check and still sounds not