Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
Anti-slop provides a set of opinionated linting rules designed to reject low-evidence patterns in TS/JS projects. It allows developers and platform teams to standardize code quality by vendoring rules, diagnostics, and tests directly into their own repositories.
The system is built to support local customizations, ensuring that upstream updates and fixes can be integrated without overwriting project-specific configuration choices.
WHO IT'S FOR
TypeScript / JavaScript developers
enforce high-evidence coding patterns via Oxlint
Platform / DevEx teams
standardize linting rules across multiple repositories
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
A target repository opened as the current working directory
Use the install-anti-slop skill to install and configure anti-slop in the current repository. First inspect the repository's agent instructions, git status, package manager, Oxlint configuration, and any existing anti-slop entry points. If no installation exists, perform the documented fresh-install procedure without overwriting existing work.
A target repository containing an existing anti-slop installation
Optional upstream revision or selected fixes
Use the install-anti-slop skill to update the existing vendored anti-slop installation while preserving local customizations. Inspect the existing entry point and configuration first, and use the skill's update procedure rather than the fresh-install path. If desired, use the supplied upstream revision or selected fixes as the update target.
Claude
Codex
Cursor
Gemini CLI
Windsurf
OpenCode