deslop
Skill4 starsChanged 13 days agoMITView on GitHub
Remove AI writing patterns from prose so it reads like a person wrote it. Use when writing, editing, or reviewing user-facing text (blog posts, docs, marketing copy, PR descriptions), or when asked to "deslop", "de-AI", or "make it sound human".
128 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- leonardourci/pnyxtheir own version, first seen Nov 16, 2026
- PaulRBerg/dot-agentstheir own version, first seen Nov 15, 2026
- gustavo-henriq/antislop-ui-ux-skilltheir own version, first seen Nov 15, 2026
- PaulRBerg/agent-skillstheir own version, first seen Nov 15, 2026
- hanyang-tech/claude-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use control-cli, verify-this and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ElyzeSolutionsSkillcontrol-cli
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
Also in 6 projects that use this
learnerLjSkillverify-this
Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
Also in 6 projects that use this
ElyzeSolutionsSkillcontrol-ui
Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.
Also in 7 projects that use this
jaydubya818Skillpoteto-mode
Use when non-trivial work should follow the smallest rigorous Jstack workflow.
Also in 6 projects that use this
Other versions128 projects use a version of this.
Word for word · 1
- every-app/open-seo★ 28k100% same
Edited · 0
None found.
Wrote their own version · 127
- molt-bot/clawdbot★ 391ksame name
- novuhq/novu★ 40ksame name
- millionco/react-doctor★ 15ksame name
- jaredpalmer/kev★ 9.8ksame name
- joe-bell/cva★ 6.9ksame name
- sanity-io/sanity★ 6.4ksame name
- millionco/expect★ 3.6ksame name
- rohitg00/pro-workflow★ 2.9ksame name
- compozy/compozy★ 2.9ksame name
- Jwuthri/Tracely-ai★ 1.3ksame name
117 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- ai-prompt-researchSkill
- ai-visibility-auditSkill
- competitive-landscapeSkill
- competitor-analysisSkill
- create-repo-skillSkill
- evaluate-skillSkill
- keyword-clusteringSkill
- keyword-researchSkill
- link-prospectingSkill
- local-seoSkill
- merge-readySkill
- observability-triageSkill
- openseo-release-notesSkill
- openseo-review-web-contentSkill
- papercutsSkill
- review-briefSkill
- review-simplifySkill
- review-ui-statesSkill
- seo-auditSkill
- seo-coachSkill
- seo-project-setupSkill
- seo-reportSkill
- setup-openseoSkill
- simple-issue-descriptionSkill
- stageshowSkill
- test-auditSkill
- verify-local-mcpSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 125 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Before: "Here's the thing: most pipelines break in production.
- Distinctive: line 31
After: "Most pipelines break in production.
“Common” is measured: kept by at least 6 in 10 of the 125 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deslop
Make prose sound like a specific person wrote it. Fix each tell by stating the underlying claim plainly, not by swapping in a new flourish.
Cut or rewrite
- Filler: throat-clearing ("Here's the thing:"), emphasis crutches ("Let that sink in."), meta-commentary ("In this section, we'll explore..."), "It's worth noting," and business jargon ("navigate the landscape," "leverage").
- Staged contrasts like "Not X. Y." or "It's not X, it's Y." State Y.
- Manufactured rhythm: dramatic fragments ("Speed. That's it."), rhetorical questions answered right away ("The result? Devastating."), three-part phrasing that exists only for cadence ("fast, simple, and powerful"), and paragraphs that end on a one-liner restating the paragraph.
- AI vocabulary: "delve," "tapestry," "quietly," "serves as," "highlighting its importance," invented concept labels ("the supervision paradox"), and inflated stakes.
- Vagueness: declaratives that name nothing ("The reasons are structural"), "experts argue" with no name, and "every," "always" or "never" doing vague work.
- False agency, where a thing does a person's verb ("the complaint becomes a fix"). Name who did it.
- Signposting: announcing what you're about to say, then summarizing what you said. "In conclusion." "Despite these challenges."
- Formatting tells: em dashes, unicode arrows, and lists where every item opens with a bolded keyword.
Keep
Specifics (names, numbers, examples), "you" for the reader in blog posts, varied sentence length, and short plain lines that carry information. Keep bullet points and numbered steps for actions and instructions; don't fold them back into paragraphs. When editing someone else's writing, keep their voice.
Example
Before: "Here's the thing: most pipelines break in production. Not because the code is bad. Because the data is bad. Let that sink in."
After: "Most pipelines break in production. The code runs fine. The data doesn't match the assumptions baked into it."
Adapted from stephenturner/skill-deslop (MIT, see LICENSE).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

