CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

76%

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.

The SKILL.md body is a well-structured operational pipeline: concrete commands, quantified scoring rubrics, explicit error fallbacks, validation checkpoints, and a pre-delivery checklist, with all deep methodology correctly pushed to four real, one-level-deep reference files. The only meaningful gaps are minor verbosity in the framing sections and a couple of loosely anchored judgment calls (word-count estimation) plus reliance on plugin scripts not bundled here.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with almost no padding — no explanations of what SEO or SERPs are, and each section carries task-specific rules (mismatch severity table, 7-dimension scoring table, error handling table). Minor over-explanation remains, e.g. the 'Core Insight' paragraph and the 'SXO Score vs SEO Health Score' section partly restate the opening framing and could be trimmed to one place. This is 'efficient with minor instances that could be trimmed' (4), not the every-token-earns-its-place level (5).

4 / 5

Actionability

Guidance is concrete and executable: exact plugin commands ('render_page.py <URL> --mode auto'), explicit keyword-extraction rule, quantified scoring rubrics (0-15 per dimension, 25 pts per persona dimension), a concrete placeholder example ('Add pricing CTA with annual savings badge below hero, linking to /pricing#enterprise'), and a full output template. It falls short of 5 only in small spots: a few steps rely on judgment without anchors ('word count estimate (from snippet length)'), and the scripts referenced via ${CLAUDE_PLUGIN_ROOT} are not part of this bundle, so their behavior is assumed.

4 / 5

Workflow Clarity

The 7-step pipeline is clearly sequenced with explicit validation checkpoints: 'Validate keyword is non-empty before proceeding', cost confirmation before DataForSEO calls, an Error Handling table mapping each failure to a fallback action (e.g. 'DataForSEO cost exceeds threshold → Fall back to WebSearch, notify user'), conditional gating ('Only execute when /seo sxo wireframe is invoked'), and a pre-delivery Quality Checklist. This matches the top anchor: clear sequence, explicit validation, feedback loops, and a checklist.

5 / 5

Progressive Disclosure

The body is an overview that delegates each deep methodology to a one-level-deep reference, clearly signaled at the point of need ('Read references/page-type-taxonomy.md for classification rules', 'Read references/persona-scoring.md for methodology'), and all four referenced files (page-type-taxonomy.md, user-story-framework.md, persona-scoring.md, wireframe-templates.md) exist in the bundle with no further nesting. This matches the top anchor: clear overview with well-signaled, one-level-deep references.

5 / 5

Total

18

/

20

Passed

Description

58%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 follows best practice: third-person voice, explicit 'Use when...' trigger, and a concrete method list. Its weaknesses are coverage and trigger breadth — it advertises only the diagnostic core of the skill and leans on the generic phrase 'ranking problems', which risks overlap with sibling SEO skills and misses natural terms like 'SEO' or 'keyword intent'.

Suggestions

Enumerate the main capabilities to raise specificity and completeness, e.g. 'Analyze SERP page-type consensus, derive user stories and personas, score page-vs-SERP gaps, and generate IST/SOLL wireframes.'

Broaden trigger terms with natural user phrasing: 'Use when a page won't rank despite good SEO health, when search results favor a different page type, or when the user asks about keyword intent, SERP layout, or search experience.'

Add a distinguishing clause that separates this from generic SEO audits, e.g. 'For technical SEO audits, use /seo technical instead' or explicit mention that this targets intent/layout mismatches rather than technical health.

DimensionReasoningScore

Specificity

The description names the domain and one main action — 'Diagnose search-experience and intent mismatches' — with its methods ('using SERP page types, user stories, and persona scoring'), but it is not comprehensive: capabilities like SERP backwards analysis, gap scoring, wireframe generation, and persona-only mode are omitted. It names the domain and 1-2 concrete actions without full coverage, matching the score-3 anchor rather than 4, which requires several specific listed actions with only minor gaps.

3 / 5

Completeness

It explicitly answers both parts: what ('Diagnose search-experience and intent mismatches using SERP page types, user stories, and persona scoring') and when ('Use when ranking problems appear intent- or layout-driven'). The 'when' clause is present and reasonably specific but single-clause, and the 'what' omits several sub-capabilities — matching score 4 ('both present; when could be more explicit or specific') rather than 5, which demands comprehensive what-and-when coverage with concrete trigger phrases.

4 / 5

Trigger Term Quality

Trigger phrases include 'ranking problems', 'intent- or layout-driven', 'SERP', and 'search-experience', but common natural variations users would actually say — 'SEO', 'why isn't my page ranking', 'keyword intent', 'search results' — are missing. This lands on the score-3 anchor ('some relevant keywords but missing common variations or synonyms') rather than 4, which requires only a few missing natural terms.

3 / 5

Distinctiveness Conflict Risk

The description is somewhat specific ('SERP page types, user stories, persona scoring' is a niche), but the trigger 'ranking problems' is the universal SEO complaint and would activate any sibling SEO skill (this plugin has /seo technical, /seo content, /seo page, etc.), creating real overlap risk. It fits score 3 ('somewhat specific but could still overlap with similar skills') better than 4, whose minimal-overlap example has a clearly distinct file-format niche.

3 / 5

Total

13

/

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.