CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-page

Analyze one supplied URL across on-page, content, technical metadata, schema, images, and performance. Use only for a single-page review.

Quality

78%

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-page/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a strong, highly operational skill body: a deterministic script front-loads all mechanical checks, the division of labor between script facts and agent judgment is stated precisely, and error handling and untrusted-data guidance are explicit. The only meaningful weaknesses are the undefined methodology behind the 0-100 score card and a few rationale passages that could be trimmed.

DimensionReasoningScore

Conciseness

The body is instruction-first and dense with copy-paste commands, finding-id tables, and interpretation rules, with no explanation of concepts Claude already knows. A few justification passages (the templated-metadata rationale, the lazy-loader note) run longer than needed, keeping it below the lean anchor 5 but well above the mostly-efficient anchor 3.

4 / 5

Actionability

Fully executable commands cover live URLs, saved HTML, JS-rendered pages, metadata template checks, and image format probing, backed by a complete output template and an error-action table. The one notable gap is that the "Overall Score: XX/100" card format is specified with no methodology for computing the sub-scores, which fits "concrete commands with minor gaps" rather than anchor 5.

4 / 5

Workflow Clarity

The sequence is explicit and ordered — run the deterministic script first, take every length/count/id from the JSON, apply judgment with stated rules, then emit the specified output — with genuine error-recovery loops (the Error Handling table and the {"error": ...} routing) and a 47-item checklist. This is a read-only analysis, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

Sections are well organized with clearly signaled, one-level-deep pointers (quality-gates.md, seo-images) and appropriately inlined working material such as the finding-id table. It does not reach 5 because the referenced files cannot be verified against a bundle (no references/ or scripts/ directories exist here) and the long body still carries detail (e.g., full threshold and format rules) that could live in those references.

4 / 5

Total

17

/

20

Passed

Description

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

The description communicates a clear, well-scoped capability with concrete analysis dimensions and an explicit single-page boundary, keeping conflict risk low. Its main weakness is trigger-term coverage: the word "SEO" — the term users are most likely to say — never appears, and the 'when' guidance is a restriction rather than a positive trigger phrase.

Suggestions

Add the primary natural trigger term "SEO" (e.g., "Use for a single-page SEO audit or review when the user supplies one URL") so requests like "audit this page's SEO" match directly.

Replace or augment the boundary-only "Use only for a single-page review" with a positive trigger clause naming the scenarios that call for this skill (page review, SEO audit, on-page check of one URL).

Briefly state the deliverable (e.g., a scored page review with prioritized issues and recommendations) to close the specificity gap.

DimensionReasoningScore

Specificity

"Analyze one supplied URL across on-page, content, technical metadata, schema, images, and performance" enumerates six concrete analysis areas with comprehensive scope. It falls short of 5 because it relies on a single verb and never states the deliverable (a scored review), and is above 3 because coverage is specific rather than 1-2 generic actions.

4 / 5

Completeness

The 'what' is clear (analyze a URL across six named dimensions) and an explicit use clause exists ("Use only for a single-page review"), so it is not capped at 3. It is not 5 because the 'when' is only a boundary restriction with no positive trigger phrase like "Use when the user asks for an SEO review of a page".

4 / 5

Trigger Term Quality

Relevant keywords like "on-page", "URL", "schema", and "single-page review" are present, but the most natural term a user would say — "SEO" (and "audit") — is entirely absent. This matches "some relevant keywords but missing common variations or synonyms" rather than 4, where only a few natural terms would be missing.

3 / 5

Distinctiveness Conflict Risk

The enumerated dimensions plus the explicit "Use only for a single-page review" scope carve a mostly distinct single-page-analysis niche with minor overlap risk against general web-performance or accessibility audit skills. Not 5 because broad terms like "performance" and "images" still invite some overlap; not 3 because the boundary and dimension list make it clearly more specific than similar skills.

4 / 5

Total

15

/

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-page/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.