Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dmmulroy/install-anti-slop
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.
Passed 13 of 18 test cases with the skill, and 9 of 18 without it.
and 7 more in the full report
8 fixed9 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Checking our lockfile shows that 'effect' is pulled in transitively by a sub-dependency, but 'effect' is not listed in our package.json dependencies or devDependencies. Should we enable the anti-slop-effect plugin in our Oxlint config?
| Checked | Without skill | With skill |
|---|---|---|
| Omits the anti-slop-effect plugin because effect is not directly declared in the package manifest. | Missed | Passed |
The instructions your model reads when the skill loads.
Anti-slop is vendored code: the target repository owns its rules, diagnostics, tests, and configuration. Preserve those choices when bringing in upstream changes.
Read the repository's agent instructions and git status. Identify its package manager, Oxlint/Vite+ configuration, and any existing anti-slop entry points, including renamed or relocated copies referenced by jsPlugins.
Complete when the operation and target path are established and pre-existing work is identified.
Copy the bundled plugin from this skill. Run from the target repository:
node <skill-directory>/scripts/install.mjs
This 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; route existing copies through the update procedure rather than --force.
Preserve the nested vendor/eslint-stylistic/LICENSE and UPSTREAM.md; they travel with the copied rule. Readability enforcement is self-contained and requires no Stylistic plugin dependency.
Complete when the files, including vendored license and provenance, exist at the agreed destination without replacing an existing copy.
Install current compatible dependencies rather than trusting versions remembered by the agent:
oxlint, read its installed version from the package manager or lockfile and install @oxlint/plugins at exactly that version. Pin it exactly rather than by range so future upgrades move both packages together.oxlint dependency, query npm view oxlint version and npm view @oxlint/plugins version, then install the same current version of both packages.oxlint is a development dependency. The copied source imports @oxlint/plugins, so install it as a development dependency for a local-only plugin.Complete when matching compatible versions are installed and unrelated dependency ranges are preserved.
Register the generic plugin, configure ignores, and enable all generic rules. For oxlint.config.ts or .oxlintrc.json, merge these fields with the existing configuration:
ignorePatterns: [
".agent/**",
test cases passed, vs 9 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.