/content-quality-auditor

name: content-quality-auditor
description: 'Use when auditing content quality, E-E-A-T, publish readiness, or 内容质量/EEAT评分. Runs 80-item CORE-EEAT scoring with veto checks and fix plan.'
version: "9.9.5"
license: Apache-2.0
allowed-tools: WebFetch
compatibility: "Claude Code, skills.sh, ClawHub, Vercel Labs, Cursor, Windsurf, Codex CLI, Amp, Gemini CLI, Kimi Code, Qwen Code, CodeBuddy"
homepage: "https://github.com/aaron-he-zhu/seo-geo-claude-skills"
when_to_use: "Use when auditing content quality before publishing. Runs CORE-EEAT 80-item scoring with veto checks. Also when the user asks for E-E-A-T analysis or publish readiness."
argument-hint: "<URL or paste content> [keyword]"
class: auditor
metadata:
  author: aaron-he-zhu
  version: "9.9.5"
  geo-relevance: "high"
  tags:
    - seo
    - geo
    - e-e-a-t
    - core-eeat
    - content-quality
    - content-scoring
    - helpful-content
    - publish-readiness
    - 内容质量
    - コンテンツ品質
    - 콘텐츠품질
    - auditoria-eeat
  triggers:
    # EN-formal
    - "audit content quality"
    - "EEAT score"
    - "CORE-EEAT audit"
    - "content quality check"
    # EN-casual
    - "is this ready to publish"
    - "grade my article"
    - "check before publishing"
    - "is my content good enough to rank"
    # EN-question
    - "is my content ready to publish"
    - "how do I improve content quality"
    # ZH-pro
    - "内容质量审计"
    - "EEAT评分"
    - "内容评估"
    # ZH-casual
    - "文章能发吗"
    - "内容打几分"
    - "文章写得怎么样"
    # JA
    - "コンテンツ品質監査"
    - "E-E-A-T評価"
    # KO
    - "콘텐츠 품질 감사"
    - "EEAT 점수"
    # ES
    - "auditoría de calidad de contenido"
    - "puntuación EEAT"
    # PT
    - "auditoria de qualidade"

Content Quality Auditor

> Based on [CORE-EEAT Content Benchmark](https://github.com/aaron-he-zhu/core-eeat-content-benchmark). Full benchmark reference: [references/core-eeat-benchmark.md](references/core-eeat-benchmark.md)

This skill evaluates content quality across 80 standardized criteria organized in 8 dimensions. It produces a comprehensive audit report with per-item scoring, dimension and system scores, weighted totals by content type, and a prioritized action plan.

When This Must Trigger

Use this when content needs a quality check before publishing — even if the user doesn't use audit terminology:

• User asks "is this ready to publish" or "how good is this"
• User just finished writing with seo-content-writer or content-refresher
• **PostToolUse hook auto-triggers**: after content is written or substantially edited, the hook recommends this audit. When hook-triggered, skip setup questions — audit the content that was just produced.
• Auditing content quality before publishing
• Evaluating existing content for improvement opportunities
• Benchmarking content against CORE-EEAT standards
• Comparing content quality against competitors
• Assessing both GEO readiness (AI citation potential) and SEO strength (source credibility)
• Running periodic content quality checks as part of a content maintenance program
• After writing or optimizing content with seo-content-writer or geo-content-optimizer

What This Skill Does

1. **Full 80-Item Audit**: Scores every CORE-EEAT check item as Pass/Partial/Fail 2. **Dimension Scoring**: Calculates scores for all 8 dimensions (0-100 each) 3. **System Scoring**: Computes GEO Score (CORE) and SEO Score (EEAT) 4. **Weighted Totals**: Applies content-type-specific weights for final score 5. **Veto Detection**: Flags critical trust violations (T04, C01, R10) 6. **Priority Ranking**: Identifies Top 5 improvements sorted by impact 7. **Action Plan**: Generates specific, actionable improvement steps

Quick Start

Start with one of these prompts. Finish with a publish verdict and a handoff summary using the repository format in [Skill Contract](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/skill-contract.md).

Audit Content

Audit this content against CORE-EEAT: [content text or URL]

Run a content quality audit on [URL] as a [content type]

Audit with Content Type

CORE-EEAT audit for this product review: [content]

Score this how-to guide against the 80-item benchmark: [content]

Comparative Audit

Audit my content vs competitor: [your content] vs [competitor content]

Skill Contract

**Gate verdict**: **SHIP** (no critical issues, dimension scores above threshold) / **FIX** (issues found but none critical) / **BLOCK** (a critical trust issue failed — see "Critical Issue to Fix" in the report). Always state the verdict prominently at the top of the report using plain language, not item IDs.

**Expected output**: a CORE-EEAT audit report, a publish-readiness verdict, and a short handoff summary ready for `memory/audits/content/`.

• **Reads**: the target content, content type, supporting evidence, and any prior decisions from [CLAUDE.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/CLAUDE.md) and the shared [State Model](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/state-model.md) when available.
• **Writes**: a user-facing audit report plus a reusable summary that can be stored under `memory/audits/content/`.
• **Promotes**: veto items and publish blockers to `memory/hot-cache.md` (auto-saved, no user confirmation needed). Top improvement priorities to `memory/open-loops.md`.
• **Next handoff**: use the `Next Best Skill` below once the verdict is clear.

Data Sources

> See [CONNECTORS.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/CONNECTORS.md) for tool category placeholders.

**With ~~web crawler + ~~SEO tool connected:** Automatically fetch page content, extract HTML structure, check schema markup, verify internal/external links, and pull competitor content for comparison.

**With manual data only:** Ask the user to provide: 1. Content text, URL, or file path 2. Content type (if not auto-detectable): Product Review, How-to Gui