skills/humanizer/SKILL.md
Strip LLM tells from text so it reads human. Triggers: humanize, sounds like AI, too robotic, natural rewrite, AI slop, or obvious LLM patterns. Reference: https://en.wikipedia.org/wiki/WP:Signs_of_AI_writing
npx skillsauth add olamedia/analytics-skills humanizerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Rewrite to remove identifiable LLM patterns. Never use the vocabulary below unless the subject truly requires a word.
Kill list — vocabulary: additionally, align with, boasts, bolstered, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract), meticulous/meticulously, pivotal, showcase, tapestry (abstract), testament, underscore (verb), valuable, vibrant, nestled, in the heart of, groundbreaking, renowned, diverse array, rich (filler adjective), profound, commitment to, natural beauty, serves as, stands as, marks a shift, setting the stage, evolving landscape, focal point, indelible mark, deeply rooted.
Structural tells: Neat parallel headers (## The Problem / ## The Solution / ## The Result). Rule of three everywhere — vary count (2 or 4 sometimes). Balanced “It does X when it should do Y” — break symmetry. Drop “not just X, but also Y”. Drop despite-challenges + forced optimism. Cut superficial -ing closers (“highlighting…”, “underscoring…”, “reflecting…”). Don’t elegant-variation — repeat the term. Don’t replace is with serves as / stands as / marks / represents. No title case on every heading; no bold-every-term list styling; no 1. **Step**: blob inline-header lists.
Tone tells: Too even and polished; promotional puff; vague “experts say” / “research suggests” without sources; outlook / “challenges and opportunities” endings; hedge-then-assert (“While X is minor, it plays a crucial role…”).
Rewrite: (1) Spot tells. (2) Strip neat sectioning — merge or drop headers so it can breathe. (3) Vary sentence length — mix fragments and longer lines. (4) Allow meander, tangent, repeat from another angle. (5) Casual register where fit — contractions, fragments, “yeah”, “look”, “honestly”. (6) Swap abstraction for specifics — what actually happened. (7) Allow lopsided takes — drop fake balance. (8) Rough edges OK — not every transition or topic sentence. (9) Delete sentences that only say importance in fancy words. (10) Mental read-aloud — if press release or Wikipedia, revise.
Do not: Only synonym-swap while keeping stiff shape (structure beats wording). Add typos or bad grammar on purpose. Over-slang past the register the user wants. Lose real content — ideas stay, packaging changes.
testing
Rebase current feature branch onto master (or configured base) with automated conflict resolution. Handles pre-checks, conflict classification, and post-rebase verification. Use when the user asks to rebase, update a branch, sync with master, or resolve rebase conflicts.
development
FE feature analysis from raw idea (or YouTrack ticket) through to a split-aware developer briefs. Produces context-map.md, requirements.md, task-brief-{side}.md. Generic — project knowledge is auto-discovered.
testing
Concise technical communication that stays readable and honest. Cuts fluff about fifty to seventy percent while keeping natural flow, uncertainty markers, and human tone. Levels lite (default), mid, tight. Short SKILL body; rules below are complete.
development
Guide frontend development toward websites that feel premium and trustworthy, grounded in cognitive science research (processing fluency, prototypicality). Two modes: active guidance during build, and audit (problems + suggestions). Use when building UI, reviewing frontend code, or when the user mentions premium, trust, design quality, audit, review, or frontend polish.