stop-slop — Claude Code skill: what it does, how to install
This skill removes predictable AI writing patterns from prose. Use it when drafting, editing, or reviewing text for formulaic phrasing.
npx skills add hardikpandya/stop-slop --skill stop-slop -a claude-codeWhat stop-slop does
stop-slop checks prose for patterns that often make AI-written text recognizable. It removes filler and emphasis crutches, pushes the writer toward specific wording and active voice, and keeps the reader in the scene. Its rules also cover sentence rhythm, vague claims, rhetorical setups, and formulaic contrasts.
The skill includes core rules, quick checks, a five-part scoring table, and references to references/phrases.md, references/structures.md, and references/examples.md. It is intended for drafting, editing, and reviewing prose in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
The rules are strict: they call for removing all adverbs, passive constructions, and stock contrast patterns. Check the result yourself when the source text relies on a deliberate style.
What it helps with
- remove formulaic phrases from a draft
- rewrite passive sentences with a human subject
- replace vague claims with specific wording
- check prose for repetitive structures and rhythm
- score a draft across five writing criteria
Example prompts for the agent
- Review this draft for predictable AI writing patterns and rewrite the weak passages.
- Edit the text by removing filler, passive voice, and vague declarative statements.
- Run a final prose check using `references/phrases.md` and `references/structures.md`.
How to install stop-slop
1Skills CLI (Vercel)
npx skills add hardikpandya/stop-slop --skill stop-slop -a claude-code2Manually: put the files in place
~/.claude/skills/stop-slop/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/stop-slop/
1Skills CLI (Vercel)
npx skills add hardikpandya/stop-slop --skill stop-slop -a codex2Manually: put the files in place
.agents/skills/stop-slop/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hardikpandya/stop-slop --skill stop-slop -a cursor2Manually: put the files in place
.cursor/skills/stop-slop/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hardikpandya/stop-slop stop-slop2Manually: put the files in place
.github/skills/stop-slop/SKILL.md1Skills CLI (Vercel)
npx skills add hardikpandya/stop-slop --skill stop-slop -a gemini-cli2Platform CLI
gemini skills install https://github.com/hardikpandya/stop-slopManually: put the files in place
.devin/skills/stop-slop/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add hardikpandya/stop-slop --skill stop-slop -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Similar
Questions about stop-slop
How do I install stop-slop in Claude Code?
Run npx skills add hardikpandya/stop-slop --skill stop-slop -a claude-code, then run the same command again. The installed file is available at ~/.claude/skills/stop-slop/SKILL.md.
What does stop-slop do?
The skill finds predictable AI writing patterns and helps rewrite them. It checks filler, active voice, specificity, reader focus, rhythm, and formulaic structures.
Which platforms support stop-slop?
The skill is listed for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
Source text
SKILL.md · MIT
---
name: stop-slop
description: Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
metadata:
trigger: Writing prose, editing drafts, reviewing content for AI patterns
author: Hardik Pandya (https://hvpandya.com)
---
# 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](references/phrases.md).
2. **Break formulaic structures.** Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See [references/structures.md](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:
| Dimension | Question |
|-----------|----------|
| Directness | Statements or announcements? |
| Rhythm | Varied or metronomic? |
| Trust | Respects reader intelligence? |
| Authenticity | Sounds human? |
| Density | Anything cuttable? |
Below 35/50: revise.
## Examples
See [references/examples.md](references/examples.md) for before/after transformations.
## License
MIT
© Hardik Pandya (https://hvpandya.com) · MIT · hardikpandya/stop-slop