AI Slop Detector
Added Jul 23, 2026
About This Prompt
This prompt audits any piece of writing for the specific, checkable patterns that make text read as AI-generated — without rewriting a word and without pretending to be an AI detector. That distinction matters: AI detection tools guess and produce false positives, while this audit names each pattern it finds, quotes the exact offending line, and suggests a fix you can accept or ignore. It checks nineteen pattern categories, from the banned-word list (delve, leverage, robust) through structural tells like binary contrasts, synonym cycling, fake-profound endings, and em dash overuse. Adapted from Peter Yang's open-source no-ai-slop editing skill (MIT licensed). Useful for auditing your own AI-assisted drafts before publishing, reviewing freelancer submissions, or teaching your team what to watch for.
Variables to Customize
[TEXT]
The text you want audited for AI-sounding patterns
Example: <!--email_off-->In today's ever-evolving digital landscape, this tool isn't just another app. It's a game changer. Experts agree that...<!--/email_off-->
Tips for Best Results
- Use this before publishing anything drafted with AI help — it catches patterns you have gone blind to after three rounds of edits
- The audit deliberately never says "this was written by AI" — quoted patterns are evidence you can verify, a verdict is just a guess
- Zero findings does not mean the writing is good, only that it avoids the common tells; judge the substance separately
- Pair it with the AI Slop Remover prompt when you want the fixes applied instead of just flagged
Example Output
<!--email_off-->PATTERN: Filler phrase + banned word QUOTE: "In today's ever-evolving digital landscape" FIX: Delete the phrase, start with the subject. PATTERN: Negative listing / binary contrast QUOTE: "this tool isn't just another app. It's a game changer." FIX: Say what the tool does instead. PATTERN: Weasel attribution QUOTE: "Experts agree that..." FIX: Name the expert or cut the claim. TOTAL: 4 patterns found in 2 sentences. Want me to apply these fixes to the full draft?<!--/email_off-->