remove-ai-slop
Skill1 starsChanged 39 days agoMITView on GitHub
Edit prose to remove AI-style filler, repetitive rhetoric, and generic polish while preserving meaning and the author's voice. Use for requests to remove AI slop, make writing less robotic, or clean up generated drafts.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- alfonsograziano/skillstheir own version, first seen Nov 1, 2026
- sdettweiler/claude_skillstheir own version, first seen Oct 25, 2026
- SalZaki/antisloptheir own version, first seen Oct 20, 2026
- christiangalsterer/documentation-plugintheir own version, first seen Oct 6, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- alfonsograziano/skills★ 13same name
- christiangalsterer/documentation-plugin★ 1same name
- SalZaki/antislop★ 0same name
- sdettweiler/claude_skills★ 0same name
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 repository6 other files it gives its agents.
- skills/logictune/AGENTS.mdAGENTS.md
- ai-fictionSkill
- bugdoctorSkill
- logictuneSkill
- quickticketSkill
- test-rightSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
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 22
Remove unearned praise, excessive reassurance, automatic agreement, generic excitement, unsolicited defensive framing, and apologies for …
- Distinctive: line 26
Do not replace polish with fake slang, deliberate mistakes, invented personal anecdotes, or a new persona.
- Distinctive: line 42
Read the result as a peer, as an editor looking for filler, and aloud for natural rhythm.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Remove AI slop
Rewrite for clarity and concision. Remove canned phrasing and make the prose read naturally. Change words freely, combine or split sentences, reorder material, and cut repetition or empty claims. Keep the author's point and recognizable voice. Follow the user's audience, genre, length, and style preferences.
Remove the habits that get in the way
Lead with the point the reader needs. Cut ceremonial openings, commentary about the writing process, repeated summaries, prompt echoes, and closing sentences that merely announce importance. Preserve greetings, context, and conclusions that serve the relationship or the argument.
Prefer concrete nouns and direct verbs to inflated abstractions and stacks of adjectives. Use the shortest familiar expression that preserves the distinction. Use active voice when it clarifies responsibility; retain passive voice when the actor is unknown, irrelevant, or deliberately withheld. Shorten tangled sentences, but keep natural variation rather than turning every sentence into a fragment.
Mix brief statements with sentences that explain a reason, develop an example, or add a qualification. Vary sentence openings and clause shapes when a paragraph sounds repetitive. Let emphasis justify deliberate repetition, including slogans. Read aloud for flow and revise awkward runs of similar sentences.
Check for repeated “not X, but Y” reversals, rhetorical questions answered immediately, decorative groups of three, grand lessons, forced metaphors, invented compound labels, and balanced slogans. State the supported point directly when the flourish adds nothing. Keep genuine contrasts, necessary lists, and intentional literary devices. In marketing copy, preserve slogans and deliberate repetition when they serve the message. Edit the surrounding filler first; familiar rhythm or a three-part structure alone does not justify deleting a tagline.
Review stock words such as “delve,” “unlock,” “landscape,” and “tapestry” in context. Replace vague promotional uses; retain literal meanings and useful technical language. A word, punctuation mark, or sentence shape alone is not a defect or evidence of AI authorship.
Remove unearned praise, excessive reassurance, automatic agreement, generic excitement, unsolicited defensive framing, and apologies for things that do not warrant them. Keep warmth, tact, humor, and a real apology where they serve the user's purpose. Preserve dialect and cultural voice.
Use headings, bold text, and lists when they help the reader scan or act. Avoid turning ordinary correspondence into a miniature report. Reduce distracting punctuation and repeated em-dash asides when they interrupt the reading; retain punctuation the author's voice or meaning needs. Do not force equal paragraph lengths or manufacture variation just to look human.
Do not replace polish with fake slang, deliberate mistakes, invented personal anecdotes, or a new persona. Keep distinctive phrasing that works. Leave already good text alone.
For ordinary business prose, default to the plain-punctuation style: straight quotes, no emoji, and periods, commas, colons, or parentheses in place of em-dash, en-dash, or double-hyphen asides. Preserve punctuation inside protected quotations, code, citations, and identifiers. Keep compound-word hyphens, URLs, and accurate ranges. The user's explicit house style or literary voice takes priority.
Inspect sentence-final participial tails that announce commitment, importance, or transparency without adding a fact. Cut the tail; keep an informative clause, as its own sentence if clearer. Replace symbolic interpretation with the actual thing or action when possible. Preserve precise uses of terms such as “represents” in mathematics or “indicates” in qualified evidence.
Remove artificial balance when it obscures the author's supported position. Give relevant contrary evidence its actual weight. Check repeated bold-header-and-colon bullets and listicle scaffolding, but keep consistent formatting when it makes a comparison or procedure easier to follow. Do not add a fourth item, nested bullet, or arbitrary fragment merely to break a pattern.
Use the relevant evidence
Review phrases and paragraph moves with phrasing.md. Use word-and-phrase-review.md for the expanded expression checks. For persistent issues, use patterns.md. Source versions and limits are in research.md.
These checks apply to prose from any generating model. Do not guess authorship from style. Research checked 2026-10-04.
Check and deliver
Read the result as a peer, as an editor looking for filler, and aloud for natural rhythm. Fix awkward or canned phrasing. Allow fresh wording and structure. Leave already good prose alone.
Return the edited text. Explain changes when asked; add a note only if an unresolved ambiguity blocks the edit. Do not append a change log, a quality score, or a claim about passing an AI detector.
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.

