Catch AI and human slop in English Markdown without calling an LLM. Slopless ships 50+ deterministic textlint rules and a CLI that emits structured JSON findings.
npm install -D slopless
npx slopless install-skill codex
npx slopless install-skill claudeThen start a fresh writing-agent session and tell it to use the Slopless skill:
Use the Slopless skill. Check this Markdown, rewrite the prose, and keep iterating until Slopless passes.
Loop:
- Install Slopless.
- Install the agent skill for Codex or Claude Code.
- Tell the writing agent to use the skill.
- Let the agent run Slopless, rewrite, and rerun until the JSON output has no findings.
- Profit.
npx slopless "docs/**/*.md"Slopless is English-only. It requires a file path, glob, or stdin input. A bare npx slopless exits with code 2.
Exit 0 means clean. Exit 1 means findings. Exit 2 means failure.
Output is always JSON:
mkdir -p .slopless/findings
npx slopless "docs/**/*.md" > ".slopless/findings/$(date +%Y-%m-%d-%H%M%S)--review.json"Agents should run help first:
npx slopless --helpAgents should save raw JSON findings under .slopless/findings/ in the current working directory. Slopless does not choose redirected output filenames, slugs, or timestamps.
Install the Codex skill into the current repo:
npx slopless install-skill codexInstall the Claude Code skill into the current repo:
npx slopless install-skill claudeBoth commands install the same slopless skill body. Start a new agent session after installing if the skill is not visible.
Use textlint comments around intentional exceptions:
<!-- textlint-disable slopless/semantic-thinness -->
Something shifted in the room.
<!-- textlint-enable slopless/semantic-thinness -->- Philosophy - what slopless is for, design principles, why deterministic.
- Comparison - slopless vs proselint, write-good, alex, vale, default textlint presets.
- Rules - full 50+ rule inventory across seven families.
- Behavior - CLI flags, exit codes, JSON output shape, direct textlint integration.
- Ignore rules - inline
textlint-disableblock syntax. - Thanks - direct rule sources, dependencies, and acknowledgments.
- Contributing - open a detailed issue first; PRs must pass the G3TS pre-commit gate.
Part of Agent Quality Controls.