CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-sxo

Diagnose search-experience and intent mismatches using SERP page types, user stories, and persona scoring. Use when ranking problems appear intent- or layout-driven.

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

Quality

Content

85%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 instruction-style skill body: a clearly sequenced 7-step pipeline with validation checkpoints, error-recovery fallbacks, a quality checklist, and clean progressive disclosure to four real reference files. The only weaknesses are minor — a slightly trimmable conceptual intro and a couple of loosely specified estimation steps (word-count estimates, authority tiers).

DimensionReasoningScore

Conciseness

The body is dense and efficient — tables for mismatch severity, gap dimensions, error handling, and cross-skill handoffs instead of prose, with no padding of concepts Claude already knows. The two short intro sections ('SXO bridges the gap...', 'Core Insight') could be trimmed slightly, matching 'efficient; minor instances of over-explanation' rather than the fully lean level 5.

4 / 5

Actionability

Guidance is mostly executable: exact commands ("${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run render_page.py <URL> --mode auto, parse_html.py --url <URL> --json), named tools (WebSearch, serp_organic_live_advanced), a point-weighted scoring rubric, a user-story template, and a complete output format. Minor gaps remain — 'word count estimate (from snippet length and page structure)' and the domain-authority tier determination are underspecified — so it falls just short of fully copy-paste-ready level 5.

4 / 5

Workflow Clarity

The 7-step execution pipeline is clearly sequenced with explicit validation steps ('Validate keyword is non-empty before proceeding', cost estimate confirmation before DataForSEO calls), feedback loops for error recovery (a full error-handling table with fallbacks, e.g. WebSearch fallback when DataForSEO exceeds threshold), and a pre-delivery quality checklist — exactly the level-5 anchor.

5 / 5

Progressive Disclosure

The body is a well-organized overview that delegates detail to four clearly signaled, one-level-deep references (page-type-taxonomy.md, user-story-framework.md, persona-scoring.md, wireframe-templates.md), all of which exist in the bundle and do not nest further. Content is appropriately split and navigation is easy, matching the level-5 anchor.

5 / 5

Total

18

/

20

Passed

Description

62%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 is well-formed with a clear what and an explicit 'Use when' clause in third person, but it undersells the skill's concrete capabilities and misses the most natural trigger vocabulary. It sits comfortably above mediocre descriptions but below the exemplary ones in the rubric.

Suggestions

Enumerate more concrete capabilities in the description, e.g. 'run SERP backwards analysis, score page-type mismatches, derive user stories and personas, and generate IST/SOLL wireframes' to lift specificity from naming 2-3 methods to listing several specific actions.

Add natural trigger terms users would actually say, such as 'SEO', 'not ranking', 'search intent', or 'keyword', so the skill triggers on common phrasings rather than only the jargon-heavy 'SERP' and 'ranking problems'.

Expand the when-clause with multiple concrete trigger phrases (e.g. 'Use when a page ranks poorly despite technical health, when the user mentions search intent, SERP layout, or page-type mismatches') to reach explicit what-and-when completeness with concrete triggers.

DimensionReasoningScore

Specificity

The description names the domain and 2-3 method components ("Diagnose search-experience and intent mismatches using SERP page types, user stories, and persona scoring") but omits several capabilities the skill actually has (SERP backwards analysis, gap scoring, wireframe generation). It lists a couple of concrete actions without comprehensive coverage, matching the level-3 anchor rather than level 4.

3 / 5

Completeness

Both parts are explicit: a clear 'what' ("Diagnose search-experience and intent mismatches using SERP page types, user stories, and persona scoring") and an explicit when-clause ("Use when ranking problems appear intent- or layout-driven"). It falls short of level 5 because the trigger is a single condition rather than multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords like "ranking problems", "SERP", "intent", and "layout" are present, but common natural phrasings users would actually say ("SEO", "not ranking", "keyword", "search intent") are missing. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of level 4.

3 / 5

Distinctiveness Conflict Risk

The niche terminology (SERP page types, persona scoring, intent/layout-driven ranking problems) gives it a distinct profile with minimal conflict risk, though it could overlap with closely related SEO audit skills in the same plugin suite. Best fit is 'mostly distinct; minor overlap risk'.

4 / 5

Total

14

/

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