CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-content/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-structured, information-dense audit guide with concrete commands, measurable thresholds, a defined report template, and thoughtful scope-honesty and security notes. Its weaknesses are an implicit rather than explicit audit workflow and conciseness drag from scattered date/version detail and some duplicated AI/GEO guidance.

Suggestions

Add an explicit numbered audit sequence (fetch/parse the page, run parse_html.py, score E-E-A-T and content metrics, generate the Output report) with validation checkpoints, instead of leaving the workflow implicit in section order.

Consolidate the date-stamped asides (QRG versions, gen-AI optimization doc dates, AI Mode model-version notes) into a single dated 'Sources & versions' section or a reference file to reduce conciseness drag.

De-duplicate the inline E-E-A-T sub-factor bullets against references/eeat-framework.md — keep a one-line-per-factor summary in SKILL.md and defer the detail to the reference file.

DimensionReasoningScore

Conciseness

Mostly tight tables and checklists, but heavily scattered time-sensitive version detail ('QRG: generative-AI guidance added January 2025; current version September 11, 2025', 'published 2026-05-15, last updated 2026-07-10', 'Yoast deprioritized Flesch scores in v19.3', 'Gemini 3.5 Flash became the default on 2026-05-19') and AI/GEO guidance repeated across the 'AI Content Assessment' and 'AI Search Visibility & GEO' sections — mostly efficient but could be tightened, matching the score-3 anchor rather than the 'efficient, minor instances' score-4 anchor.

3 / 5

Actionability

Provides copy-paste-ready commands ('"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run content_humanize.py draft.md -o cleaned.md', 'parse_html.py --url <url> --json', 'seo_updates.py --since <yyyy-mm> --limit 0 --json' with the --limit 0 semantics explained), concrete thresholds ('3-5 relevant internal links per 1000 words', 'Flesch 60-70', word-count floors table), a defined output template, and a per-scenario error-handling table — mostly executable guidance with minor gaps such as no end-to-end audit example.

4 / 5

Workflow Clarity

The main audit workflow (fetch page, parse, score E-E-A-T and metrics, produce the Output report) is only implicit in section order with no explicit step sequence, though conditional checkpoints exist ('If freshness.stale is true... check status.search.google.com', 'A date overlap is a hypothesis, never proof of cause') — steps present but sequence and checkpoints implicit matches the score-3 anchor.

3 / 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', 'Cross-reference the seo-geo skill'), no bundle files exist to verify, and heading structure is clear; however the inline E-E-A-T sub-factor bullet lists duplicate content stated to live in eeat-framework.md and the GEO/AI sections run long inline — good structure with minor organization gaps (score 4).

4 / 5

Total

14

/

20

Passed

Description

75%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, concrete description that names its evaluation dimensions and cleanup capability with an explicit scope boundary and exclusion. Its main weaknesses are the absence of concrete user-trigger phrases in the 'Use for' clause and a few missing natural synonyms users would actually say.

Suggestions

Add concrete trigger phrases to the 'Use for' clause, e.g. 'Use when the user asks to evaluate or score page content, check for thin or low-quality content, assess E-E-A-T, or humanize/clean up an AI-generated draft.'

Include natural synonyms users say — 'content quality', 'thin content', 'humanize', 'GEO / AI search visibility' — alongside the current terminology.

If hidden-text detection and Google update correlation are core capabilities, mention them (or fold them explicitly under the content-analysis scope); otherwise they read as undisclosed features.

DimensionReasoningScore

Specificity

Names several concrete capabilities ('usefulness, E-E-A-T, readability, thinness, and AI citation readiness' plus 'last-mile draft cleanup (AI-typical phrasing and invisible Unicode watermark characters)'), but omits capabilities covered in the body such as hidden-text detection and Google update correlation — minor gaps in coverage matching the score-4 anchor rather than the comprehensive coverage of a 5.

4 / 5

Completeness

The 'what' is clear ('Evaluate page content for... plus last-mile draft cleanup') and 'Use for content-only analysis, not full-page technical checks' provides a when-to-use clause, but it is a scope boundary rather than explicit user-trigger phrases, fitting the score-4 anchor where 'when' could be more specific.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('page content', 'readability', 'E-E-A-T', 'AI citation readiness', 'draft cleanup'), but common user phrasings like 'content quality', 'thin content', 'humanize', and 'GEO/AI search' are missing — a few natural terms short of the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The 'content-only analysis, not full-page technical checks' boundary carves a mostly distinct niche, but 'AI citation readiness' overlaps with the sibling seo-geo skill referenced in the body — minor overlap risk with a closely related skill rather than the minimal-conflict score-5 anchor.

4 / 5

Total

16

/

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

Path

skills/seo-content/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.