stop-slop

hardikpandya/stop-slop · Agent Skill

Removes predictable AI writing patterns from text, making it more natural and human-like.

Jump to install ↓

Overview

PublisherhardikpandyaCommunity
Repositoryhardikpandya/stop-slop ↗
Skill folderstop-slop
Stars16,902
Bundled files4
LicenseMIT
Last updatedMarch 16, 2026
LinksSkill source ↗

Mozgi check

What we found in the skill files. Details come with a subscription.

Security
low risk · no obvious risks found — the full report shows the details
Compatibility
instructions only — works with most agents
Similar skills
133 similar skills found
Also with subscription

Installation

A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.

Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.

Install the “stop-slop” skill from mozgi.io (https://mozgi.io/skills/stop-slop/) for me.

1. Download the archive: https://mozgi.io/skills/stop-slop/download
   If it fails, take the skill folder from the source: https://github.com/hardikpandya/stop-slop
2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me.
3. Put the “stop-slop” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.).
4. Make sure <skills folder>/stop-slop/SKILL.md exists.
5. Briefly tell me what this skill does and offer to try it on my task.

If you cannot do a step yourself, tell me what to click or type.

Review the source files

4 files Download Zip

Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.

SKILL.md contents

Original author text · read-only

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.

2. Break formulaic structures. Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See 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 for before/after transformations.

License

MIT

Frequently asked questions

What does the stop-slop skill do?

Removes predictable AI writing patterns from text, making it more natural and human-like.

How do I install stop-slop?

Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.

Which AI models work with stop-slop?

Skills are plain Markdown instructions (the Agent Skills format), so stop-slop works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.

Is stop-slop free?

The skill is published openly by hardikpandya under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.

Is it safe to install skills?

A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.

How is a skill different from an MCP server or a plugin?

An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.

Related skills

All skills →