humanizer
Remove AI writing patterns to make documentation sound natural, specific, and human. Covers content patterns, language patterns, style patterns, and communication patterns.
59
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/humanizer/SKILL.mdHumanizer
Identifies and removes AI-generated text patterns so writing sounds natural and specific instead of generic and hollow.
Process
- Read the input text.
- Identify AI patterns using the references below.
- Rewrite the problematic sections.
- Do a final anti-AI pass: ask "what makes this obviously AI generated?", name the remaining tells, and fix them.
Ensure the result sounds natural read aloud, varies sentence structure, uses specific details, and keeps the right tone.
Adding voice
Removing patterns is only half the job. Sterile, voiceless writing is just as obvious. Have opinions and react to facts instead of only reporting them. Vary sentence rhythm: short punchy sentences, then longer ones that take their time. Acknowledge complexity ("it works, but it also feels like a workaround"), use specific details, and let natural asides appear.
Pattern references
Load the category you need:
| Reference | Covers |
|---|---|
| content-patterns.md | Undue significance, empty credibility signals, -ing-participle filler, marketing language, vague attributions, generic filler sections |
| language-patterns.md | AI vocabulary, copula avoidance, negative parallelisms, rule-of-three, elegant variation, false ranges, filler and hedging, words to cut |
| style-patterns.md | Dashes and semicolons as punctuation, unnecessary bold, inline-header lists, title-case headings, emojis |
| communication-patterns.md | Chatbot artifacts, sycophantic openers |
- Repository
- kubb-labs/kubb
- Commit
8349acf
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.