CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-content

Evaluate page content for usefulness, E-E-A-T, readability, thinness, and AI citation readiness, plus last-mile draft cleanup (AI-typical phrasing and invisible Unicode watermark characters). Use for content-only analysis, not full-page technical checks.

64

Quality

81%

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

75%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.

The body is a highly actionable, well-sourced reference with executable commands, explicit scoring weights, and honest scoping caveats. Its weaknesses are verbosity — duplicated E-E-A-T checklists and scattered dated Google-update notes that belong in a consolidated changelog section — and an audit workflow that is implied by checkpoints rather than laid out as an explicit sequence.

Suggestions

Consolidate time-sensitive version/date notes (QRG versions, core-update dates, AI Mode model versions) into a single 'Google update ledger' or 'Old patterns' section so stale details don't pad the mainline guidance.

Trim the inline E-E-A-T sub-bullets that duplicate eeat-framework.md, keeping only the trust-weighted summary and the pointer to the reference file.

Add a short numbered audit workflow (fetch page -> Who/How/Why test -> E-E-A-T scoring -> content metrics -> AI citation readiness -> output report) so the sequence is explicit rather than implied by section order.

DimensionReasoningScore

Conciseness

The body is mostly efficient reference material, but it includes unnecessary content: the inline E-E-A-T sub-bullets ("Contact information, physical address", "Privacy policy, terms of service") duplicate criteria already delegated to eeat-framework.md, and time-sensitive dates (March 2024, Sept 2025 QRG, 2026-05-15, Gemini 3.5 Flash 2026-05-19, changelog 2025-12-09) are scattered throughout rather than confined to an old-patterns/deprecated section, which the guidelines penalize. It is above 2 because there is no concept-teaching padding and most sections earn their tokens.

3 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands ("${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run content_humanize.py draft.md -o cleaned.md; seo_updates.py --since <yyyy-mm> --json), named output fields (invisible_removed, changes, freshness.stale), numeric thresholds (word-count floors, Flesch 60-70, keyword density 1-3%), explicit E-E-A-T weights (20/25/25/30), named DataForSEO MCP tools, and a concrete error-handling table. It matches the 5 anchor because the common cases are covered with specific commands and numbers.

5 / 5

Workflow Clarity

There is no single numbered end-to-end procedure, but sequencing and checkpoints are present: "Before scoring E-E-A-T sub-factors, every page audit should pass Google's own three-question heuristic", "Before attributing a traffic or ranking change... list the confirmed Google updates" (a validate-before-concluding loop), freshness staleness flagging, an error-handling table, and a defined output format. This is not a destructive/batch skill, so the workflow cap-3 rule does not apply; it falls short of 5 because the overall audit sequence is implied by section order rather than explicit.

4 / 5

Progressive Disclosure

References are one level deep and clearly signaled ("Read ${CLAUDE_PLUGIN_ROOT}/skills/seo/references/eeat-framework.md for full criteria and ... eeat-scoring-guide.md for score bands"), with inline script usage and a cross-reference to the seo-geo skill; no bundle directories were provided alongside SKILL.md to verify further. Minor gaps keep it at 4: the inline E-E-A-T bullet lists duplicate the referenced framework file, and the google-ai-optimization-guide.md reference is buried mid-paragraph rather than clearly signaled.

4 / 5

Total

16

/

20

Passed

Description

80%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: specific, third-person, comprehensive about what the skill evaluates, and explicitly scoped to content-only analysis. Its main weaknesses are a 'when' clause that states scope rather than concrete user triggers, and missing natural synonyms (humanize, content audit) that users would likely say.

DimensionReasoningScore

Specificity

"Evaluate page content for usefulness, E-E-A-T, readability, thinness, and AI citation readiness, plus last-mile draft cleanup (AI-typical phrasing and invisible Unicode watermark characters)" enumerates multiple specific concrete actions with comprehensive coverage of the skill's capabilities, in third-person voice. It exceeds the 4 anchor because coverage is complete rather than having minor gaps.

5 / 5

Completeness

A clear 'what' (the enumerated evaluation dimensions plus draft cleanup) is paired with an explicit "Use for content-only analysis, not full-page technical checks" clause, so the cap-3 rule for a missing use-when clause does not apply. It is not a 5 because the 'when' is a scoping statement rather than concrete trigger phrases like 'when the user mentions E-E-A-T or asks to humanize a draft'.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("E-E-A-T", "readability", "thinness", "AI citation readiness", "draft cleanup", "watermark characters"), but a few natural user phrasings are missing (e.g., "humanize this", "content audit", "SEO content"). It falls below the 5 anchor, which requires synonyms and variations of the kind users actually say.

4 / 5

Distinctiveness Conflict Risk

The "content-only analysis, not full-page technical checks" scoping and the niche combination (E-E-A-T, AI citation readiness, invisible watermark cleanup) make it mostly distinct with only minor overlap risk against closely related content/writing skills such as the cross-referenced seo-geo skill. It lacks the fully distinct trigger set of the 5 anchor.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
AgriciDaniel/claude-seo
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.