deslop
Skill2 starsChanged 56 days agoMITView on GitHub
Audits a diff or file for over-engineering and AI code and prose tells, then applies only the fixes the user confirms. Use before opening a PR, when asked to clean up, simplify, or review a diff, or when code looks generated.
130 other projects use a version of this.
Adopted by
Most recently taken up by
- iyazerski/dev-flows-plugintheir own version, first seen Nov 16, 2026
- Floppa2003/skillstheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- leonardourci/pnyxtheir own version, first seen Nov 16, 2026
- PaulRBerg/dot-agentstheir own version, first seen Nov 15, 2026
- gustavo-henriq/antislop-ui-ux-skilltheir own version, first seen Nov 15, 2026
Used with
Projects with it also use simple-issue-description, control-cli and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JwuthriSkillsimple-issue-description
Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior. Use when a contributor asks to simplify an issue, explain what a PR is for, create the corresponding issue for a PR, remove implementation detail from a report, or invokes /simple-issue-description.
Also in 4 projects that use this
ElyzeSolutionsSkillcontrol-cli
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
Also in 6 projects that use this
JwuthriSkillopenseo-review-web-content
Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.
Also in 4 projects that use this
learnerLjSkillverify-this
Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
Also in 6 projects that use this
ElyzeSolutionsSkillcontrol-ui
Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.
Also in 7 projects that use this
ten9876Skillpapercuts
Read-only AetherSDR issue triage that surfaces the UX papercuts, bugs, and regressions you can fix AND prove today with the agent automation bridge. Use when the user says $papercuts or /papercuts, or asks to "find papercuts", "what can I fix and prove today", "triage bridge-provable issues", "what UX bugs can the bridge close", "sort issues by priority I can knock out", or otherwise wants a curated, lifecycle-aware (design→code→prove) shortlist of issues — NOT the label-and-respond /triage workflow. This is the discovery step that feeds /fb. Strictly read-only: it never labels, comments, closes, or edits issues.
Also in 4 projects that use this
- +5 more from Jwuthri
Other versions130 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 130
- molt-bot/clawdbot★ 391ksame name
- novuhq/novu★ 40ksame name
- every-app/open-seo★ 28ksame name
- millionco/react-doctor★ 15ksame name
- jaredpalmer/kev★ 9.8ksame name
- joe-bell/cva★ 6.9ksame name
- sanity-io/sanity★ 6.4ksame name
- millionco/expect★ 3.6ksame name
- rohitg00/pro-workflow★ 2.9ksame name
- compozy/compozy★ 2.9ksame name
120 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 128 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 52
Read the matching convention rules first, including the testing rule for any test you add.
- Distinctive: line 54
Keep trust-boundary checks and real error handling.
- Distinctive: line 55
Run format, lint, and the relevant tests.
- Very specific: line 58
Leave the fixes in the working tree.
“Common” is measured: kept by at least 6 in 10 of the 128 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deslop
Find what a diff adds that the task did not need, and remove only what the user confirms.
1. Walk the reuse-first ladder
For each new dependency, file, wrapper, or export, stop at the first rung that fits:
- Does it need to exist? Skip guards for inputs that cannot occur and flags nobody asked for.
- Is it already in this codebase? Search before writing a helper or component.
- Does the standard library or language cover it?
- Does the platform or framework cover it?
- Does an installed dependency cover it?
- Does one inline line do it, instead of a new function or component?
- Otherwise, write only what the task needs.
Flag a dependency an earlier rung covers, a wrapper with one caller, an unrequested flag, generality for inputs nobody passes, a type alias that only renames another type, and a compatibility shim nobody asked for. Two real callers justify reuse.
For a new module or layer, run the deletion test: imagine it gone. If the complexity vanishes, it was a pass-through. If it reappears across several callers, it earns its place. One implementation behind an interface is a hypothetical seam, not a real one.
2. Check the code tells
- Comments that restate the code or do not match the local comment density.
- Abnormal defensive checks or
try/catchon trusted paths. Trust-boundary validation stays. anycasts that dodge a type error.- Nesting that early returns would flatten, and any
elseorelse if. - Naming, import, or export style that differs from nearby code.
- Tests that restate the implementation or check what TypeScript already guarantees.
- Changed comments and docs: the
humanizertells. Skip when no prose changed. - Docs that explain internals the reader does not act on, such as which package bundles a dependency. Delete the sentence rather than reword it.
3. Report, then ask
A request to review, assess, or explain a diff is audit-only: report and stop, unless the user
also asked for fixes or already approved them. Otherwise write the findings list in chat (see Output), then, in the same
reply, follow the ask skill with one question per finding, or per group that shares one fix,
named after the finding (Unused enabled flag in Studio?). Every finding gets a question, so
send a follow-up call when there are more than four.
4. Apply only what was confirmed
- Read the matching convention rules first, including the testing rule for any test you add.
- Make surgical edits that preserve behavior, unless the fix is a clear bug.
- Keep trust-boundary checks and real error handling. Never weaken a type, rule, or test.
- Run format, lint, and the relevant tests.
- Re-audit the whole resulting diff against steps 1 and 2 and the convention rules, and fix what your edits introduced.
- Leave the fixes in the working tree. Committing, pushing, or opening a PR, including a stacked
PR on someone else's branch, is a separate decision to put through
ask.
Output
A bulleted list, one bullet per finding: path:line, the rung or tell, the fix, and Apply or
Skip as your recommendation. Never a prose summary. End with one bullet for what you checked
and found fine. After applying, one bullet per change and one per skipped finding.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

