Anti AI Slop Writing
Jalaaldeen’s writing skill that eliminates detectable AI patterns — 50+ banned words, 35+ phrases, structural tells, punctuation leaks, and accuracy failures.
Overview
Anti AI Slop Writing (jalaalrd) forces agents to produce human-sounding text by constraining vocabulary, structure, punctuation, and formatting patterns that readers and detectors flag. It draws on Carnegie Mellon research, Wikipedia’s Signs of AI Writing, Buffer’s large-scale post analysis, and community detection patterns. Beyond style, it also flags accuracy failures — invented statistics, fabricated quotes, and fake anecdotes — so it doubles as a light hallucination check for marketing copy.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
# Plugin marketplace (founder-toolkit)
/plugin marketplace add jalaalrd/founder-toolkit
# Manual
git clone https://github.com/jalaalrd/anti-ai-slop-writing.git /tmp/anti-ai-slop-writing
cp -R /tmp/anti-ai-slop-writing/skills/anti-ai-slop-writing ~/.claude/skills/For chat UIs: paste SKILL.md at the start of the conversation.
How to use it
Invoke `/anti-ai-slop-writing` or ask the agent to write under anti-slop constraints. Use for tweets, emails, articles, bios, reports, and ads. Load `references/banned-words.md` when auditing long drafts.
Example prompts
- “Use Anti AI Slop Writing to rewrite this tweet thread.”
- “/anti-ai-slop-writing — draft a product launch email for our new analytics export.”
- “Audit this blog post against banned words and structural patterns; list every hit.”
- “Write a founder bio that avoids testament/vibrant/delve and rule-of-three padding.”
Use cases and examples
- Write founder tweets that do not trip AI detectors for style
- Produce launch emails without corporate pep-talk structure
- Rewrite bios and About pages with concrete detail
- Catch invented stats before they ship in a blog post
- Cross-agent writing constraints (Claude, Cursor, Gemini CLI, Codex)
Prerequisites
- Agent Skills–compatible host or paste-into-chat workflow
- Source facts for any claims — the skill blocks fake anecdotes but cannot invent truth
Tips
- Keep the banned-words reference on demand to avoid context bloat.
- Works as a system-level constraint in ChatGPT/Claude.ai when pasted.
- Combine with stop-slop for a second editorial pass if needed.