The 6 Best Anti AI Slop Claude Skills In 2026

No AI Slop

What sold me was the change list. I pasted a rough draft into Claude Code, ran the skill, and it printed every edit it made. I could accept or reject each one. Most cleanup tools just hand back a rewritten block and hope you don’t look too closely.

It also names the pattern. My draft had three versions of “It’s not X. It’s Y.” and a throat-clearing opener I’d written without noticing. Each got flagged with its name attached. That loop taught me more than a silent rewrite ever would.

There is a detect mode too. I typed “is this slop?” at a paragraph I doubted. It quoted the patterns it spotted and left the text alone. Handy when you want a second opinion, not an edit.

The traction is not small. The repo showed 12.5k stars and 873 forks when I checked in late October. One independent writeup reported about 1,000 stars within a day and called it a narrow, single-purpose skill that does one job.

Now the limits. It fixes tells, not substance. If the argument is thin, tidy language will not save it. Skeptics on r/ClaudeAI made the same point about comparable skills. A pass can smooth the surface and leave the mush underneath. I found that true in my own testing.

It will not make text pass AI detectors either. Different problem entirely. I treat this as a readability and voice tool, nothing more.

Who should use it: writers, newsletter authors, founders, developers drafting with Claude who want the assists to stop reading like assists. My loop matches Yang’s stated 25/50/25 rule. Draft it yourself first. Run the skill. Read the change list line by line. Then do your own final pass.

Skip that last pass and you are trusting the tool over your own taste. I would not.

Make Interfaces Feel Better

Before anything else, I noticed this wasn’t your usual fuzzy prompt pack. The rules are exact. Outer radius equals inner radius plus padding. Tabular-nums on live numbers. Optical alignment over geometric. 40x40px minimum hit areas. Claude has something specific to check, not a mood to chase.

I installed it with one command and asked for a quick review of an existing page. What came back: severity ratings, file:line citations, then a Block or Approve verdict. I liked that. A nitpick without a location just wastes a round trip.

Micro-interactions are where it earns its keep. Press feedback at scale(0.96), interruptible transitions instead of keyframes, exits quieter than enters. This is exactly the layer AI-generated UI tends to skip. As June 2026 writeup puts it, none of the individual tricks are novel in isolation; the value is the whole checklist in one place with the CSS to apply it, packaged as an installable skill for Claude Code, Cursor and friends.

Don’t stack skills that fight over the same layer. Three or four complementary ones, no more.

Honest limit: no benchmarks exist. The payoff is perceived craft and consistency, not measured lift.

Also, Krehel has since split the material into focused better-ui, better-typography and better-colors skills inside a plugin family that a third-party listing counts at 7.5K stars. The standalone skill remains the cleanest single install.

Against the rest of this list, SuperDesign gives the premium typography and whitespace look, Better Icons cleans the icon layer. This one fixes how the interface behaves when you touch it. That’s the layer I’d install it for.

Better Icons

Once you notice it, you can’t unsee it. Ask Claude for a dashboard without guidance and it reaches for Lucide every time. Hacker News users literally said they discovered Lucide “thanks to claude always using it,” and that these icons now “instantly ring everyone’s slop alarm bells.”

Better Icons is the escape hatch. It gives Claude keyword search across 200,000-plus icons from 150-plus collections: Lucide, Heroicons, Material Design, Tabler, Phosphor, Remix, Font Awesome. Instead of a reflex pick, the model chooses deliberately.

I liked the workflow. You search a keyword, grab an ID like lucide:home or heroicons:check, and the SVG syncs straight into your project’s icons file. React, Vue, Svelte, Solid, or raw SVG all work. No bouncing between five icon sites before lunch. That grind was real, and Tony Lee’s 2026 roundup describes it almost word for word. He kept Better Icons as the only icon-specific skill that survived his delete-within-a-week test.

The sync also saves tokens. Pasting raw SVGs into chat burns context fast. Pointing Claude at a file does not. And emoji icons, the other classic slop signature, get replaced with actual SVGs.

One honest knock. Lee notes search quality varies by collection, though common UI icons resolve quickly. That matched my testing.

Security-wise it passed 3 of 3 skills.sh scanners and earned an A grade from Skills Directory. That grade carries one medium note: it installs npm packages at runtime. Read the SKILL.md first, like you should with any skill.

Position it as your asset layer. SuperDesign and Make Interfaces Feel Better fix typography and whitespace. Audit skills flag generic icons. Better Icons supplies the actual files. I’d install three or four skills total, one concern each. The repo last saw an update in April 2026, so skim the changelog before betting a big project on it.

Humanizer

I pasted two paragraphs of an old newsletter in and told it to match my voice. What came back kept my short opener, my habit of ending on a one-liner, and, best of all, my em dashes. That last part sold me. Most anti-slop tools strip every dash on sight. Humanizer sees your sample uses them and backs off.

The mechanics are simple. You run /humanizer, paste a sample, then paste the AI text. Under the hood it checks 26 patterns lifted from Wikipedia’s Signs of AI writing guide. Some fire on one sighting: “Not X but Y” reframes, “Let that sink in” closers, staged run-ups like “Honestly?”. Weaker tells only count in clusters. It also refuses to flag a lone em dash, which tells you the list was written by someone who edits.

Then comes the second pass. It drafts a rewrite, asks itself what still reads as AI, and revises. That self-critique is the part I’d keep if I could only keep one thing.

Now the limits, because there are real ones. The repo is blunt: this edits for human readers, and detectors still flag most output. Ars Technica found in January 2026 that prose came out more casual and less precise, and warned the have-opinions instruction is a bad fit for technical docs. I’d agree. Don’t run it on API references.

Here’s the part most people skip. Run it without a sample and you get clean, neutral text. Not yours. A Superbash walkthrough from August 2026 hit the same wall before adding a personality file. The sample is the step to skip if you like generic output.

Competitor No AI Slop claims voice preservation but has no sample mode. If voice is your need, this is the one.

SuperDesign

Most of the skills in this listicle, No AI Slop, Better Icons, Humanizer, are prompt wrappers. They change the words Claude writes. SuperDesign changes who makes the design call. It hands that call to a separate agent on a canvas and gives you real markup back.

I installed the CLI, ran the login, then added the skill. Inside Claude Code I typed something like /superdesign help me design a settings page that doesn’t look like default AI slop. What came back was actual HTML on an infinite canvas, with a draft id and a preview link. Not a screenshot.

Forking is the part I liked. Each draft stacks constraints, dark theme, minimal, editorial, so variations sit side by side instead of overwriting each other. I picked with my eyes, then handed the winning prompt back to Claude to implement. It also reads my codebase, pulls a brand guide from a live URL, and remembers the project next session. Version history and direct canvas editing exist too.

The catch. Generation needs an account, and the company’s own FAQ lists a free tier plus a flat $20/month. Design-heavy sessions are token-hungry, and Business Insider reported Anthropic roughly doubled its Claude Code cost estimate in April 2026. Check dates too. Older write-ups about Super Design cover an archived VS Code extension, a different project. One independent tester flagged excessive whitespace on content-heavy pages. Still, Anthropic now ships its own /design command, so this workflow is clearly sticking around.

Anti-AI-Slop Writing

First thing I did was paste the classic opener: “In today’s rapidly evolving technological landscape…” Claude produced three flags at once. “Landscape” hit the banned-word list. The opening frame matched a banned stock phrase. The next paragraph started with “Moreover,”, one of 16 banned sentence openers. I hadn’t seen a skill catch that many tells in one pass.

The word list is the main draw. 50+ banned words, 35+ stock phrases, 16 openers. The vocabulary sits in a separate references/banned-words.md that loads on demand, keeping the main skill file under 500 lines. That design matters if you run this daily.

These words are not paranoia. Pew Research Center‘s August 2026 analysis of roughly 490,000 webpages found AI-typical vocabulary more than doubled since 2023, with em dashes appearing about twice as often.

Now the honest critique. Word bans fix surface tells. A highly upvoted commenter in an r/ClaudeAI thread put it plainly: “The slop comes from the structure, not the words.” Fair point. This skill answers it with 10 structural rules, covering uniform sentence length, rule-of-three, hedging seesaw. It also blocks invented statistics and fabricated quotes outright. That last rule is why I trust it more than a pure word filter.

Word lists also age. What screamed AI in 2024 barely registers now, and new tells keep arriving with every model generation. A skill with a maintainable banned-words file beats a static prompt for exactly that reason.

If you want pattern-based philosophy, No AI Slop has the bigger community. For raw banned-word volume, nothing else comes close. I run this as a separate pass after drafting, never during.