Slop Cop

What the tool does

• Flags stylistic patterns strongly associated with current LLM output (e.g., formulaic openings, “staccato burst” short sentences, hedging, rule-of-three lists, overused intensifiers).
• Author and several commenters stress it is not an AI-authorship detector, but an “LLM cliché detector.”
• Acknowledged that many flagged patterns were already common human clichés before LLMs; models amplified them.

Reception and naming

• Some like the concept and find the visualization of “slop” patterns eye-opening.
• Others say the name (“cop”) and framing feed into a punitive “AI detective” culture and may fuel false accusations.
• Mixed views on the name: seen as catchy and descriptive by some, rude and self-sabotaging by others.

Usefulness and potential applications

• Seen as helpful for business/technical writing to cut fluff, get to the point, and reduce corporate/LinkedIn-style language.
• A few use similar rule sets to post-process AI-written drafts, improving clarity and reducing obvious “slop.”
• Some want a browser extension or built-in browser feature to quickly assess whether an article “looks like AI” before investing time.

Critiques and concerns

• Many report high false-positive rates on their own writing and on classic authors; tool often flags legitimate rhetorical devices and personal style.
• Strong criticism of its prescriptive advice: guidance on intensifiers, hedges, triples, and “broader implications” is seen as over-absolute, context-blind, and sometimes logically wrong.
• Fear that following all suggestions will homogenize prose, strip personality, and encourage performative self-censorship rather than better writing.
• Some argue the core problem of AI prose is emptiness and wordy padding, not the specific surface constructions the tool targets.

Writing quality, AI slop, and style

• Thread broadens into a discussion of good writing: brevity vs verbosity, BLUF (bottom line up front), clarity, and audience-specific style.
• Debate over whether patterns like the rule of three or “not X, but Y” are inherently tainted by LLMs or still valuable when used judiciously.
• Several note that “human slop” and “AI slop” can look similar; what matters is information density, substance, and genuine intent.

Technical and implementation notes

• Some object to entering an API key in a web app; author points to local, open-source use and notes it could target local models instead of Anthropic.
• Current heuristics are English- and whitespace-centric; CJK languages break some rules (e.g., mislabeling entire sentences as fragments).