elithrar/dotfiles

anti-slop

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.

First seen Aug 12, 2026

Installation

$ npx skills add elithrar/dotfiles --skill anti-slop

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from elithrar/dotfiles · top by installs.

npx skills add elithrar/dotfiles

Browse all from elithrar/dotfiles

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 203
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,292 B
  • docs SUMMARY.md 227 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 103 installs

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](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.