ai-content-audit
Audit a content library, docs site, or blog for AI-generated filler that's eroding trust and search performance — and triage what to fix, rewrite, or delete. Use when asked to find slop in a content library, audit AI-written content quality, explain why content engagement or rankings dropped after scaling with AI, or set a quality bar for AI-assisted publishing. Produces an audited inventory with per-piece verdicts, the detection signals used, a triage plan, and a publishing quality gate that prevents recurrence. For a single article's AI-citability use aeo-optimizer; for the strategy itself u
npx skills add mohitagw15856/pm-claude-skills --skill ai-content-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# AI Content Audit Skill Teams that scaled content with AI are discovering the bill: libraries full of fluent, structurally identical, information-free pieces that readers bounce off, search engines quietly demote, and — worst — that erode the trust the *good* content earned. This skill audits the library for slop with named signals, triages it, and installs the gate that stops the refill. ## What This Skill Produces - An **audited inventory** with per-piece verdicts: keep / enrich / rewrite / delete-and-redirect - The **detection signals** found, quoted — so verdicts are checkable, not vibes - A **triage plan** sequenced by traffic and trust impact - A **publishing quality gate** for AI-assisted content going forward ## Required Inputs Ask for (if not already provided): - **The corpus** — pieces or URLs to audit (or a sample; state the sampling), with publish dates - **Performance data if available** — traffic, engagement, rankings over time (the audit works without it, but verdicts get sharper) - **What the content is *for*** — SEO, docs, thought leadership, support deflection (the quality bar differs) - **Production context** — when AI-assisted publishing started, at what volume
- What This Skill Produces
- Required Inputs
- Detection Method
- The Quality Gate (prevention)
- Output Format
- AI Content Audit: [property] — [n] pieces ([sampling noted])
- Quality Checks
- Anti-Patterns
What does the ai-content-audit skill do?
Audit a content library, docs site, or blog for AI-generated filler that's eroding trust and search performance — and triage what to fix, rewrite, or delete. Use when asked to find slop in a content library, audit AI-written content quality, explain why content engagement or rankings dropped after scaling with AI, or set a quality bar for AI-assisted publishing. Produces an audited inventory with per-piece verdicts, the detection signals used, a triage plan, and a publishing quality gate that prevents recurrence. For a single article's AI-citability use aeo-optimizer; for the strategy itself u
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill ai-content-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.