.claude/skills/stop-slop/SKILL.md
A skill for removing AI-generated writing patterns ('slop') from prose. Eliminates telltale signs of AI writing like filler phrases, excessive hedging, overly formal language, and mechanical sentence structures. Use when: writing content that should sound human and natural, editing AI-generated drafts, cleaning up prose for publication, or any content that needs to sound authentic rather than AI-generated. Triggers: 'stop-slop', 'remove AI tells', 'clean up prose', 'make it sound human', 'edit AI writing'.
npx skillsauth add alfredolopez80/multi-agent-ralph-loop stop-slopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
~/.claude/settings.json or CLI/env varsANTHROPIC_DEFAULT_*_MODEL env varsA skill for removing AI tells from prose. AI writing has patterns—predictable phrases, structures, and rhythms. Once you notice them, you see them everywhere.
Throat-clearing openers — Generic openings that delay the actual content:
Emphasis crutches — Overused emphasis patterns:
Business jargon — Empty corporate speak:
Binary contrasts — Forced either/or framings:
Dramatic fragmentation — Unnecessary line breaks for emphasis:
Rhetorical setups — Predictable question-answer patterns:
Tripling — Lists of three as a pattern:
Metronomic endings — Sentences that all end the same way
Immediate question-answers — Ask and answer in same paragraph
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 the content.
When editing content:
While removing slop, keep:
This skill does NOT:
| AI Pattern | Fix | |------------|-----| | "It is important to note that" | Delete or state directly | | "In conclusion" (as transition) | Just end or summarize | | "Furthermore/Moreover" | Delete or use specific transition | | "plays a crucial role" | "is important" or describe role | | "manner in which" | "how" | | "due to the fact that" | "because" | | "each and every" | "each" or "every" | | "a wide array of" | "many" | | "As mentioned above" | Just continue | | "This demonstrates that" | Just state what it demonstrates |
BEFORE (AI Slop):
"It is important to note that consistent practice plays a crucial role in skill development. Furthermore, one must consider that motivation is a key factor in maintaining this consistency. Moreover, this highlights the importance of setting realistic goals."
AFTER (Human):
"Consistent practice develops skills. Motivation keeps you going, so set realistic goals."
BEFORE (AI Slop):
"It should be noted that there are various different approaches to solving this problem. Each approach offers a unique set of advantages and disadvantages. In conclusion, the best choice depends on the specific context."
AFTER (Human):
"Several approaches can solve this problem. Each has pros and cons. Pick what fits your situation."
BEFORE (AI Slop):
"Certainly! Let's dive right in. In today's fast-paced digital landscape, businesses must leverage the power of technology to stay competitive. It's crucial to understand that digital transformation is not just a buzzword."
AFTER (Human):
"Let's dive in. To stay competitive, businesses need technology. Digital transformation matters."
Claude Code: This folder is a skill. Invoke @stop-slop when editing prose.
Claude Projects: Upload SKILL.md to project knowledge.
API calls: Include SKILL.md in your system prompt.
For complete lists, see:
references/phrases.md — Full banned phrases listreferences/structures.md — Structural patterns to avoidreferences/examples.md — More before/after transformationsBased on work by Hardik Pandya
development
Living knowledge base management. Actions: search (query vault), save (store learning), index (update indices), compile (raw->wiki->rules graduation), init (create vault structure). Follows Karpathy pipeline: ingest->compile->query. Use when: (1) searching accumulated knowledge, (2) saving learnings, (3) compiling raw notes into wiki, (4) initializing a new vault. Triggers: /vault, 'vault search', 'knowledge base', 'save learning'.
testing
Produce a verifiable technical specification before coding. 6 mandatory sections: Interfaces, Behaviors, Invariants (from Aristotle Phase 2), File Plan, Test Plan, Exit Criteria (executable bash commands + expected results). Use when: (1) before implementing features with complexity > 4, (2) as Step 1.5 in orchestrator workflow, (3) when requirements need formalization. Triggers: /spec, 'create spec', 'write specification', 'technical spec'.
testing
Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
development
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.