Natural-language processing. Local first.

Your AI
has a
tell.

SlopSift uses a small dependency parser we trained to map the relationships between words and find canned arguments, unsupported claims, and filler.

Open the editor
draft.txt editablelive NLP
Starting the local parser…

Loading the on-device NLP model…

Ln 1, Col 1stays local
corrective-antithesisunsupported-certaintyperformed-revelationvague-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. Those links let each rule inspect a sentence's claim and vocabulary.

  1. 01

    Build a dependency graph

    Our custom-trained compact model maps tokens, parts of speech, and the grammatical relationships holding the sentence together.

  2. 02

    Match the construction

    Authorable rules inspect the graph for structural tells. Every finding names what matched and the exact text that triggered it.

  3. 03

    Keep judgment with the writer

    Errors are strong tells. Warnings need attention. Notes are candidates for the writer to review.

Not an API wrapper

We trained the parser for this.

SlopSift starts with a compact pretrained English encoder and trains it for parts of speech and dependency parsing. Training combines structured distillation from a larger parser with 50 controlled examples targeting grammatical relationships used by the linter. We reserved separate template families for evaluation.

16 MiB

Small enough to ship

Quantized ONNX weights run locally in Node and browser WebAssembly.

3 heads

Built for syntax

The model predicts parts of speech and the grammatical links between words.

0 uploads

Your draft stays yours

The model and deterministic rules run on-device. No remote judge reads the text.

Read how the model and CLI work

Not every em dash is slop.

error

“As an AI language model...”

caught red-handed
warning

Three paragraphs use the same canned outline.

probably slop
note

An actorless passive may be hiding responsibility.

worth a look

Meet writers where they write.

$

CLI

Glob files, lint Markdown, inspect code comments, and emit ESLint-shaped JSON in CI.

CLI docs →
VS

VS Code

See SlopSift findings in the Problems panel while you edit Markdown, plain text, and source comments.

Install extension →
AI

Agent skill

Let coding agents run the real linter, interpret its findings, and edit without flattening your voice.

Add the skill →

Paste this into your coding agent.

The linked file explains how to install the plugin, preserve your settings, restart the agent, and prove the correction loop works.

Claude Code or Codexuser-level Stop hook

Set up SlopSift as a user-level Stop hook for Claude Code and/or Codex. Follow https://slopsift.dev/llms.txt, preserve my existing settings, and test the hook after installation.

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.

terminal~/your-writing

Use --format json for machines, --level info for the full suspicious pile.

VSWrite with SlopSift in VS CodeLocal diagnostics in the Problems panelInstall ↗