agentleFS
Sign inStart free
rsdltrsdlt/rsdlt.github.io/.agents/skills/stop-slop/SKILL.md

stop-slop

Skill1 starsChanged 26 days agoMITView on GitHub

Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.

44 other projects use a version of this, 16 of them edited; 1 new project in the last 4 weeks, against 3 the 4 before.

Adopted by

Cooling: 1 new project took it in the last 4 weeks, 0.3× the 4 weeks before.thin data

Week of Sep 13: 1 new projectWeek of Sep 20: 0 new projectsWeek of Sep 27: 1 new projectWeek of Oct 4: 1 new projectWeek of Oct 11: 0 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 4 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use operational-enterprise-ai, product-proof-saas and 10 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.
  • boraoztuncSkill

    operational-enterprise-ai

    Create or redesign enterprise AI, automation, security, and operations product pages that explain system boundaries, approvals, auditability, exceptions, and rollback. Use for dark cinematic heroes, hairline grids, metric pauses, expandable solution rows, case-study evidence, security proof, and qualified demo or waitlist handoffs.

    Also in 3 projects that use this

  • boraoztuncSkill

    product-proof-saas

    Create or redesign SaaS and AI product landing pages where a real workflow, interface, or deterministic demo is the central proof. Use for pale atmospheric shells, product UI in the hero, prompt-to-output stories, audience tabs, compact feature modules, honest pricing comparisons, and FAQ handoffs.

    Also in 3 projects that use this

  • Dragoon0xSkill

    pricing-page

    Present pricing in ways that reduce friction and increase clarity. Handles tier naming, feature comparison, anchor pricing, and plan selection psychology. Use when designing pricing pages, plan selectors, or upgrade prompts.

    Also in 3 projects that use this

  • brpazSkill

    tailwind-v4

    Configure Tailwind CSS v4 with Oxide, CSS-first directives, migration steps, and production guidance.

    Also in 3 projects that use this

  • ParthJadhavSkill

    app-store-screenshots

    Use when building App Store or Google Play screenshot pages, generating exportable marketing screenshots for iOS, macOS, and/or Android apps, or scaffolding a screenshot editor with Next.js. Triggers on app store, mac app store, play store, screenshots, marketing assets, html-to-image, phone mockup, mac mockup, android screenshots, feature graphic.

    Also in 3 projects that use this

  • seikaikyoSkill

    banner-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

  • +1 more from boraoztunc

The file

We split this skill into the rules it gives an agent

6 rules. 5 are common, 1 is distinctive, and 0 are very specific to this project.

  • 5

    Common

    Most of the 19 edited versions we read keep these.

  • 1

    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
  1. Common:

    Cut filler phrases: Remove throat-clearing openers, emphasis crutches, and all adverbs.

    line 15
  2. Common:

    Break formulaic structures: Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency.

    line 17
  3. Distinctive:

    Use active voice: Every sentence needs a human subject doing something.

    line 19
  4. Common:

    Be specific: No vague declaratives ("The reasons are structural").

    line 21
  5. Common:

    Put the reader in the room: No narrator-from-a-distance voice.

    line 23
  6. Common:

    Cut quotables: If it sounds like a pull-quote, rewrite it.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 19 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Stop Slop

Eliminate predictable AI writing patterns from prose.

Core Rules

  1. Cut filler phrases. Remove throat-clearing openers, emphasis crutches, and all adverbs. See references/phrases.md.
  2. Break formulaic structures. Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See references/structures.md.
  3. 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").
  4. Be specific. No vague declaratives ("The reasons are structural"). Name the specific thing. No lazy extremes ("every," "always," "never") doing vague work.
  5. Put the reader in the room. No narrator-from-a-distance voice. "You" beats "People." Specifics beat abstractions.
  6. Vary rhythm. Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes.
  7. Trust readers. State facts directly. Skip softening, justification, hand-holding.
  8. 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:

DimensionQuestion
DirectnessStatements or announcements?
RhythmVaried or metronomic?
TrustRespects reader intelligence?
AuthenticitySounds human?
DensityAnything cuttable?

Below 35/50: revise.

Examples

See references/examples.md for before/after transformations.

License

MIT

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free