Guide · Agent skill
How to use the Stop Slop agent skill: install and trigger it
Updated · written with AI from the project's own documentation and checked against our catalogue data
Stop Slop is an agent skill that makes an AI agent check its prose against a set of rules for removing common signs of AI-generated writing, such as filler openers, needless adverbs, passive voice, dramatic fragments and em dashes. It is for writers, newsletter authors and editors who want drafts to read less like a chatbot produced them. This guide explains what the skill does, how to install it, how to trigger it, and where it falls short.
Quick start
- 1Download the ZIP. Download the stop-slop ZIP from this page and unzip it.
- 2Choose a location. Put the stop-slop folder in ~/.claude/skills/ for personal use, or in a project's .claude/skills/ folder.
- 3Or upload it in the apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 4Ask for writing work. Request drafting, editing or reviewing in plain language, naming stop-slop if you want to be certain.
- 5Review the changes. Read each suggested edit and keep the ones that improve clarity and keep your intended meaning.
What is an agent skill, and what does Stop Slop make the agent do?
An agent skill is a folder of instructions that an AI agent can load when a task calls for it. Stop Slop's main file, SKILL.md, tells the agent to apply a set of writing rules when it drafts, edits or reviews prose.
The rules cover filler phrases, formulaic structures, passive voice, vague declaratives and quotable lines. The agent also scores text from 1 to 10 on directness, rhythm, trust, authenticity and density, and revises anything scoring below 35 out of 50.
- Cut throat-clearing openers, emphasis crutches and adverbs.
- Replace passive voice with a human subject doing something.
- Remove binary contrasts such as 'not X, it's Y' and dramatic fragments.
- Vary sentence length and remove em dashes.
- Name specifics instead of writing vague declaratives.
How do you install the Stop Slop skill?
Download the stop-slop ZIP from this page and unzip it. Then put the stop-slop folder in one of these locations, depending on how you work.
For a personal setup available across projects, place it in ~/.claude/skills/. For a single project, place it in that project's .claude/skills/ folder. You can also upload the skill in the Claude apps under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/stop-slop/
- Project: .claude/skills/stop-slop/ inside your project folder
- Claude apps: Settings → Capabilities → Skills, then upload the skill
How do you trigger the skill with natural requests?
You do not need a special command. The skill's description says it applies when drafting, editing or reviewing text, so ask for that work in plain language and name the skill if you want to be sure it runs.
The metadata trigger for the skill is 'Writing prose, editing drafts, reviewing content for AI patterns'. Requests that match that description are the ones it is designed for.
- 'Edit this newsletter draft with the stop-slop skill.'
- 'Review this essay for AI writing patterns.'
- 'Draft a blog intro about our product launch and apply stop-slop.'
- 'Tighten this paragraph and remove filler phrases.'
What do the reference files add?
SKILL.md points to three reference files. references/phrases.md lists phrases to remove, references/structures.md covers structural patterns to avoid, and references/examples.md contains before-and-after transformations.
The README describes these files as loading on demand in API setups. The CHANGELOG lists example phrases such as 'Here's what I find interesting' and 'Not X. But Y.' that the reference files target.
What does the skill need, and is it safe to run?
The skill lists no requirements. It does not run scripts and does not use the network. The files included are CHANGELOG.md, README.md and SKILL.md, with the reference folder described in the README.
The skill is MIT licensed and its author is Hardik Pandya. Because it only gives the agent writing rules, it has no install scripts to review, but you should still read SKILL.md before installing any skill you did not write.
Tips for getting good results
Run the skill on a draft you have written, then read every change. The rules are strict, and some edits can alter meaning or remove tone you wanted to keep.
Give the agent the context it needs, such as the audience and the publication, so it does not strip a voice you chose on purpose.
- Check that quoted material and names are not changed.
- Keep a copy of your original draft to compare.
- Use it as a checklist for your own edits, not a final judge of quality.
What people use it for
- Cleaning up a blog post draft before publishing.
- Tightening a newsletter so openers and closers sound less formulaic.
- Editing an essay to replace passive constructions with active ones.
- Reviewing marketing copy for generic, repetitive phrasing.
Frequently asked questions
Is the Stop Slop skill free?
Yes, the skill is released under the MIT licence, as stated in its SKILL.md and README. The source does not list any price.
What do I need to use Stop Slop?
The skill lists no requirements. It runs no scripts and uses no network access, so you only need an agent that can load skills.
How do I install the stop-slop skill in Claude?
Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. In the Claude apps, you can upload it under Settings → Capabilities → Skills.
Can Stop Slop detect whether text was written by AI?
No. It only edits prose toward its rules. It does not detect AI-written text.
Does Stop Slop work outside Claude?
The README says it can be used with Claude or any LLM, through Claude Projects uploads, copied custom instructions, or API system prompts that include SKILL.md.
When should I not use Stop Slop?
Avoid it for content that must keep a specific required tone or legal wording, and for academic or technical writing where passive voice is a standard convention.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Stop Slop suits writers, newsletter authors and editors who want a consistent checklist for removing predictable AI phrasing from blog posts, newsletters and essays. It is a poor fit for legal, required-tone or academic writing, where its rules can change meaning or conflict with conventions. If you need a tool that detects AI-written text, pick something else.
Download the skill