Small enough to ship
Quantized ONNX weights run locally in Node and browser WebAssembly.
Natural-language processing. Local first.
Your AI
has a
tell.
SlopSift uses our custom-trained dependency parser to map the grammatical structure beneath a draft—not just words or parts of speech—and catch canned arguments, borrowed certainty, and suspiciously polished filler.
Starting the local parser…
Loading the on-device NLP model…
corrective-antithesisunsupported-certaintymechanical-outlinevague-attributionai-vocabulary
More than a word list
It reads structure,
not vibes.
Many writing tools stop at word matching and basic parts of speech. SlopSift follows the relationships between words, so rules can recognize how a sentence makes its claim—not only which vocabulary it uses.
- 01
Build a dependency graph
Our custom-trained compact model maps tokens, parts of speech, and the grammatical relationships holding the sentence together.
- 02
Match the construction
Authorable rules inspect the graph for structural tells. Every finding names what matched and the exact text that triggered it.
- 03
Keep judgment with the writer
Errors are strong tells. Warnings need attention. Notes are candidates—not a machine pretending to know who wrote the sentence.
Not an API wrapper
We trained the parser for this.
SlopSift starts with a compact pretrained English encoder, then fine-tunes it for parts of speech and dependency parsing. Our rule-aware distillation adds the constructions the linter actually needs to understand, with lexical families held out so the model has to learn structure instead of memorizing phrases.
Built for syntax
UPOS, dependency arcs, and dependency relations—not a generic text score.
Your draft stays yours
The model and deterministic rules run on-device. No remote judge reads the text.
Not every em dash is slop.
“As an AI language model...”
caught red-handedThree paragraphs use the same canned outline.
probably slopAn actorless passive may be hiding responsibility.
worth a lookMeet writers where they write.
$
CLI
Glob files, lint Markdown, inspect code comments, and emit ESLint-shaped JSON in CI.
VS
VS Code
Diagnostics beside the sentence, with the same severity and rule name as the terminal.
CR
Chrome
Review text boxes and editable pages before the draft escapes into the internet.
AI
Agent skill
Let coding agents run the real linter, interpret its findings, and edit without flattening your voice.
Yes, AI helped build this.
Built by AI.
Edited on purpose.
That is the point. SlopSift is not an AI detector and it does not pretend to know who typed a sentence. It catches vague or inflated writing. It also catches repetition and borrowed certainty. Human beings do those things too.
One command.
Several opinions.
Use --format json for machines, --level info for the full suspicious pile.