slop-cop

A universal prose audit with two parallel axes. Built on ~135 published sources spanning peer-reviewed linguistics, AI-detector vendor methodology, plain-language style guides (plainlanguage.gov, GOV.UK, Microsoft, Google), cognitive-load research (Miller, Sweller, Pinker), web-readability research (NN/g), and the Plain Writing Act / WCAG accessibility standards.

The one-line summary

Two axes, two verdicts. AI-Slop and Comprehension. A piece can pass one and fail the other.

• AI-Slop axis — Does this read like AI wrote it? Patterns, vocabulary, formatting, rhythm.
• Comprehension axis — Can a fresh reader follow this? Acronyms, named-entity bombing, telegraphic compression, readability, structure.

Single instances aren't a signal. Density is. Both axes use density-based scoring (per 500 words, weighted by severity) with the same verdict tiers (PASS / LOW / MEDIUM / HIGH / CRITICAL). The audit reports both and combines them into a single recommendation based on whichever is worse.

Why this skill exists

Our feeds are becoming shit. Our websites are becoming shit. Our repos are becoming shit. AI didn't make writing harder, it made writing easier, and now everyone uses the same shortcuts, the same shapes, the same words. Open ten landing pages in a row and you can't tell them apart.

I built this skill to make my own websites less shit, my clients' websites less shit, and my LinkedIn feed less of a copy-paste graveyard. Yes, AI wrote parts of this skill. That is not the problem. The problem is AI prose nobody catches: the safe, hedge-stacked, em-dash-heavy paragraph where every line is grammatically clean but the whole thing is forgettable.

I run this against my own work every day. Landing pages, blog posts, READMEs, pitch decks, cold emails. It catches the stuff I would have shipped. If someone uses it to score other people's writing, fine. The first job is policing yourself before you ship.

Running it daily means finding new things every week. A pattern I missed. A false alarm on real human prose. A new model with new tells. The list moves with the work. Expect a lot of changes.

Mode selection

Two modes. Pick one based on what the user wants.

If ambiguous, ask one short question: "Audit only, or do you want a revised version?"

When to skip

This skill governs prose meant for human readers. Skip it for:

• Code, code comments, commit messages, or PR descriptions
• Technical API documentation or reference material (different audience target — see calibration §10)
• Raw data, structured outputs (JSON, YAML, CSV)
• Direct quotations from other people that should preserve their voice
• Instructions to other agents or skills (system prompts, agent briefs)
• Intentionally formal or legal documents (different audience target)
• Dialogue under another character's voice in fiction (apply voice-aware judgment)

The audit workflow

Five steps. The scanner does the mechanical work on both axes; reading does the qualitative work; calibration converts findings into two verdicts plus a combined recommendation.

Step 1 — Run the scanner

python3 scripts/scan.py /path/to/draft.md
echo "draft text..." | python3 scripts/scan.py

Flags:

# Compact one-screen output (for embedding in other skills):
python3 scripts/scan.py --quick draft.md

# Structured JSON for programmatic use:
python3 scripts/scan.py --json draft.md

# Set audience for comprehension-axis calibration:
python3 scripts/scan.py --audience marketing draft.md
python3 scripts/scan.py --audience academic draft.md
python3 scripts/scan.py --audience technical draft.md

# Override AI-slop genre detection:
python3 scripts/scan.py --genre encyclopedic draft.md

# Mahmoud-mode: treat ALL em dashes as H severity:
python3 scripts/scan.py --strict-em-dash draft.md

The scanner outputs:

• Two verdicts (AI-Slop, Comprehension) with density scores
• Combined recommendation
• Per-axis violation breakdown
• Readability metrics panel (Flesch RE, FK Grade, SMOG, Coleman-Liau, Dale-Chall, lexical density, avg sentence length, passive voice %)
• Density signals (acronym density, named-entity density, numeric density per sentence)
• Burstiness, contraction ratio, model fingerprint

Step 2 — Read against both pattern catalogs

AI-Slop axis: Load references/patterns.md. Walk through the 45 patterns by group. The scanner catches the mechanically-detectable subset; the rest requires reading.

Comprehension axis: Load references/comprehension.md. Walk through the 35 patterns by group. Roughly 17 are mechanically detectable; the rest require reading. Particularly:

• Buried lede / missing thesis — does the first paragraph tell the reader the point?
• No topic sentences — does each paragraph open with its claim?
• Curse of knowledge — does the writer assume context the reader lacks?
• No concrete examples — does every abstract claim have a specific instance?
• Definition by synonym — are domain terms defined with concrete examples or just other jargon?

For each pattern (both axes), flag with quote + severity.

Step 3 — Apply calibration

Load references/calibration.md. Apply:

1. Density-based scoring on both axes (§1 for AI-Slop, §9 for Comprehension)
2. Genre adjustment (AI-Slop: §3) and audience calibration (Comprehension: §10)
3. Compound triggers — escalate when 3+ H tells in one paragraph (slop) or any 100w window has 3+ undefined acronyms / 5+ named entities (comp)
4. Cross-axis recommendation (§11) — single sentence based on whichever axis is worse

The scanner does most of this automatically. The reader applies judgment to ambiguous cases.

Step 4 — Output the audit report

Use the dual-verdict format in references/audit-report-template.md. The report has:

• Two verdicts (AI-Slop and Comprehension) in a header table
• Combined recommendation — one sentence drawn from cross-axis matrix
• Stats block — word count, audience, burstiness, model fingerprint
• AI-Slop axis section — counts, top fixes, mechanical violations, qualitative violations, calibration notes
• Comprehension axis section — counts, top fixes, readability metrics panel, density signals, mechanical violations, qualitative violations, calibration notes
• Combined top 3 fixes — pulled from both axes by impact
• Combined recommended action — what to do next

Don't soften findings on either axis. The point of the audit is to catch what the writer missed.

Step 5 — If asked, deliver the revision

If the user wanted polish/edit (not just critique), produce the full revised version. The rewrite must address violations on both axes:

• Replace AI texture: kill delve-class verbs, em-dash clusters, sycophancy, grandiose framing
• Add reader scaffolding: define acronyms inline, break up long paragraphs, add a thesis sentence, contextualize named entities, replace telegraphic colon-labels with sentences
• Hit audience-specific readability targets (FK grade in band, lexical density appropriate, sentence length variance present)
• Don't introduce new tells (re-scan after rewrite if uncertain)

The revision should read as deliverable prose for the target audience.

Quick reference: lethal tells (both axes)

If you only have time for a quick scan, look for these. Each appears in the highest-density failures.

AI-Slop (20 most lethal)

Vocabulary: delve / delves, tapestry, underscore / underscores, leverage (verb), harness

**Senten