anti-spamlisted

Evergreen pass/fail gate that detects scaled-content and mass-generation signatures in AI-drafted blog posts BEFORE publishing — the patterns Google spam systems and LLMs actually penalize (templated skeletons, cluster duplication, publish bursts, programmatic footprints). Works for ANY website: point it at the draft plus the site's existing post corpus. Use on every AI-generated blog post and for cluster audits. Trigger phrases: 'anti spam', 'spam check', 'scaled content check', 'will this get penalized', 'mass-generated check'. Do NOT use for style/wording slop (use anti-slop) or fact accuracy (use accuracy-verifier) — this gate is about scale patterns, not sentences. If you maintain a site-tuned variant of this gate, use that instead when the site matches.
rdoser13/free-claude-skills · ★ 0 · AI & Automation · score 73

Install: claude install-skill rdoser13/free-claude-skills

# Anti Spam — Scaled-Content Signature Gate (any website) Google and Bing do not penalize AI-generated content for being AI-generated, and no ranking treatment exists for AI watermarks (see your own provenance/watermark policy notes, if any). What gets penalized is **scaled content abuse**: clusters of pages that share templated skeletons, near-duplicate substance, machine publish cadence, and uniform commercial footprints — regardless of who or what wrote them. Cluster-scoring systems (S-CTS class) score the CLUSTER, so a post that is individually clean can still be penalized by the company it keeps. This gate checks both levels, on any site. ## Hard prohibitions (read first) - **NEVER attempt to strip, launder, paraphrase-away, or otherwise defeat an AI watermark** (text watermark or C2PA metadata). It is model-level, carries no ranking penalty, and quality-destroying "humanizer" rewrites are the thing that IS penalized. This skill removes penalty-attracting *patterns*, never provenance marks. - **Never claim the content is human-written.** The honest position is "human-reviewed and human-owned." - This gate judges and reports; the maker rewrites. On FAIL, fix and re-run — do not ship on a promise. ## Input A draft file path (or pasted draft) + the target site + where that site's existing post corpus lives. Cluster checks need the sibling corpus; acquire it by whichever applies: - **Git-based site:** read post files from the REMOTE default branch (detached worktree of `o