Stop Slop — strip the AI tells out of your prose
Catches banned phrases, structural clichés and rhythm tells, then scores your draft 1–10 on five dimensions.
- What
- Catches banned phrases, structural clichés and rhythm tells, then scores your draft 1–10 on five dimensions.
- Cost
- Free
- Needs
- none. No account, no CLI, no MCP server, no paid service.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a plain-instructions skill — no scripts, no tools, no MCP, no account — that teaches an agent to remove predictable AI writing patterns from prose. Its 8 core rules: cut filler phrases; break formulaic structures; active voice with a human subject; be specific, with no vague declaratives and no lazy extremes like 'every / always / never'; put the reader in the room; vary rhythm, mixing sentence lengths; trust readers, with no softening or hand-holding; and cut quotables — if it sounds like a pull-quote, rewrite it. A Quick Checks list turns the rules into a pre-delivery pass: adverbs, passive voice, inanimate subjects doing human verbs, Wh- sentence starters, throat-clearing, 'not X, it's Y' contrasts, matched sentence lengths, punchy one-liner paragraph endings, em dashes, vague declaratives, narrator-from-a-distance voice, and meta-joiners. Scoring rates 1–10 on Directness, Rhythm, Trust, Authenticity, and Density; below 35/50, revise. The skill bans em dashes outright and bans all adverbs — a user who likes either will fight the skill. That is a feature of the skill, not a bug softened in this fiche.
Version:
Install
Copy the install package below, then paste it into Muse📌 Pinned version: commit 8da1f03Prerequisites: none. No account, no CLI, no MCP server, no paid service. Install "Stop Slop — strip the AI tells out of your prose" for me. It gives my agent Hardik Pandya's stop-slop workflow: cut filler phrases and throat-clearing openers, break formulaic structures like binary contrasts and negative listings, enforce active voice with a human subject, demand specifics instead of vague declaratives and lazy extremes, put the reader in the room, vary sentence rhythm, trust the reader, and cut anything that sounds like a pull-quote. Before delivering prose, run its quick checks (adverbs, passive voice, Wh- starters, em dashes, meta-joiners) and score the draft 1–10 on Directness, Rhythm, Trust, Authenticity and Density; below 35/50, revise. Repository: https://raw.githubusercontent.com/hardikpandya/stop-slop/8da1f030185bdfe8471220585162991eaeb970e9/SKILL.md 1. Fetch the SKILL.md file and the references/ folder (phrases.md, structures.md, examples.md) from the repository into a temporary folder. 2. Safety check: review the SKILL.md and references for anything suspicious (unexpected network calls, shell commands, credential harvesting). This skill should contain plain instructions only, no scripts and no secrets. STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its references/ folder into my Muse skills folder, in a folder named "stop-slop". Do NOT use ~/.claude/skills and do NOT use ~/.codex/skills — this is a Muse install. 4. Verify with no network calls: frontmatter name is stop-slop, SKILL.md and all three reference files are in place. 5. Report what was installed, where, and what I still need to do myself (nothing, except paste or point at a draft when I want it edited). This install is copy-paste into Muse, never automatic. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.