Make AI Drafts Sound Human: Stop Slop Flags the Tells Editors Keep Fixing
A lightweight MIT-licensed skill file that helps editors and agent workflows remove common AI-writing tells from prose without running third-party code on production systems.
What you get from it
What it does
Stop Slop is a Markdown-based writing skill for spotting and removing common AI prose patterns: filler openers, generic emphasis, formulaic contrasts, vague importance claims, passive constructions, and punchline-style endings. The Open-source Projects article frames it as a developer-friendly cleanup tool, but the GitHub repo is the source of truth: it currently ships a SKILL.md file plus reference Markdown, not a packaged Python CLI.
Who should use it
Use it for AI-assisted blog drafts, docs, release notes, PR descriptions, support replies, and prompt outputs that need a sharper editorial pass. It is especially useful when the draft is factually fine but reads like template-generated AI copy.
Setup surface
The safest setup is to treat Stop Slop as a checklist or system-prompt fragment. Copy the relevant rules into your editor or agent instructions, then adapt them to your house style. Do not blindly clone and execute anything from a third-party project on a production Raspberry Pi or runner.
Practical LinkLoot angle
For LinkLoot, Stop Slop works best as a pre-publish quality gate. Blog posts and Loot descriptions can use it to remove filler while keeping source citations, technical terms, pricing caveats, and security warnings intact. The useful version is not an aggressive word killer; it is a final pass that asks whether each sentence says something specific.
Risk notes
The repo is MIT licensed and mostly Markdown, which keeps runtime risk low. The main editorial risk is overcorrection: some rules, such as removing all adverbs or forcing every sentence into active voice, can damage technical accuracy. Treat the rules as review prompts, not absolute automation. The article's Python-script framing did not match the current GitHub repo, so the repository should be checked before recommending an install path.
Source links
- Open-source Projects article: https://www.opensourceprojects.dev/post/stop-slop
- GitHub repository: https://github.com/hardikpandya/stop-slop
- Core skill file: https://raw.githubusercontent.com/hardikpandya/stop-slop/main/SKILL.md
- MIT license: https://raw.githubusercontent.com/hardikpandya/stop-slop/main/LICENSE
Discussion
Share practical experience, questions, or warnings with the community.
Sign in to join the discussion and vote on comments.
Sign in