Show HN: Anti-AI-slop: a 4 staged skill to detect and remove any AI writing slop
anti-ai-slop A skill for Claude Code, Codex, and other coding agents that removes AI-writing tells from a draft and then checks the result before handing it back. What it catches Sentence patterns Negative parallelism. It's a trust problem." Throat-clearing openers.
- ▪anti-ai-slop A skill for Claude Code, Codex, and other coding agents that removes AI-writing tells from a draft and then checks the result before handing it back.
- ▪What it catches Sentence patterns Negative parallelism.
- ▪It's a trust problem." Throat-clearing openers.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,752 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/misbahsy/anti-ai-slop |
| Publication time | Mon, 14 Sep 2026 06:11:01 +0000 |
| Retrieval time | 2026-09-14T06:16:51.448Z |
| Last seen | 2026-09-14T06:16:51.448Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | R5FioXeljTwZ · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
anti-ai-slop A skill for Claude Code, Codex, and other coding agents that removes AI-writing tells from a draft and then checks the result before handing it back. What it catches Sentence patterns Negative parallelism. "It isn't a pricing problem. It's a trust problem." Throat-clearing openers. "Here's the thing," "Let me be honest" Faux-insight setups. "What most teams get wrong," "The part nobody mentions" Rhetorical setups. "Think about it:" "Sound familiar?" Colon reveals. "The clever part: it retries on its own." Trailing -ing analysis. "...adds dark mode, underscoring its focus on users" Importance puffery. "stands as a testament to," "cannot be overstated" Telling the reader what to think. "As you can see," "The key takeaway here is" Fake-strong verbs.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.