Find unjustified AI-like filler, visual or wording residue, needless abstraction, and process bloat in a candidate; optionally repair bounded presentation-only defects. Use for reviewing interfaces, prose, code, analytics, plans, or explicit slop review.
Installs into .claude/skills of the current project.
Are you the author of Slop Sweep?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/simonasrazm-slop-sweep)
---
name: slop-sweep
description: Find unjustified AI-like filler, visual or wording residue, needless abstraction, and process bloat in a candidate; optionally repair bounded presentation-only defects. Use for reviewing interfaces, prose, code, analytics, plans, or explicit slop review.
---
# Slop Sweep
Judge residue against the artifact's intent, audience, project conventions, and real cost, not against a blacklist of fashionable words, colors, gradients, cards, or styles. An unconventional trait is not a defect by resemblance alone.
Inspect what was actually produced. Look for generic filler, redundant explanation, obvious generated copy, decorative UI without purpose, duplicated structure, needless abstraction, speculative extensibility, tracker ceremony, and output that cannot justify its maintenance or attention cost. State the demonstrated consequence to clarity, trust, usability, performance, maintenance, or scope.
Repeated long em dashes in generated prose are a common AI-slop signal. Replace them with natural punctuation unless the source or project voice deliberately uses them; judge isolated use in context rather than treating punctuation alone as proof of generation.
Under explicit or delegated fix authority, this skill may repair an unambiguous presentation-only defect whose meaning and behavior remain unchanged: wording cleanup, redundant labels, mechanical token alignment, or an equally local correction. Give the mutation a new candidate identity and obtain a recheck in a fresh context supplied with the accepted contract and candidate, without inherited builder conversation or rationale; this skill does not accept its own repair. The same independence boundary applies when this skill supplies acceptance for another builder.
Route changes to behavior, product meaning, information architecture, design-system rules, code architecture, data, or broad structure to the implementation owner. When invoked as a check only, leave all maintained output unchanged and return evidence plus the smallest repair boundary.
Return findings or the repaired candidate in-channel; create no report or run-state artifact unless requested.
