
Content Quality Auditor
Audit pages and articles against the CORE-EEAT benchmark so landing copy, docs, and growth content score on intent, experience, expertise, and trust signals for SEO and GEO.
Install
npx skills add https://github.com/aaron-he-zhu/seo-geo-claude-skills --skill content-quality-auditorWhat is this skill?
- CORE-EEAT quick reference spanning 80 scored audit items (C, O, R, Exp, Ept families)
- Covers intent alignment, direct answers, FAQ coverage, schema, and citation density
- Experience signals: first-person narrative, sensory detail, limitations acknowledged
- Expertise signals: credentials, methodology rigor, reasoning transparency
- Points to full scoring criteria in core-eeat-benchmark.md for item-level grading
Adoption & trust: 4.1k installs on skills.sh; 2.1k GitHub stars; 2/3 security scanners passed (skills.sh audits).
Recommended Skills
Journey fit
Search and AI-visibility work peaks at Launch, but the same 80-item CORE-EEAT frame applies whenever you publish or refresh URL-facing content, so Launch SEO is the canonical shelf. content-quality-auditor maps directly to on-page and entity trust checks that search and answer engines reward—core SEO subphase work.
Common Questions / FAQ
Is Content Quality Auditor safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Content Quality Auditor
# CORE-EEAT Item Reference Quick reference for all 80 CORE-EEAT audit items. Full scoring criteria in [core-eeat-benchmark.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/core-eeat-benchmark.md). ## Complete Item Reference | ID | Item | ID | Item | |----|------|----|------| | C01 | Intent Alignment | Exp01 | First-Person Narrative | | C02 | Direct Answer | Exp02 | Sensory Details | | C03 | Query Coverage | Exp03 | Process Documentation | | C04 | Definition First | Exp04 | Tangible Proof | | C05 | Topic Scope | Exp05 | Usage Duration | | C06 | Audience Targeting | Exp06 | Problems Encountered | | C07 | Semantic Coherence | Exp07 | Before/After Comparison | | C08 | Use Case Mapping | Exp08 | Quantified Metrics | | C09 | FAQ Coverage | Exp09 | Repeated Testing | | C10 | Semantic Closure | Exp10 | Limitations Acknowledged | | O01 | Heading Hierarchy | Ept01 | Author Identity | | O02 | Summary Box | Ept02 | Credentials Display | | O03 | Data Tables | Ept03 | Professional Vocabulary | | O04 | List Formatting | Ept04 | Technical Depth | | O05 | Schema Markup | Ept05 | Methodology Rigor | | O06 | Section Chunking | Ept06 | Edge Case Awareness | | O07 | Visual Hierarchy | Ept07 | Historical Context | | O08 | Anchor Navigation | Ept08 | Reasoning Transparency | | O09 | Information Density | Ept09 | Cross-domain Integration | | O10 | Multimedia Structure | Ept10 | Editorial Process | | R01 | Data Precision | A01 | Backlink Profile | | R02 | Citation Density | A02 | Media Mentions | | R03 | Source Hierarchy | A03 | Industry Awards | | R04 | Evidence-Claim Mapping | A04 | Publishing Record | | R05 | Methodology Transparency | A05 | Brand Recognition | | R06 | Timestamp & Versioning | A06 | Social Proof | | R07 | Entity Precision | A07 | Knowledge Graph Presence | | R08 | Internal Link Graph | A08 | Entity Consistency | | R09 | HTML Semantics | A09 | Partnership Signals | | R10 | Content Consistency | A10 | Community Standing | | E01 | Original Data | T01 | Legal Compliance | | E02 | Novel Framework | T02 | Contact Transparency | | E03 | Primary Research | T03 | Security Standards | | E04 | Contrarian View | T04 | Disclosure Statements | | E05 | Proprietary Visuals | T05 | Editorial Policy | | E06 | Gap Filling | T06 | Correction & Update Policy | | E07 | Practical Tools | T07 | Ad Experience | | E08 | Depth Advantage | T08 | Risk Disclaimers | | E09 | Synthesis Value | T09 | Review Authenticity | | E10 | Forward Insights | T10 | Customer Support | **Note on site-level items**: Most Authority items (A01-A10) and several Trust items (T01-T03, T05, T07, T10) require site-level or organization-level data that may not be observable from a single page. When auditing a standalone page without site context, mark these as "N/A — requires site-level data" and exclude from the dimension average. ## Example Audit Report **User**: "Audit this blog post against CORE-EEAT: [paste of 'Best Project Management Tools for Remote Teams 2025']" **Output** (partial — showing one dimension to demonstrate format): ```markdown ## CORE-EEAT Audit Report ### Overview - **Content**: "Best Project Management Tools for Remote Teams 2025" - **Content Type**: Blog Post / Comparison - **Audit Date**: 2025-06-15 - **Veto Status**: No triggers ### C -- Contextual Clarity (scored dimension example) | ID | Check Item | Score | Points | Notes | |-----|--------------------|---------|--------|-------------------------------------------------------------| | C01 | Intent Alignment | Pass | 10 | Matches "best X" comparison intent; title and body aligned | | C02 | Direct Answer | Partial | 5 | Answer appears in first 300 words but no summary box | | C03 | Query Coverage | Pass | 10 | Covers "project management tools", "remote team software", "best PM tools" | | C04 | Definition First | Pass | 10 | Key terms ("PM tool", "async colla