ai-slop-audit
AI Slop Audit
Overview
This is the detector. Given any artefact, it decides how strongly it reads as AI slop, names exactly why with evidence, scores it, and says how to fix each finding. Production-side prevention is the companion anti-ai-slop skill. It runs as the final gate before any plan, deck, or narrative leaves the suite, and on demand whenever a user asks for a slop review.
Cadence — run after each major iteration
This is the default mode: run this audit after each major iteration of work on the plan — each drafted plan section, each completed deck, each financial-narrative module, each significant revision, each milestone — before moving to the next. Log the verdict each time. If the verdict is F (Blocked), do not progress to the next section or iteration until the blocking findings are fixed. Treat it like a test suite that runs at every checkpoint, not a one-time final review. This is in addition to running on request and as the final pre-submission gate; the companion anti-ai-slop skill runs continuously during drafting, and this audit runs at each checkpoint to catch what slipped through.
Use When
- Use when the user asks to analyse, review, evaluate, audit, critique, score, or de-slop a business plan, plan section, pitch deck, investment case, financial model or narrative, GTM/pricing narrative, proposal/EoI, blog post, document, or codebase.
- Use when the user asks "is this AI slop / does this look AI-generated / why does this feel off?".
- Use as the final gate before publishing or submitting any suite output.