install-anti-slop
Skill6 starsChanged 2 months agoMITView on GitHub
Install and configure the generic and optional Effect anti-slop Oxlint plugins in a local TypeScript or JavaScript repository. Use whenever a user asks to add anti-slop lint rules, copy the anti-slop plugin, configure opinionated Oxlint rules, or migrate an existing local anti-slop setup.
8 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- bbplayer-app/BBPlayeredited, first seen Nov 16, 2026
- imMamdouhaboammar/anti-slop-engineeringedited, first seen Nov 16, 2026
- Amronos/skillsedited, first seen Nov 15, 2026
- mohammadchehab/isnadibotedited, first seen Nov 15, 2026
- dmmulroy/anti-slopedited, first seen Oct 25, 2026
- trycompai/crmedited, first seen Oct 8, 2026
Other versions8 projects use a version of this.
Word for word · 1
- Verbiflow/mako★ 5100% same
Edited · 6
- trycompai/crm★ 12k88% same
- dmmulroy/anti-slop★ 5.7k42% same
- bbplayer-app/BBPlayer★ 1.4k42% same
- imMamdouhaboammar/anti-slop-engineering★ 439% same
- mohammadchehab/isnadibot★ 238% same
- Amronos/skills★ 142% same
Wrote their own version · 1
- kuker24/OpenCodeBestFriend★ 0same name
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.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- commitSkill
- gh-stackSkill
- grade-itSkill
- hygieneSkill
- principle-prove-it-worksSkill
- review-commentSkill
- react-doctorSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
5 rules. 1 is common, 3 are distinctive, and 1 is very specific to this project.
1
Common
Most of the 7 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 13
Read its agent instructions.
- Distinctive: line 14
Check git status and preserve unrelated changes.
- Distinctive: line 17
Check whether anti-slop files or rules already exist.
- Common: line 31
Do not replace the package manager or rewrite unrelated dependency ranges.
- Very specific: line 81
If the repository declares effect in a package manifest, or the user explicitly requests Effect rules, also register the opt-in Effect …
“Common” is measured: kept by at least 6 in 10 of the 7 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
Install anti-slop
Install the bundled Oxlint plugin into the current repository and integrate it with the repository's existing lint setup. Preserve unrelated work and adapt to the project's package manager and configuration style.
Procedure
- Inspect the repository before changing it:
- Read its agent instructions.
- Check
git statusand preserve unrelated changes. - Identify the package manager from
packageManagerand lockfiles. - Find Oxlint configuration (
oxlint.config.*,.oxlintrc*, or a Vite+ config). - Check whether anti-slop files or rules already exist. Do not overwrite them without reviewing the diff.
Copy the bundled plugin from this skill. Run from the target repository:
node <skill-directory>/scripts/install.mjsThis creates
tools/oxlint/anti-slop/. Pass another relative destination as the first argument when the repository has an established tooling layout. The script refuses to replace an existing destination; only use--forceafter backing up and reviewing existing files.- Install current compatible dependencies rather than trusting versions remembered by the agent:
- Query
npm view oxlint versionandnpm view @oxlint/plugins version. - Install the same current version of both packages with the repository's package manager.
oxlintis a development dependency. The copied source imports@oxlint/plugins, so install it as a development dependency for a local-only plugin.- Do not replace the package manager or rewrite unrelated dependency ranges.
- Query
Register the generic plugin, configure ignores, and enable all generic rules. For
oxlint.config.tsor.oxlintrc.json, merge these fields with the existing configuration:ignorePatterns: [ ".agent/**", ".agents/**", ".claude/**", ".codex/**", ".continue/**", ".cursor/**", ".gemini/**", ".opencode/**", ".pi/**", ".roo/**", ".windsurf/**", "tools/oxlint/anti-slop/**", ], jsPlugins: [ { name: "anti-slop", specifier: "./tools/oxlint/anti-slop/index.ts" }, ],Keep every existing ignore. Adjust the final pattern when the plugin was copied elsewhere. Inspect the repository for other project-local agent tooling directories and add them rather than linting installed skills, hooks, or generated agent configuration as application source. Do not broadly ignore all dot-directories, because some repositories keep owned source or checks in them.
For Vite+, add these fields to
lint.ignorePatternsandlint.jsPlugins. Also merge the same patterns intofmt.ignorePatternssovp checkdoes not reformat installed agent assets or the vendored plugin. Merge existing entries instead of replacing them.Enable these rules at
"error":{ "anti-slop/no-chained-type-assertions": "error", "anti-slop/no-conditional-empty-object-spread": "error", "anti-slop/no-known-value-widening": "error", "anti-slop/no-module-mocking": "error", "anti-slop/no-object-parameters": "error", "anti-slop/no-reflect-apply": "error", "anti-slop/no-reflect-get": "error", "anti-slop/no-runtime-typeof": "error", "anti-slop/no-shape-in-symbol-names": "error", "anti-slop/no-unknown-parameters": "error", "anti-slop/no-unknown-returns": "error", "anti-slop/no-unknown-type-aliases": "error", "anti-slop/no-unsafe-dictionary-type": "error", "anti-slop/no-widen-then-assert": "error", "anti-slop/require-safety-comment-for-type-assertion": "error" }If the repository declares
effectin a package manifest, or the user explicitly requests Effect rules, also register the opt-in Effect plugin:jsPlugins: [ { name: "anti-slop-effect", specifier: "./tools/oxlint/anti-slop/effect/index.ts", }, ], rules: { "anti-slop-effect/no-service-constructor-imports": "error", },Merge these entries with the generic plugin configuration rather than replacing it. Do not enable the Effect plugin merely because Effect appears transitively in a lockfile; require a direct package-manifest dependency or an explicit user request. The rule covers relative project imports. Report package-alias imports as a current limitation rather than pretending they are enforced.
- Run the repository's lint command and typecheck. For Vite+, run the repository's full
vp checkcommand after adding both lint and format ignores. If findings appear in owned project source, report them and fix them only when the user asked for migration/cleanup. Do not suppress rules, weaken rule severity, add unsafe casts, or mechanically launder types to make lint pass. - Review the final diff and clearly report:
- copied path,
- dependency versions installed,
- configuration changed,
- checks run and any remaining findings.
Migration guidance
When replacing an older local copy, compare its rules and diagnostics before overwriting. Keep project-specific rules in their own plugin. The default anti-slop plugin is intentionally generic; framework-specific policy belongs in an explicit opt-in group such as anti-slop-effect. Prefer inference, as const, satisfies, named owner contracts, and boundary parsing when resolving findings.
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.

