By slop for slop, to remove slop in an AI slop world.
Written as a late shower thought from my ranting LinkedIn post
Two skills for writing like a human. Works with your favourite agent that supports SKILL.md or AGENTS.md.
- antislop: a writing style skill. Ambient, always-on. Suppresses AI writing patterns across everything you write.
- antislop-audit: a detection skill. Scores text 0-100 and returns a violations list. Zero exceptions for intent.
It catches:
- Banned vocabulary and phrases
- Antithesis as tone management ("not just X but Y" that decorates instead of argues)
- Structural tells (sentence, paragraph, and discourse-level patterns)
- Formatting habits (em-dashes, scare quotes, bolding, title case)
- Rhythmic giveaways (uniform length, parataxis, overlong sentences)
- Voice-level absences (no opinion, no experience, no position)
npx openskills install drunkrhin0/antislop --globalThis installs to ~/.claude/skills/ so the skills are available across all projects. Leave off --global to install in the current directory instead.
Just ask your agent to install drunkrhin0/antislop from GitHub. Most will figure it out. The repo includes an AGENTS.md file for automatic skill discovery.
The repo ships a .claude-plugin/plugin.json manifest, so it loads as a Claude Code plugin straight from a local clone. No copying files into ~/.claude/skills/ first.
git clone https://github.com/drunkrhin0/antislop.git
claude --plugin-dir ./antislopClaude Code finds skills/antislop/SKILL.md and skills/antislop-audit/SKILL.md under the default skills/ scan, so the manifest does not need to list them one by one. Once loaded, the skills sit under the antislop namespace, for example /antislop:antislop-audit.
Run claude plugin validate .claude-plugin/plugin.json to check the manifest before you rely on it. The repo also ships a .claude-plugin/marketplace.json, so pointing validate at the bare repo root validates the marketplace file instead. Pass the manifest path explicitly to check the plugin.
The repo also self-hosts its own marketplace, so you can install without a local clone:
claude plugin marketplace add https://git.drunkrhin0.au/drunkrhin0/antislop.git
claude plugin install antislop@drunkrhin0Not listed on Anthropic's community marketplace (that submission is a separate, manual step), but self-hosted install works today.
Requires Gemini Advanced. Create a Gem:
- Left sidebar → Gem manager → New Gem
- Name it "Antislop"
- Paste the contents of
skills/antislop/GEMINI.mdinto the instructions field - Save and use that Gem for writing
Free tier: paste skills/antislop/GEMINI.md at the start of any chat instead.
A spawnable subagent with two modes: style (writing) and audit (scoring). Lives in .opencode/agents/antislop.md in the repo. The agent file format is opencode-specific, but the rules content works as a system prompt in any LLM.
Project-level use works automatically when the repo is cloned. opencode discovers .opencode/agents/ in project directories. For global install, copy the agent file:
cp .opencode/agents/antislop.md ~/.config/opencode/agents/Mention @antislop in opencode, or let the primary agent spawn it automatically when it detects a writing or auditing task. The agent is read-only: it returns corrected text or audit results, and the primary agent or user writes files.
The agent is a hand-maintained derivative of the canonical SKILL.md files, like GEMINI.md. When adding a rule, update the agent file alongside the other derivatives.
Copy skill files straight into your agent's directory. No plugin system, no CLI install step.
| Agent | Target directory | What to copy |
|---|---|---|
| Claude Code | ~/.claude/skills/ |
skills/antislop/, skills/antislop-audit/ |
| opencode | ~/.config/opencode/skills/ |
skills/antislop/, skills/antislop-audit/ |
| Gemini CLI | ~/.gemini/extensions/antislop/ |
skills/antislop/gemini-extension.json, skills/antislop/GEMINI.md |
# Claude Code / opencode
cp -r skills/antislop skills/antislop-audit ~/.claude/skills/
# Gemini CLI
mkdir -p ~/.gemini/extensions/antislop
cp skills/antislop/gemini-extension.json skills/antislop/GEMINI.md ~/.gemini/extensions/antislop/Gemini CLI picks up the extension automatically on next launch.
Triggers automatically when you ask your agent to write or edit anything.
Paste text and ask your agent to audit it with /antislop-audit
Returns a Formulaic Writing Risk Score (0-100), a violations table with severity and excerpt, word count, finding density, and a plain-English summary of what to fix first.
Score bands:
- 85-100: Clean. Reads like a person.
- 65-84: Some slop. Fixable with targeted edits.
- 40-64: Heavy slop. Significant rewrite needed.
- 0-39: Severe. This reads like unreviewed AI output.
Writing profiles:
general(default): all rules activetechnical: technical documentation, API references (contextual terms like significant and robust are not penalized)
To add a new profile, see the _profile_guide in rules.json.
The score measures formulaic-writing risk and cannot prove AI authorship.
Let it run ambiently. Both skills trigger automatically when you ask your agent to write, edit, or audit text. They activate on matching intent. No manual invocation needed.
Audit before sending, not while writing. Write freely. Let antislop clean up sentence-level patterns in real time. The mandatory pre-output scan catches em-dashes that slip through. Then run antislop-audit as a final gate before publishing. The audit catches what the style misses: paragraph redundancy, triplet overlap, semantic repetition.
Bring content, not just form. Antislop catches patterns: sentence structure, banned words, rhythm tells. It does not catch vague ideas or unsupported claims. You still need to bring specific experience, numbers, examples, and a point of view.
Run the checklist. The skill includes a 20+ item audit checklist. Run through it before finishing any piece. The items at the bottom matter most: redundancy, triplet overlap, antithesis, metaphors, endings. They catch what pattern matching can't.
Don't over-apply. Antislop is for prose meant to be read by humans. Skip it for code, config files, commit messages, structured data, or API docs. Those have their own conventions.
For Gemini users. The Gem or GEMINI.md copy approach works best. Style mode outputs to Canvas only. No preamble, no commentary. Audit mode returns the score and violations in chat.
Version 2.0 introduces the rule registry (rules.json) as the single source of truth for all writing rules. Each rule has a stable ID, severity, detection class, profile set, and overlap relationships. The generator (generate.py) renders pattern reference files from the registry, and the scorer (score.py) calculates scores using the registry metadata.
What changed from 1.7:
- Score renamed from "Slop Score" to "Formulaic Writing Risk Score"
- Authorship disclaimer added: score cannot prove AI authorship
- Writing profiles: general and technical (extensible via rules.json)
- Diminishing repetition: repeated instances of one rule diminish (100%, 50%, 25%), capped at 3x base weight
- 500-word normalization: comparable scores across different text lengths
- Overlap handling: one primary finding per text span, related findings unscored
- Rule registry: 146 rules with stable IDs, severity weights, and profile assignments
Compatibility boundary: 2.0.0 ships directly from 1.7.0. A 1.8 compatibility release was planned to correct contradictions and overlap handling while preserving the 1.7 score formula, but no 1.8.0 tag was ever cut (see docs/adr/0002); those corrections landed directly in 2.0 instead. The 1.7 score formula is not preserved in 2.0.
- blader/humanizer (MIT): 29-pattern taxonomy grounded in Wikipedia's Signs of AI Writing
- jalaalrd/anti-ai-slop-writing (MIT): banned word and phrase lists, structural pattern rules
- Reddit r/copywriting: hard-banned phrases, emergency replacements, quality checks
- ignorance.ai/field-guide-to-ai-slop: structural patterns, parallelism analysis, metaphor detection, authenticity crisis framing
- Banned: The Definitive Guide (Creative Commons): comprehensive construction, phrase, and pattern taxonomy
- Pangram: exhaustive AI vocabulary cross-reference, phrasing patterns, uniform sentence length, organizational tells
- Anbeeld/WRITING.md (MIT): specificity theater, catalog prose, regularity diagnostics, compound-modifier nuance, medium routing
- Bugcrowd Design System — Tone & Language: plain English substitutions, link text semantics, punctuation tell detection
- hardikpandya/stop-slop (MIT): cherry-picked emphasis crutches, throat-clearing openers, meta-commentary, performative emphasis
- apurvrdx1/tagore (MIT): vocabulary additions (actually, enhance, showcase, interplay) and punchy one-liner closure pattern
- petergyang/no-ai-slop (MIT): padding adverbs, colon reveals, expert cosplay, voice preservation framing, protect-the-fact editing principle
- Self: scare quotes, random bolding, ambiguous bold bullets, em-dash as false authority, voice and authenticity framing
MIT