Keep your content off the AI slop list
Have your Claw periodically check the AI Slop Wiki and build a living filter of patterns to avoid. Every piece of content your Claw creates runs through this filter first, so you never publish anything that reads like generic AI-generated filler.
Create a skill called "Anti-AI Slop". Weekly, visit https://en.wikipedia.org/wiki/AI_slop and find all of the patterns that are considered the latest in AI slop. Update your Anti-AI Slop skill with the latest patterns. Then any content you create should go through this filter to make sure we don't fall into any of these traps.
This skill turns your Claw into a self-updating content quality gate. It
reads the Wikipedia AI Slop article on a schedule, extracts the patterns
that define low-quality AI output, and maintains a living checklist. Every
piece of content your Claw produces gets checked against that list before
you see it.
Wikipedia-grade AI pattern removal
Comprehensive AI writing cleanup based on Wikipedia's WikiProject AI Cleanup guidelines. Catches 24+ distinct patterns including inflated symbolism, em dash overuse, rule of three, copula avoidance, and sycophantic tone.
Wikipedia-grade AI pattern removal
Comprehensive AI writing cleanup based on Wikipedia's WikiProject AI Cleanup guidelines. Catches 24+ distinct patterns including inflated symbolism, em dash overuse, rule of three, copula avoidance, and sycophantic tone.
Catch AI writing patterns before your readers do
Sniff out the bot. Run this as a final pass on any prose before publishing. It catches the telltale patterns that scream "AI wrote this" — dramatic contrasts, fake urgency, hollow intensifiers, and all those "Here's the thing:" crutches.
Stop waiting on clients for copy, images, and bios
Content bottlenecks stall launches. This recipe builds a structured content request from your sitemap, sends it to the client, and follows up until everything lands. It keeps the project moving without turning you into a full-time chaser.