by FeedHive
120 patterns that make writing read like AI slop, with an agent skill for Claude Code and Codex.
# Add to your Claude Code skills
git clone https://github.com/FeedHive/ai-slop-detectorGuides for using ai agents skills like ai-slop-detector.
See how ai-slop-detector compares with popular alternatives.
ai-slop-detector is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by FeedHive. 120 patterns that make writing read like AI slop, with an agent skill for Claude Code and Codex. It has 57 GitHub stars.
ai-slop-detector's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/FeedHive/ai-slop-detector" and add it to your Claude Code skills directory (see the Installation section above).
ai-slop-detector is primarily written in JavaScript. It is open-source under FeedHive on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh ai-slop-detector against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
See comparison
120 patterns that make writing read like AI slop, in 9 categories. Each pattern has a short explanation, a bad example and a plain rewrite.
Give the list to your AI before it writes, or check a draft against it afterwards. To check a draft in your browser, paste it into the free AI Slop Detector.
The list doesn't try to tell whether a person or an AI wrote a text. People write these patterns too, and a model can be told to avoid them. A single pattern is normal in human writing; several in one paragraph is what makes a text read as slop.
Claude Code, Codex and other agents. Give the agent this repository and ask it to install the skill:
Install the AI Slop Detector skill from https://github.com/FeedHive/ai-slop-detector
Or install it yourself for Claude Code:
git clone https://github.com/FeedHive/ai-slop-detector.git
cp -r ai-slop-detector/skills/ai-slop-detector ~/.claude/skills/
ChatGPT, Claude and other chat apps. Paste this README into the chat and ask it to avoid every pattern in what it writes next. To check a draft, paste the README and the draft and ask for every pattern it finds, with the line it found it in.
Your own tools. patterns.json has the full list as structured data. Edit it and run node scripts/build.mjs to regenerate this README and the skill.
| Category | Patterns |
|---|---|
| Vocabulary | 20 |
| Stock phrases | 15 |
| Sentence patterns | 22 |
| Structure and rhythm | 12 |
| Imagery and metaphor | 6 |
| Substance | 12 |
| Formatting and punctuation | 10 |
| Chatbot residue | 8 |
| Social media and LinkedIn | 15 |
Words that show up far more often in AI output than in human writing. One is a coincidence; three in a paragraph is a pattern.
delve, dive into, deep dive, unpack, explore (for "discuss").
Bad: "Let's delve into the data."
Better: "Here is what the data shows."
tapestry, landscape, realm, sphere, ecosystem, fabric (used abstractly).
Bad: "the ever-evolving landscape of marketing."
Better: "marketing in 2026" or name the actual change.
testament to, beacon of, embodiment of, hallmark of.
Bad: "The launch is a testament to the team's dedication."
Better: "The team shipped it in six weeks."
pivotal, crucial, vital, paramount, critical (as decoration).
Bad: "plays a pivotal role in growth."
Better: "drives 40% of signups."
showcase, highlight, underscore, emphasize, spotlight (as commentary verbs).
Bad: "The results underscore the importance of testing."
Better: "Testing caught three bugs before launch."
foster, cultivate, nurture (applied to abstract things).
Bad: "fostering a culture of innovation."
Better: Say what the team actually does.
leverage, utilize, harness, capitalize on.
Bad: "Leverage AI to streamline your workflow."
Better: "Use AI to draft the weekly report."
elevate, enhance, empower, supercharge, unlock, amplify.
Bad: "Elevate your content strategy."
Better: Name the result: "Post three times a week without writing on weekends."
seamless, robust, cutting-edge, state-of-the-art, best-in-class, world-class.
Bad: "a seamless, robust solution."
Better: "it syncs in under a second and hasn't gone down this year."
intricate, multifaceted, nuanced, complex (as filler).
Bad: "the intricate interplay of factors."
Better: Name two of the factors.
meticulous, meticulously, painstakingly, carefully crafted.
Bad: "meticulously crafted templates."
Better: "templates tested on 200 posts."
vibrant, rich, bustling, thriving, dynamic.
Bad: "a vibrant community of creators."
Better: "4,000 creators who post weekly."
journey, embark, navigate, voyage, path (for ordinary processes).
Bad: "embark on your SEO journey."
Better: "start with your top ten pages."
game changer, revolutionary, groundbreaking, transformative, paradigm shift.
Bad: "This feature is a game changer."
Better: Say what changes and for whom.
Additionally, Furthermore, Moreover, Notably, Importantly (opening sentences).
Bad: "Additionally, the tool supports exports."
Better: "It also exports to CSV."
truly, incredibly, deeply, profoundly, remarkably, fundamentally.
Bad: "a truly remarkable result."
Better: Give the number that makes it remarkable.
quietly, silently, subtly (adding drama to plain events).
Bad: "Costs quietly crept up."
Better: "Costs rose 12% in March."
align with, resonate with, speak to, in line with.
Bad: "content that resonates with your audience."
Better: "posts your audience replies to."
key insight, key takeaway, key factor, key role.
Bad: "The key takeaway is consistency."
Better: "Post on the same days every week."
in today's fast-paced world, in the digital age, in an era of, now more than ever.
Bad: "In today's fast-paced digital world, content is king."
Better: Cut it and start with the point.
Ready-made phrases that fill space without adding meaning.
it's worth noting, it's important to note, it should be noted.
Bad: "It's worth noting that the API is rate limited."
Better: "The API allows 100 calls a minute."
at its core, at the end of the day, when all is said and done, ultimately.
Bad: "At its core, marketing is about people."
Better: Delete, or say something specific about people.
when it comes to, in terms of, with regard to, in the world of.
Bad: "When it comes to scheduling, timing matters."
Better: "Posts at 9am get more reach than posts at 3pm."
let's dive in, let's get started, buckle up, without further ado.
Bad: "Ready? Let's dive in!"
Better: Start with the first point.
plays a role in, contributes to, is a factor in.
Bad: "Hashtags play a role in reach."
Better: "Posts with 3 to 5 hashtags reached more people in our test."
stands as, serves as, functions as, acts as (instead of "is").
Bad: "The dashboard serves as a central hub."
Better: "The dashboard shows every scheduled post."
navigate the complexities of, the ins and outs of, the nuances of.
Bad: "helping you navigate the complexities of SEO."
Better: "explains how Google picks which page to rank."
Whether you're a beginner or a pro, from startups to enterprises.
Bad: "Whether you're a solo creator or a global brand, ..."
Better: Say who it is actually for.
look no further, you've come to the right place, this is your ultimate guide.
Bad: "Looking for a scheduler? Look no further."
Better: "FeedHive schedules posts to 10 platforms."
unlock the power of, harness the potential of, take it to the next level.
Bad: "Unlock the full potential of your content."
Better: Say the specific gain.
here's the thing, here's the deal, let me be clear, I'll be honest, I'll be straight with you.
Bad: "Here's the thing: most people quit."
Better: "Most people quit in month two."
the truth is, the reality is, the uncomfortable truth, the hard truth.
Bad: "The hard truth is that SEO takes time."
Better: "SEO takes about six months to show results."
I hope this helps, happy writing, feel free to reach out, let me know if you have any questions.
Bad: A post or article ending with "Hope this helps!"
Better: End on the last useful point.
In conclusion, In summary, To sum up, Overall, All in all.
Bad: "In conclusion, consistency is key."
Better: End on the last concrete point; the reader was just there.
the future is bright, the possibilities are endless, only time will tell, the sky's the limit.
Bad: "With A