agentleFS
elithrarelithrar/dotfiles/.agents/skills/anti-slop/SKILL.md

anti-slop

Skill222 starsChanged 58 days agoMITView on GitHub

Edit formulaic or AI-sounding prose while preserving the author's voice. Use for an anti-slop pass, editorial review, or requests to make writing sound more human; ordinary drafting does not require this skill.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use research and handoff.

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.
  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 32 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. Distinctive:

    Read the whole piece to understand its voice.

    line 10

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

Anti-slop editing

Make small phrasing changes that remove filler without flattening voice. Preserve facts, citations, technical claims, paragraph structure, and the author's argument unless the user asks for a broader rewrite. Stylistic patterns cannot establish whether a person or model wrote a passage.

Read the whole piece to understand its voice. Flag phrasing only when it adds no meaning or repeats a formula; preserve deliberate fragments, parallelism, humor, and useful contrast. When a candidate could be an intentional choice, leave it or explain the tradeoff.

For a detailed pass or a contested edit, read references/tells.md for patterns and examples. Do not treat its vocabulary as banned words.

For a review request, return the material findings and suggested edits. For an edit request, apply the changes and reread the affected passages for meaning and rhythm. Follow the requested output format; explain only significant edits, and omit a change log when the user asks for just the revised text.

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.