CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-quality-auditor

Use when auditing content quality, E-E-A-T, or publish readiness; runs a typed 80-item CORE-EEAT profile with evidence coverage, veto checks, and a fix plan. Not for structural tags/headers alone — use on-page-seo-checker; not for domain/citation trust — use domain-authority-auditor. 内容质量/EEAT评分

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, well-engineered audit contract with explicit validation, fail-closed behavior, and proper offloading of the 80-item detail to bundle files. Main weaknesses are redundancy in the veto/verdict rules and report-header duplication, plus reference paths that only resolve in the monorepo install rather than the shipped bundle.

Suggestions

State the veto/cap rules once (e.g., in Verdict and Handoff) and have Evidence Procedure, §2, and §3 reference that section instead of restating them, cutting the duplicated report-header markdown template from the Report section.

Make bundle-relative paths unambiguous: mark the "../../../references/" entries as monorepo-only and point standalone installs explicitly at references/auditor-runtime.md, or inline the few needed rules so no Runtime Read dangles.

Have references/item-reference.md and references/recursive-refinement.md stop chaining to second-level files outside the bundle; summarize the needed benchmark/runbook content in-file or drop the links.

DimensionReasoningScore

Conciseness

The body is mostly lean with no basic-concept padding, but veto and cap rules are restated across Evidence Procedure, Report, Verdict and Handoff, §2, and §3, and the Report section carries both a generated header block and a redundant inline markdown template. Fits anchor 3 (could be tightened) better than anchor 4, since the repetition goes beyond minor instances.

3 / 5

Actionability

Concrete executable commands are present ("python3 \"$AARON_SKILLS_ROOT/scripts/rubric-score.py\" score <run.json>", the validate-audit-artifact.py invocation, env resolution) alongside exact enums, profile names, and paths. Anchor 4 rather than 5 because several "../../../references/" paths and "audit-run.schema.json" do not resolve within the shipped standalone bundle, leaving minor execution gaps.

4 / 5

Workflow Clarity

The workflow is clearly sequenced (Required Setup → Data Sources → numbered Evidence Procedure → Report → Verdict and Handoff) with an explicit Validation Checkpoints checklist, a fail-closed NOT_SCORED path when the runtime is unavailable, and a validate→write→revalidate persistence loop. Matches anchor 5 (explicit validation steps, error-recovery loops, checklist).

5 / 5

Progressive Disclosure

SKILL.md stays an overview while the 80-item detail properly lives in references/auditor-runtime.md (1,103 lines) with a quick table in item-reference.md, and references are clearly signaled in Runtime Reads and Reference Materials. Anchor 4 rather than 5 because reference files chain onward to "../../../../references/core-eeat-benchmark.md" and "auditor-runbook.md" (second-level references), and six root-relative paths dangle in the standalone bundle.

4 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: explicit trigger clause, concrete capability statement, and explicit disambiguation against sibling auditor skills. Minor room to broaden natural-language synonyms (e.g., "content review", "quality check") and enumerate outputs more fully.

DimensionReasoningScore

Specificity

"runs a typed 80-item CORE-EEAT profile with evidence coverage, veto checks, and a fix plan" names several concrete actions with a specific artifact count, but it does not comprehensively cover what the profile assesses or the report/verdict outputs. Fits anchor 4 (several specific actions, minor gaps) rather than 3 (only 1-2 actions) or 5 (comprehensive coverage).

4 / 5

Completeness

Explicitly answers both: what ("runs a typed 80-item CORE-EEAT profile with evidence coverage, veto checks, and a fix plan") and when ("Use when auditing content quality, E-E-A-T, or publish readiness") with concrete trigger phrases. Matches anchor 5; anchor 4 would require the 'when' clause to be less explicit than it is.

5 / 5

Trigger Term Quality

"auditing content quality, E-E-A-T, or publish readiness" gives good natural keyword coverage a user would actually say. Missing common variations like "content review" or "quality check", so anchor 4 rather than 5; well above anchor 3's "missing common variations or synonyms" level.

4 / 5

Distinctiveness Conflict Risk

Negative triggers ("Not for structural tags/headers alone — use on-page-seo-checker; not for domain/citation trust — use domain-authority-auditor") carve out a clear niche and route adjacent requests elsewhere. Minimal conflict risk; matches anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 8 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

seo-geo/tune/content-quality-auditor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.