CtrlK
BlogDocsLog inGet started
Tessl Logo

seo

Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability, indexability, Core Web Vitals with INP), schema markup, content quality (E-E-A-T), image optimization, sitemap analysis, and GEO for AI Overviews/ChatGPT/Perplexity. Industry detection for SaaS, e-commerce, local, publishers, agencies. Triggers on: SEO, audit, schema, Core Web Vitals, sitemap, E-E-A-T, AI Overviews, GEO, technical SEO, content quality, page speed. Use this hub only when the SEO domain is clear and the requested workflow is not; otherwise use the exact retained leaf or command.

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An operationally dense hub skill with concrete commands, a well-sequenced conditional audit workflow, and genuinely on-demand reference files that all exist. Its main cost is length — footer policy, synthesis methodology, and duplicated sub-skill/subagent rosters inflate the body — and its runtime invocations cannot be verified against the bundle because no scripts/ directory ships with it.

Suggestions

Cut the Community Footer section to a one-line rule (or move the show/skip policy to a reference file); the ~70 lines of per-command display policy plus the decorative box are the largest source of avoidable tokens.

Reduce the Synthesis Methodology section to a short pointer to references/thinking-framework.md, since the body already duplicates that file's phase structure and per-recommendation requirements.

Merge the Sub-Skills and Subagents enumerations into a single table (name, purpose, spawn condition) — the two lists restate the same roster twice — and cite references/backlink-quality.md and references/free-backlink-sources.md somewhere so no bundled file is orphaned.

DimensionReasoningScore

Conciseness

The body is mostly operational, but several sections are padded relative to their value: the ~70-line Community Footer policy (show/skip lists for 26 commands plus a decorative box), an inline Synthesis Methodology that duplicates references/thinking-framework.md, and two overlapping roster enumerations (Sub-Skills and Subagents) restating the same capabilities. Not 4: these are several unnecessary sections that could be trimmed or moved to references, not just minor over-explanation.

3 / 5

Actionability

Guidance is concrete and command-shaped throughout: '"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run <script.py>', 'doctor --json', 'run google_auth.py --check', 'run seo_updates.py --kind spam --json', plus an explicit invocation contract and argument-hint. Not 5: there are no worked examples or sample outputs, and every runtime command depends on a scripts/ launcher that is not present in this bundle, so nothing is copy-paste verifiable as shipped.

4 / 5

Workflow Clarity

The audit orchestration is a clear 16-step numbered sequence with explicit conditional gates (auth '--check' scripts, drift baseline lookup, business-type detection) and an error-handling table covering unrecognized commands, unreachable URLs, and sub-skill failure with recovery actions. Not 5: recovery guidance lives in a fallback table rather than integrated fix-and-revalidate loops, and steps like 'Synthesize via the 10-principle framework' and 'generate unified report' defer their mechanics without inline checkpoints.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep ('Load these on-demand as needed (do NOT load all at startup)'), and all 15 body-cited files in references/ exist with substantive content. Not 5: backlink-quality.md and free-backlink-sources.md are orphaned (never cited from the body), and every runtime command targets scripts/claude-seo plus named .py scripts that are absent from the bundle's file listing.

4 / 5

Total

15

/

20

Passed

Description

92%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 description: concrete capability enumeration, explicit trigger terms, and routing guidance that disambiguates hub versus leaf usage in third-person voice. The only weakness is trigger-term breadth — several natural SEO phrases (backlinks, keyword research, ranking) are absent.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Full site audits, single-page analysis, technical SEO (crawlability, indexability, Core Web Vitals with INP), schema markup, content quality (E-E-A-T), image optimization, sitemap analysis, and GEO for AI Overviews/ChatGPT/Perplexity' — covering the SEO domain comprehensively. Not 4: there are no noticeable coverage gaps; every clause names a concrete capability rather than a generic category.

5 / 5

Completeness

Both questions are explicitly answered: the 'what' via the enumerated capabilities and the 'when' via the explicit 'Triggers on:' clause plus hub-routing guidance ('Use this hub only when the SEO domain is clear and the requested workflow is not'). Not 4: the when-clause is explicit with concrete trigger phrases, not merely present or imprecise.

5 / 5

Trigger Term Quality

'Triggers on: SEO, audit, schema, Core Web Vitals, sitemap, E-E-A-T, AI Overviews, GEO, technical SEO, content quality, page speed' gives good natural keyword coverage a user would actually say. Not 5: common variations and synonyms are missing — e.g. 'backlinks', 'keyword research', 'rank tracking', 'search engine ranking'.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear SEO niche with distinct triggers, and the hub-vs-leaf routing instruction further reduces the chance of triggering for the wrong skill. Not 4: no meaningful overlap risk with closely related skills is identifiable from the text.

5 / 5

Total

19

/

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.