explaingit

drunkrhin0/antislop

1Audience · writerComplexity · 1/5ActiveLicenseSetup · easy

TLDR

Two agent skills that steer Claude Code or opencode away from AI writing tells and score any text out of 100 for common slop patterns.

Mindmap

mindmap
  root((antislop))
    Inputs
      Draft text
      Agent prompts
    Outputs
      Cleaner prose
      Score out of 100
      Violations table
    Use Cases
      Audit AI drafts
      Style guard for agents
      Edit marketing copy
    Tech Stack
      Markdown
      Agent Skills
      Claude Code
      opencode

Things people build with this

USE CASE 1

Run an audit on a blog draft and get a score with a list of banned words and filler phrases to fix

USE CASE 2

Keep the antislop skill loaded in Claude Code so writing tasks avoid em-dashes and inflated adjectives

USE CASE 3

Paste the SKILL.md text into a chat tool that has no skill support to get the same style guardrails

USE CASE 4

Check ChatGPT or Claude output against the audit before publishing to clean up scare quotes and rule-of-three patterns

Tech stack

MarkdownSkillsClaude Code

Getting it running

Difficulty · easy Time to first run · 5min

Works only inside agents that read SKILL.md or AGENTS.md; plain chat tools need the file pasted into the prompt.

MIT license, free to use and modify with attribution and no warranty.

In plain English

Antislop is a small project aimed at stripping the most recognizable AI writing patterns out of text. It does this through two skills you plug into an AI coding agent, such as Claude Code or opencode. Any agent that reads the SKILL.md or AGENTS.md convention can pick them up. The README frames the project as a late shower thought from a frustrated LinkedIn rant about machine-written copy. The two skills do different jobs. The first, called antislop, is a writing style skill that stays on in the background and quietly steers everything the agent writes away from common AI tells. The second, called antislop-audit, is a detection skill that takes a piece of text and returns a score out of 100, a violations table with severity and excerpt, and a plain summary of what to fix first. The README lists what the audit looks for. It flags a list of banned vocabulary, including filler verbs, inflated adjectives, and other words associated with AI prose, plus banned filler phrases like it's worth noting and at its core. It catches em-dashes used as authority props, scare quotes that hedge instead of commit, random bolding that decorates rather than emphasizes, and ambiguous bolded bullets where the body does not support the claim. It also flags the rule of three, synonym cycling, vague attributions, and chatbot artifacts such as I hope this helps or Great question. The score is split into bands. From 85 to 100 the text reads like a person, from 65 to 84 there is some slop that targeted edits will fix, from 40 to 64 a significant rewrite is needed, and below 40 the text reads like unreviewed AI output. The audit gives no exceptions based on the writer's intent. Installation is short. The simplest path is to run a single openskills command that pulls the skills from GitHub, but you can also ask the agent to install it directly, or copy the antislop and antislop-audit folders into your skills directory by hand. For chat tools that do not support skills, you can paste the SKILL.md contents at the start of a conversation. The project credits two earlier MIT projects, a Reddit thread on copywriting, and Wikipedia's signs of AI writing as inspiration, and is itself MIT-licensed.

Copy-paste prompts

Prompt 1
Install the antislop and antislop-audit skills into my Claude Code skills directory using a single openskills command
Prompt 2
Audit this paragraph for AI slop and return the score, the top three violations, and a rewritten version
Prompt 3
Show me what patterns antislop-audit flags as severity high and give an example fix for each
Prompt 4
Write a Claude Code workflow that runs antislop-audit on every paragraph in a markdown file and prints a per-section score
Prompt 5
Compare two drafts of the same blog post using antislop-audit and tell me which one passes the 85 plus band
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.