humanizer-compact
Humanizer (compact)
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.
More from olamedia/analytics-skills
analyze-project
Use when starting work on any project to produce or update living documentation (TechStack.md, ProjectStructure.md) that bootstraps context for any AI agent session. Run before any feature work, or periodically to keep docs current.
13humanizer
>-
12architect
>-
12goal-definition
Use when you have a raw idea or request and need to define a clear goal with success criteria before exploring solutions. Use when requirements are vague, when "what does done look like" is unclear, or when assumptions need surfacing.
11prd
Use when you have a chosen direction and need to formalize requirements into a Product Requirements Document. Use when user stories, acceptance criteria, and scope boundaries need to be written down before architecture or implementation.
10analyze
Use when you have a raw idea or request and want to run the full analytics pipeline automatically — from research through to an interlinked task list. Best for straightforward problems where the full pipeline can flow with minimal back-and-forth.
10