AI Slop Audit

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

The detector. Given any artefact, it decides how much it reads as AI slop, names exactly why, and says how to fix each finding. Production-side prevention is the companion anti-ai-slop skill.

Use When

• After EACH major iteration of work on the project at hand — a drafted section, finished feature/module, completed deck, significant revision, or milestone. Log the verdict; block progression on grade F.
• The user asks to analyse, review, evaluate, audit, critique, score, or de-slop any website, web/mobile app, business plan, SRS/spec, proposal/EoI, blog/article, social post, marketing copy, document, image/video, or codebase.
• The user asks "is this AI slop / does this look AI-generated / why does this feel off?".
• As the final gate before publishing or delivering any output.

Do Not Use When

• There is no concrete artefact to inspect yet — generate it first under anti-ai-slop, then audit.

Required Inputs