slopless CLI
slopless is an English prose-checking CLI with distinct exit codes for a clean result, editorial findings and execution failure.
- 339 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Installation adds a project dependency; selected semantic checks send text to an external service.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/sloplessDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Installation adds a project dependency; selected semantic checks send text to an external service.
This is third-party code. Review the repository files before installing.
What it does
slopless is a CLI that checks English Markdown for stock openings, clichés and rhetorical structures. The CLI accepts files, path globs or standard input and returns JSON findings. Its default checks use local textlint rules. An agent can revise the flagged passages and run the checker again. Optional semantic checks use TypeSafe, while separately enabled narrative rules examine action descriptions and fiction craft.
Who it is for. English documentation authors editing Markdown with an agent and adding prose checks to a project.
Good fit when
- Documentation is checked for stock openings and clichés.
- An agent receives JSON findings and prepares revisions.
- A fiction author enables separate narrative rules.
- An existing textlint setup gains prose checks.
Not a fit when
- Your main text is Russian
- You need proof that a text was written by AI
- You need automatic fact and link correction
Example request
Check this English guide with local slopless rules and suggest a revision for each finding.Limitations
Only English prose is supported; Russian needs a different checker and editorial review. The package requires Node.js 22 or newer in the environment where the agent runs it. Semantic checks require `JEV_API_KEY` and send selected writing to TypeSafe, so private documents need a separate data-sharing decision. Those checks use experimental cutoffs with varying quality, so evaluate each finding against the actual meaning of the passage.
How to disable. Remove the slopless dependency from the project and disable its rules in your lint configuration.
FAQ
Does a bare command check text?
No. Supply a path, glob or standard input. The README example `npx slopless "docs/**/*.md"` checks Markdown under the documentation directory; substitute your own glob.
Is an API key mandatory?
No. Local rules need no key; optional TypeSafe checks do.
How do I install the Codex skill?
After installing the package, run `npx slopless install-skill codex` in the target project.
Are reports saved automatically?
No. The agent must choose a filename and save the returned JSON.
What does exit code 1 mean?
Findings were detected. Exit 0 is clean and exit 2 indicates failure.
Discussion
No questions or reviews yet.
Related
CLI toolsThe CLI checks and formats Markdown so an agent can report violations before applying agreed changes.
Docling is a CLI for mixed document archives, bringing PDFs, office files and spreadsheets into a shared format for AI search.
A skill plus the docx program: the agent fills forms, edits tables and reviews Word files with tracked changes
A CLI and skill for an agent to publish reports and specs as HTML documents that a team comments on, with every version kept
humanizer-ru (chat paste hygiene)
humanizer-ru
A CLI, MCP server and skill that find and safely strip chatbot copy-paste artifacts in Russian text and check facts after editing
An editing skill that strips stock AI phrasing but keeps the author's vocabulary, rhythm and bluntness, not a flat style.
README in short
Alongside the CLI, the package includes a textlint preset and an editing-loop skill. Narrative rules are enabled separately from ordinary documentation checks.