agentleFS
Sign inStart free
Darius-TokamDarius-Tokam/superSkill/skills/anti-blabla/SKILL.md

anti-blabla

Skill4 starsChanged 26 days agoMITView on GitHub

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

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. TokDar2410621/superSkill★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    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. Distinctive:

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

    line 15
  2. Distinctive:

    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. Distinctive:

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

    line 21
  5. Distinctive:

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

    line 23
  6. Distinctive:

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

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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