stop-slop
Skill4 starsChanged 22 days agoMITView on GitHub
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.
43 other projects use a version of this, 37 of them edited.
Adopted by
Most recently taken up by
- danieleteti/delphimvcframeworkedited, first seen Nov 2, 2026
- b-mendoza/agent-skillsedited, first seen Nov 1, 2026
- rsdlt/rsdlt.github.ioedited, first seen Oct 25, 2026
- daviszhen/agent-skillsedited, first seen Oct 25, 2026
- AbdelrhmanAlquran/claude-skillsedited, first seen Oct 20, 2026
- davidanthonyn/claude-skillsedited, first seen Oct 20, 2026
Used with
Projects with it also use banner-design, emails and 3 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.
seikaikyoSkillbanner-design
Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage.
Also in 4 projects that use this
roerohanSkillemails
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
Also in 3 projects that use this
MicrosoftSkillui-styling
Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.
Also in 4 projects that use this
yologdevSkillsocial
Interact with the community through GitHub Discussions — reply, share, learn
Also in 3 projects that use this
seikaikyoSkillbrand
Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.
Also in 4 projects that use this
Other versions43 projects use a version of this.
Word for word · 2
- boraoztunc/skills★ 454100% same
- florattu/claude-skills★ 0100% same
Edited · 37
- hardikpandya/stop-slop★ 18k85% same
- danieleteti/delphimvcframework★ 1.4k85% same
- jvm-skills/jvm-skills★ 14020% same
- jonathanmalkin/jules★ 6514% same
- applypack/applypack★ 3085% same
- chappyasel/meta-kb★ 2585% same
- BuilderIO/builder-agent-skills★ 1686% same
- JustMichael-80/MasterVault★ 1285% same
- tomerose/stop-slop★ 1259% same
- tylerbutler/repoverlay★ 1085% same
27 more not listed
Wrote their own version · 4
- tdimino/claude-code-minoan★ 41same name
- wpgaurav/WordPress-skills★ 19same name
- romangalaxys10-spec/fable★ 4same name
- wpgaurav/claude-code-skills★ 3same 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 repository92 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- analytics-trackingSkill
- app-store-screenshotsSkill
- business-profile-creatorSkill
- call-debriefSkill
- copy-editingSkill
- copywritingSkill
- daily-logSkill
- decision-gauntletSkill
- deep-researchSkill
- hard-taskSkill
- harvestSkill
- invoice-creatorSkill
- landing-pageSkill
- make-interfaces-feel-betterSkill
- ogilvySkill
- onboardSkill
- operational-enterprise-aiSkill
- page-croSkill
- pricing-pageSkill
- product-proof-saasSkill
- proposal-creatorSkill
- prospect-briefSkill
- research-doctrineSkill
- run-coding-sessionSkill
- schema-markupSkill
- seo-auditSkill
- stop-slopSkill
- tailwind-v4Skill
- visual-style-presetsSkill
- web-design-guidelinesSkill
- analytics-trackingSkill
- app-store-screenshotsSkill
- business-profile-creatorSkill
- call-debriefSkill
- copy-editingSkill
- copywritingSkill
- daily-logSkill
- decision-gauntletSkill
- deep-researchSkill
- hard-taskSkill
- harvestSkill
- invoice-creatorSkill
- landing-pageSkill
- make-interfaces-feel-betterSkill
- ogilvySkill
- onboardSkill
- operational-enterprise-aiSkill
- page-croSkill
- pricing-pageSkill
- product-proof-saasSkill
- proposal-creatorSkill
- prospect-briefSkill
- research-doctrineSkill
- run-coding-sessionSkill
- schema-markupSkill
- seo-auditSkill
- stop-slopSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. 6 are common, 4 are distinctive, and 1 is very specific to this project.
6
Common
Most of the 41 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 18
Cut filler phrases: Remove throat-clearing openers, emphasis crutches, and all adverbs.
- Common: line 20
Break formulaic structures: Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency.
- Common: line 22
Use active voice: Every sentence needs a human subject doing something.
- Common: line 24
Be specific: No vague declaratives ("The reasons are structural").
- Common: line 26
Put the reader in the room: No narrator-from-a-distance voice.
- Common: line 32
Cut quotables: If it sounds like a pull-quote, rewrite it.
- Distinctive: line 71
Remove these announcement phrases.
- Distinctive: line 153
Remove self-referential asides.
- Very specific: line 194
If a sentence says something is important/deep/structural without showing the specific thing, cut it or replace it with the specific thing.
- Distinctive: line 290
Instead: Put the reader in the room.
- Distinctive: line 294
Every sentence needs a subject doing something.
“Common” is measured: kept by at least 6 in 10 of the 41 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
Stop Slop
Eliminate predictable AI writing patterns from prose.
Core Rules
- Cut filler phrases. Remove throat-clearing openers, emphasis crutches, and all adverbs. See Phrases to Remove below.
- Break formulaic structures. Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See Structures to Avoid below.
- Use active voice. Every sentence needs a human subject doing something. No passive constructions. No inanimate objects performing human actions ("the complaint becomes a fix").
- Be specific. No vague declaratives ("The reasons are structural"). Name the specific thing. No lazy extremes ("every," "always," "never") doing vague work.
- Put the reader in the room. No narrator-from-a-distance voice. "You" beats "People." Specifics beat abstractions.
- Vary rhythm. Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes.
- Trust readers. State facts directly. Skip softening, justification, hand-holding.
- Cut quotables. If it sounds like a pull-quote, rewrite it.
Quick Checks
Before delivering prose:
- Any adverbs? Kill them.
- Any passive voice? Find the actor, make them the subject.
- Inanimate thing doing a human verb ("the decision emerges")? Name the person.
- Sentence starts with a Wh- word? Restructure it.
- Any "here's what/this/that" throat-clearing? Cut to the point.
- Any "not X, it's Y" contrasts? State Y directly.
- Three consecutive sentences match length? Break one.
- Paragraph ends with punchy one-liner? Vary it.
- Em-dash anywhere? Remove it.
- Vague declarative ("The implications are significant")? Name the specific implication.
- Narrator-from-a-distance ("Nobody designed this")? Put the reader in the scene.
- Meta-joiners ("The rest of this essay...")? Delete. Let the essay move.
Scoring
Rate 1-10 on each dimension:
| Dimension | Question |
| Directness | Statements or announcements? |
| Rhythm | Varied or metronomic? |
| Trust | Respects reader intelligence? |
| Authenticity | Sounds human? |
| Density | Anything cuttable? |
Below 35/50: revise.
Phrases to Remove
Throat-Clearing Openers
Remove these announcement phrases. State the content directly.
- "Here's the thing:"
- "Here's what [X]"
- "Here's this [X]"
- "Here's that [X]"
- "Here's why [X]"
- "The uncomfortable truth is"
- "It turns out"
- "The real [X] is"
- "Let me be clear"
- "The truth is,"
- "I'll say it again:"
- "I'm going to be honest"
- "Can we talk about"
- "Here's what I find interesting"
- "Here's the problem though"
Any "here's what/this/that" construction is throat-clearing before the point. Cut it and state the point.
Emphasis Crutches
These add no meaning. Delete them.
- "Full stop." / "Period."
- "Let that sink in."
- "This matters because"
- "Make no mistake"
- "Here's why that matters"
Business Jargon
Replace with plain language.
| Avoid | Use instead |
| Navigate (challenges) | Handle, address |
| Unpack (analysis) | Explain, examine |
| Lean into | Accept, embrace |
| Landscape (context) | Situation, field |
| Game-changer | Significant, important |
| Double down | Commit, increase |
| Deep dive | Analysis, examination |
| Take a step back | Reconsider |
| Moving forward | Next, from now |
| Circle back | Return to, revisit |
| On the same page | Aligned, agreed |
Adverbs
Kill all adverbs. No -ly words. No softeners, no intensifiers, no hedges.
Specific offenders:
- "really"
- "just"
- "literally"
- "genuinely"
- "honestly"
- "simply"
- "actually"
- "deeply"
- "truly"
- "fundamentally"
- "inherently"
- "inevitably"
- "interestingly"
- "importantly"
- "crucially"
Also cut these filler phrases:
- "At its core"
- "In today's [X]"
- "It's worth noting"
- "At the end of the day"
- "When it comes to"
- "In a world where"
- "The reality is"
Meta-Commentary
Remove self-referential asides. The essay should move, not announce its own structure.
- "Hint:"
- "Plot twist:" / "Spoiler:"
- "You already know this, but"
- "But that's another post"
- "X is a feature, not a bug"
- "Dressed up as"
- "The rest of this essay explains..."
- "Let me walk you through..."
- "In this section, we'll..."
- "As we'll see..."
- "I want to explore..."
Performative Emphasis
False intimacy or manufactured sincerity:
- "creeps in"
- "I promise"
- "They exist, I promise"
Telling Instead of Showing
Announcing difficulty or significance rather than demonstrating it:
- "This is genuinely hard"
- "This is what leadership actually looks like"
- "This is what X actually looks like"
- "actually matters"
Vague Declaratives
Sentences that announce importance without naming the specific thing. Kill these.
- "The reasons are structural"
- "The implications are significant"
- "This is the deepest problem"
- "The stakes are high"
- "The consequences are real"
If a sentence says something is important/deep/structural without showing the specific thing, cut it or replace it with the specific thing.
Structures to Avoid
Binary Contrasts
These create false drama. State the point directly.
| Pattern | Problem |
| "Not because X. Because Y." / "Not because X, but because Y." | Telegraphed reversal |
| "[X] isn't the problem. [Y] is." | Formulaic reframe |
| "The answer isn't X. It's Y." | Predictable pivot |
| "It feels like X. It's actually Y." | Setup/reveal cliche |
| "The question isn't X. It's Y." | Rhetorical misdirection |
| "Not X. But Y." / "not X, it's Y" / "isn't X, it's Y" | Mechanical contrast |
| "It's not this. It's that." | Same formula, different words |
| "stops being X and starts being Y" | False transformation arc |
| "doesn't mean X, but actually Y" | Negation-then-assertion crutch |
| "is about X but not Y" | False distinction |
| "not just X but also Y" | Additive hedge |
Instead: State Y directly. "The problem is Y." "Y matters here." Drop the negation entirely.
Negative Listing
Listing what something is not before revealing what it is. A rhetorical striptease.
| Pattern | Problem |
| "Not a X... Not a Y... A Z." | Dramatic buildup through negation |
| "It wasn't X. It wasn't Y. It was Z." | Same structure, past tense |
Instead: State Z. The reader doesn't need the runway.
Dramatic Fragmentation
Sentence fragments for emphasis read as manufactured profundity.
| Pattern | Problem |
| "[Noun]. That's it. That's the [thing]." | Performative simplicity |
| "X. And Y. And Z." | Staccato drama |
| "This unlocks something. [Word]." | Artificial revelation |
Instead: Complete sentences. Trust content over presentation.
Rhetorical Setups
These announce insight rather than deliver it.
| Pattern | Problem |
| "What if [reframe]?" | Socratic posturing |
| "Here's what I mean:" | Redundant preview |
| "Think about it:" | Condescending prompt |
| "And that's okay." | Unnecessary permission |
Instead: Make the point. Let readers draw conclusions.
Formulaic Constructions
| Pattern | Problem |
| "By the time X, I was Y." | Narrative template |
| "X that isn't Y" | Indirect. Say "X is broken" |
False Agency
Giving inanimate things human verbs. Complaints don't "become" fixes. Bets don't "live or die." Decisions don't "emerge." A person does something to make those things happen. AI loves this because it avoids naming the actor.
| Pattern | Problem |
| "a complaint becomes a fix" | The complaint did nothing. Someone fixed it. |
| "a bet lives or dies in days" | Bets don't have lifespans. Someone kills the project or ships it. |
| "the decision emerges" | Decisions don't emerge. Someone decides. |
| "the culture shifts" | Cultures don't shift on their own. People change behavior. |
| "the conversation moves toward" | Conversations don't move. Someone steers. |
| "the data tells us" | Data sits there. Someone reads it and draws a conclusion. |
| "the market rewards" | Markets don't reward. Buyers pay for things. |
Instead: Name the human. "The team fixed it that week" beats "the complaint becomes a fix." If no specific person fits, use "you" to put the reader in the seat.
Narrator-from-a-Distance
Floating above the scene instead of putting the reader in it.
| Pattern | Problem |
| "Nobody designed this." | Disembodied observation |
| "This happens because..." | Lecturer voice |
| "This is why..." | Same |
| "People tend to..." | Armchair sociologist |
Instead: Put the reader in the room. "You don't sit down one day and decide to..." beats "Nobody designed this."
Passive Voice
Every sentence needs a subject doing something. Passive voice hides the actor and drains energy.
| Pattern | Fix |
| "X was created" | Name who created it |
| "It is believed that" | Name who believes it |
| "Mistakes were made" | Name who made them |
| "The decision was reached" | Name who decided |
Instead: Find the actor. Put them at the front of the sentence.
Sentence Starters to Avoid
| Pattern | Fix |
| Sentences starting with What, When, Where, Which, Who, Why, How | Restructure. Lead with the subject or the verb. |
| Paragraphs starting with "So" | Start with content |
| Sentences starting with "Look," | Remove |
Wh- openers become a crutch. "What makes this hard is..." becomes "The constraint is..." or better, name the specific constraint.
Rhythm Patterns
| Pattern | Fix |
| Three-item lists | Use two items or one |
| Questions answered immediately | Let questions breathe or cut them |
| Every paragraph ends punchily | Vary endings |
| Em-dashes | Remove. Use commas or periods. No em dashes at all. |
| Staccato fragmentation | Don't stack short punchy sentences |
| "Not always. Not perfectly." | Hedging disguised as reassurance |
Word Patterns
| Pattern | Problem |
| Lazy extremes (every, always, never, everyone, everybody, nobody) | False authority. Use specifics instead of sweeping claims. |
| All adverbs (-ly words, "really," "just," "literally," "genuinely," "honestly," "simply," "actually") | Empty emphasis. See Adverbs section above. |
Examples
Example 1: Throat-Clearing + Binary Contrast
Before:
"Here's the thing: building products is hard. Not because the technology is complex. Because people are complex. Let that sink in."
After:
"Building products is hard. Technology is manageable. People aren't."
Changes: Removed opener, binary contrast structure, and emphasis crutch. Direct statements.
Example 2: Filler + Unnecessary Reassurance
Before:
"It turns out that most teams struggle with alignment. The uncomfortable truth is that nobody wants to admit they're confused. And that's okay."
After:
"Teams struggle with alignment. Nobody admits confusion."
Changes: Cut hedging ("most"), removed throat-clearing phrases, deleted permission-granting ending.
Example 3: Business Jargon Stack
Before:
"In today's fast-paced landscape, we need to lean into discomfort and navigate uncertainty with clarity. This matters because your competition isn't waiting."
After:
"Move faster. Your competition is."
Changes: Eliminated jargon entirely. Core message in six words.
Example 4: Dramatic Fragmentation
Before:
"Speed. Quality. Cost. You can only pick two. That's it. That's the tradeoff."
After:
"Speed, quality, cost—pick two."
Changes: Single sentence. No performative emphasis.
Example 5: Rhetorical Setup
Before:
"What if I told you that the best teams don't optimize for productivity? Here's what I mean: they optimize for learning. Think about it."
After:
"The best teams optimize for learning, not productivity."
Changes: Direct claim. No rhetorical scaffolding.
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.

