ai-slop-detector · git:20261025.7c7d700 · 2026-10-25 · sha256 7f05cd81a8d1d414

ai-slop-detector git:20261025.7c7d700A

Immutable. This exact content never changes and is served at /api/v1/blob/7f05cd81a8d1d414.

---
name: ai-slop-detector
description: Finds "AI slop" writing patterns, such as cliché phrases ("delve", "in today's fast-paced world"), em-dash overload, uniform sentence rhythm, reflexive triads, and empty conclusions, using a scoring script, then rewrites the text to sound specific and human while keeping the author's meaning and voice. Use when the user asks to humanize text, remove AI-sounding phrasing, de-slop a draft, or check whether writing sounds robotic.
---

# AI Slop Detector

Make writing sound like a specific human wrote it, not an average of the internet.

## 1. Scan

```bash
python3 scripts/slop_scan.py draft.md          # file
pbpaste | python3 scripts/slop_scan.py -       # stdin
```

The script prints a **slop-signal score from 0 to 100**, the flagged lines with line numbers, em-dash density and sentence-rhythm uniformity.

## 2. Diagnose the patterns the script can't catch

- Generic claims with no specifics (no names, numbers, examples).
- Reflexive "X, Y, and Z" triads, and "It's not just A, it's B" constructions.
- Empty openers and closers ("In conclusion", "Ultimately", "I hope this helps!").
- Hedging stacks ("may potentially help to"), and bullet lists where prose would read better.
- The same paragraph shape repeated over and over.

## 3. Rewrite

- Keep the meaning, the facts and the author's voice. Ask for a sample of their own writing if you can.
- Replace abstractions with concrete details **the author supplies**. Never invent anecdotes or data. Mark the gaps as `[add a real example]`.
- Vary sentence length, use plain verbs, and cut filler and most em-dashes.
- Show the top 5 changes as before → after, then the full rewrite. Re-run the scanner to confirm the score dropped.

## Rules

- This measures **style signals, not authorship**. Never claim it proves text was written by AI, and don't use it to accuse students, employees or writers.
- Don't strip technical terms that are correct in context ("robust" in statistics, "leverage" in finance).