seo-sxo

Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

62%

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 well-structured, actionable pipeline with strong workflow clarity and validation checkpoints, but it loses points for conciseness redundancy, broken script references that hurt executability, and a bundle that does not match the referenced script paths. Addressing the missing scripts would most improve the score.

Suggestions

Add the missing `scripts/render_page.py` and `scripts/parse_html.py` to the bundle (or replace the invocations with inline, self-contained instructions) so the headline commands are actually runnable.

Trim the 'Core Insight' intro section, which restates the description's premise about wrong page type causing ranking failure, to reduce redundancy.

Make script-fallback behavior explicit: note what to do if render_page.py cannot fetch the page (e.g., raw fetch + warning) rather than only the abstract error-handling row.

Dimension	Reasoning	Score
Conciseness	Mostly efficient procedural content without explaining basics Claude knows, but the intro and 'Core Insight' section restate the premise already covered by the description, and some prose could be tightened.	2 / 3
Actionability	Offers concrete scoring tables, a user-story template, and an output-format spec, but the headline executable commands `scripts/render_page.py --mode auto` and `scripts/parse_html.py` reference files absent from the bundle, so they are not copy-paste runnable.	2 / 3
Workflow Clarity	A clear seven-step pipeline is sequenced with explicit checkpoints — keyword validation before proceeding, DataForSEO cost confirmation before API calls, an error-handling table, and a pre-delivery quality checklist with feedback loops.	3 / 3
Progressive Disclosure	The four reference files are well-signaled and one level deep (all exist: page-type-taxonomy, user-story-framework, persona-scoring, wireframe-templates), but the body also directs Claude to `scripts/render_page.py` and `scripts/parse_html.py` which are not present in the bundle.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 third-person, concrete, and complete, naming specific capabilities and giving an explicit trigger list. It cleanly answers both what the skill does and when Claude should invoke it. No changes needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives' plus 'analyzing what Google rewards for each keyword' — matching the multi-action anchor.	3 / 3
Completeness	Explicitly states both what it does (SERP analysis, user-story derivation, persona scoring, ranking-failure diagnosis) and when to use it via an explicit 'Use when user says...' clause, satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Provides broad natural-phrase coverage via 'Use when user says "SXO", "search experience", "page page-type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe"' — terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear SXO niche with distinctive triggers unlikely to fire for general SEO or content skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: AgriciDaniel/claude-seo
Path: skills/seo-sxo/SKILL.md
Commit: 09d37c7

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.