Agent skill · Code Review & Quality

content-quality-auditor

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.

ViryaZhenggithub.com/ViryaZhengGitHub ↗
claude-coderead-onlyMIT
Install
npx skills add ViryaZheng/recomby-geo --skill content-quality-auditor --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 31 KB
Bundled scripts: none
Version: 9.9.5
Declared author: aaron-he-zhu
Allowed tools: WebFetch
Requires: Claude Code, skills.sh, ClawHub, Vercel Labs, Cursor, Windsurf, Codex CLI, Amp, Gemini CLI, Kimi Code, Qwen Code…
Path: plugins/recomby-geo/skills/content-quality-auditor/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 510 · +3 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Audits content quality against an 80-item CORE-EEAT benchmark, awarding Pass/Partial/Fail per item, and generates dimension scores (8 dimensions, 0-100 each), system scores (GEO/SEO), a prioritized Action Plan, and a Top 5 improvements list.

How it works

It is designed to be used when auditing content quality before publishing or evaluating existing content. It:

  • Performs a full 80-item audit with per-item scoring (Pass = 10, Partial = 5, Fail = 0).
  • Calculates Dimension Scores for 8 dimensions (0-100 each).
  • Computes System Scores (GEO Score and SEO Score).
  • Applies content-type-specific weights to produce weighted totals.
  • Detects vetoes for critical trust issues (T04, C01, R10) and flags them.
  • Produces a Top 5 improvements ranking and an actionable improvement plan.
  • Exposes a Quick Start with prompts for auditing content or comparing with competitors.

When to use it

Use when content needs a quality check before publishing or when asked for E-E-A-T analysis or publish readiness. It is triggered by prompts such as "Audit Content" or related phrases and can be auto-triggered after content is written or edited as part of a hook.

What it can touch

The skill integrates with tools listed in the frontmatter for automated data collection (e.g., content from URLs or text inputs) and then outputs a CORE-EEAT audit report, a publish-readiness verdict, and a handoff summary. It also promotes veto items to memory caches and top improvements to memory/open-loops. The output includes a structured artifact ready for storage under memory/audits/content/.

Caveats

The skill enforces a gate verdict (SHIP / FIX / BLOCK) and must report any veto items immediately. It relies on access to target content and benchmark references; missing data may lead to Insufficient Data flags. The cap and veto handling rules, including how scores are adjusted to a maximum 60 in cap scenarios, are described in the included fail-cap framework references (not reproduced here).

From the SKILL.md

# 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 cit

What's inside
Steps it walks through
  1. When This Must Trigger
  2. What This Skill Does
  3. Quick Start
  4. Audit Content
  5. Audit with Content Type
  6. Comparative Audit
  7. Skill Contract
  8. Data Sources
  9. Decision Gates
  10. Instructions
  11. Step 1: Preparation
  12. Step 2: CORE Audit (40 items)
  13. Step 3: EEAT Audit (40 items)
  14. §1 · Handoff Schema (authoritative)
Ships with 4 files
  • references/cite-domain-rating.md
  • references/core-eeat-benchmark.md
  • references/fail-cap-worked-examples.md
  • references/item-reference.md
More from recomby-geo
All skills →
About this skill
What does the content-quality-auditor skill do?

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.

How do I install it?

Run `npx skills add ViryaZheng/recomby-geo --skill content-quality-auditor --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 ViryaZheng/recomby-geo, a repository with 510 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.

Keep going