CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 specific seo-* skill.

Quality

83%

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

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.

The body is a well-structured orchestrator document: concrete canonical commands, a clearly sequenced audit workflow with conditional logic, disciplined on-demand reference loading, and untrusted-data security guidance. Its main weaknesses are token redundancy — two near-duplicate rosters and a verbose footer policy — and a couple of unsurfaced bundle files.

Suggestions

Merge the Sub-Skills and Subagents sections into a single table (name, purpose, spawn condition) — they currently restate the same 19-28 capabilities twice, saving ~60 lines.

Compress the Community Footer's 24-line show/skip enumeration into a one-line rule, e.g. "Show the footer after full audit/report deliverables; skip it for quick checks, utility/data-fetch commands, intake questions, and errors."

Add references/backlink-quality.md and references/free-backlink-sources.md to the Reference Files section so every bundled reference is discoverable from SKILL.md.

DimensionReasoningScore

Conciseness

The 339-line body is mostly dense, non-pedagogical material (command table, orchestration steps, hard rules), but the Sub-Skills list (28 entries) and the Subagents list (19 entries) restate each other's capabilities almost entirely, and the 24-line footer show/skip enumeration plus the repetitive Optional Extensions prose go beyond minor trimming. Not 4: the duplication is systematic rather than "minor instances of over-explanation"; not 2: there is no explanation of concepts Claude already knows and most sections earn their tokens.

3 / 5

Actionability

Guidance is mostly executable: exact canonical invocations ("${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run <script.py>, setup, doctor --json, seo_updates.py --kind spam --limit 500 --json), a 30-row command table, and conditional spawn rules keyed to concrete auth-check commands. Not 5: the referenced scripts/ runtime and the seo-* sub-skill definitions are not present in the reviewed bundle, and individual commands delegate with "load the relevant sub-skill directly" without further detail.

4 / 5

Workflow Clarity

The audit orchestration is a clearly sequenced 17-step list with conditional agent spawning, pre-flight auth checks, truncated-output handling, and an error-handling table that prescribes recovery (report partial results, re-run the failed sub-skill individually). Not 5: there is no explicit validate→fix→retry feedback loop around the audit pipeline itself, and per-command workflows are one-line delegations.

4 / 5

Progressive Disclosure

A dedicated Reference Files section with per-file descriptions, an explicit "Load these on-demand as needed (do NOT load all at startup)" instruction, and one-level-deep references — all 15 cited files verified to exist in references/. Not 5: two bundle files (backlink-quality.md, free-backlink-sources.md) are never surfaced anywhere in the body, and the Sub-Skills/Subagents rosters that overlap them are inlined instead of consolidated into a reference.

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.

The description is excellent: it lists comprehensive concrete capabilities, provides an explicit trigger list, and adds boundary guidance that disambiguates the hub from its specific seo-* sub-skills. The only weakness is that the trigger list omits a few natural synonyms users might say (ranking, keywords, backlinks, SERP).

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities — "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" — comprehensive coverage with sub-features named, matching the anchor-5 example's structure. Not 4: there are no notable gaps in the action list.

5 / 5

Completeness

Both questions are explicitly answered: a clear "what" (the full capability list) and a concrete "when" — "Triggers on: SEO, audit, schema, ... Use this hub only when the SEO domain is clear and the requested workflow is not; otherwise use the specific seo-* skill." Not 4: the "when" is fully explicit with concrete trigger phrases, not merely present.

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" provides good natural keyword coverage a user would actually say. Not 5: common variations and synonyms such as "ranking", "keyword research", "backlinks", or "SERP" are absent; clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

A clear SEO niche with distinct domain triggers, plus explicit disambiguation guidance against sibling skills ("Use this hub only when the SEO domain is clear and the requested workflow is not; otherwise use the specific seo-* skill"), which is stronger than the anchor-5 example. Not 4: the overlap risk with related seo-* skills is actively addressed, not just minor.

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

Path

skills/seo/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.