unslop-text
Paste a draft in and find out what gives it away as machine-written. Two passes, because the two kinds of tell need completely different machinery to catch.
The idea
There are two kinds of tell and only one is mechanical
Some giveaways are fixed strings. Particular punctuation, a small set of overused words, a handful of stock constructions. A regular expression catches those perfectly, instantly, and without sending your draft anywhere.
The rest are structural. Rhythm that never varies. Sycophancy. Saying very little at considerable length. Those are cited by readers just as often, sometimes more, and no pattern can detect them because the problem is not which words appear but how the whole thing moves.
So the tool is honest about the split. A clean mechanical scan means the lexical layer is clean. It does not mean the writing reads as human, and the interface says so rather than letting a green score imply otherwise.
Architecture
Local first, model second
Detail
At a glance
| Pass A | Regex scanner, runs entirely in the tab. No network request, nothing stored. |
|---|---|
| Pass B | Optional model-based structural read, proxied through the app's own server. |
| Key handling | API key server-side only. Never exposed to the browser. |
| Output | Ranked findings with severity filters, a slop score, and a suggested fix per item. |
| Companion | Shares its audit with a Claude skill of the same name. |
| Stage | Live. |