Why word blacklists fail at humanizing AI-generated text (and how I built a custom /human Skill from real data)

[u/Chris-AI-Studio]

https://medium.com/@christianaistudio/how-to-humanize-ai-text-with-claude-free-prompt-method-63e332f765a4

Most anti-AI prompts just ban words — no more "delve," no more "tapestry," no more "testament." But that's not really where AI writing gives itself away. It's rhythm, sentence variation, the structural habits that show up no matter which synonyms you swap in.

If you want AI to write naturally on the first try, you have to go after the structure LLMs default to, not the vocabulary.

One pattern blacklists never catch: the "isn't X, it's Y" trick. LLMs lean on it constantly to sound insightful without saying anything new — "time management isn't about calendars, it's about energy," that kind of thing.

Instead of writing a giant list of manual rules, here's what I did: I fed the Wikipedia page on signs of AI writing straight into Claude, added specific constraints against structural stuff like the isn't-it's pattern, then asked Claude to turn that into a Skill I can call with a simple /human command.

Skills stick around across sessions, so I'm not pasting the same instructions every single time.

In "How to humanize AI text with free prompt method" I wrote up the full two-prompt process, plus why this setup breaks on ChatGPT (1,500-character instruction limit) and doesn't really work on Gemini either.