CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-technical

Run a comprehensive technical SEO audit covering crawlability, indexability, rendering, site architecture, structured data, page experience, security, and internationalization. Use this skill whenever the user asks about technical SEO, crawl issues, indexing problems, sitemaps, robots.txt, canonical tags, schema markup, page speed, Core Web Vitals, hreflang, redirects, or site-wide search performance. Triggers on technical SEO, site audit, crawlability, indexability, sitemap, robots.txt, canonical, redirect chain, schema, JSON-LD, Core Web Vitals, page speed, hreflang, mobile usability, HTTPS, security headers, render-blocking, JavaScript SEO. Also triggers when a site has indexing problems, traffic drops, or migration concerns, even if 'technical SEO' is not said explicitly.

Quality

87%

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

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

A well-structured skill body: lean expert checklists, a clear 7-step audit workflow, and exemplary use of two one-level-deep reference files for the heavy templates. The recurring weakness is a handful of vague or unverifiable criteria in the architecture layer and the absence of an explicit validation loop before report writing.

Suggestions

Make the vague architecture-layer bullets measurable, e.g. replace 'Internal linking distributes authority logically' and 'Clear URL hierarchy that mirrors site structure' with decidable checks like 'category depth <= 3 URL segments' or 'top pages have >= N unique internal inbound links per crawl'.

Add an explicit validation checkpoint to the workflow before 'Write the report', e.g. verify each finding against a second source (rendered HTML, search console, or log line) and re-check any finding that only one data source supports.

Trim parentheticals that define concepts Claude already knows (e.g. '(showing different content to bots vs users)' after 'No cloaking') to lift conciseness toward the every-token-earns-its-place standard.

DimensionReasoningScore

Conciseness

The body is dense, checklist-driven, and full of expert criteria Claude would not reliably recall ('rel=next/prev is deprecated, but consistent canonicals matter', '404 pages return 404, not 200 with page not found content (soft 404)'), with almost no fluff. A few parentheticals explain concepts Claude already knows ('No cloaking (showing different content to bots vs users)'), which keeps it at anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Most checklist items are concrete, verifiable pass/fail criteria ('Sitemap is present, returns 200, and lists canonical URLs only', 'Important pages reachable in 3 clicks or fewer', 'test with the URL Inspection tool'), and the workflow/output sections give concrete structure. However several bullets are undecidable as written ('Internal linking distributes authority logically', 'Clear URL hierarchy that mirrors site structure'), which is the minor-gap profile of anchor 4 rather than the fully executable anchor 5.

4 / 5

Workflow Clarity

The 7-step workflow (Define scope, Confirm access, Crawl, Run the framework, Cross-reference, Prioritize, Write the report) is clearly sequenced with a verification checkpoint (cross-referencing search console against sitemap and crawl output) and explicit prioritization tiers. It is not anchor 5 because there is no explicit validate-findings-before-reporting feedback loop; it is not anchor 3 because checkpoints are present and the destructive/batch-operation cap does not apply to a read-only audit.

4 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview that keeps the core 6-layer method inline while pushing detail to two real, substantial reference files (audit-template.md, migration-checklist.md) that are exactly one level deep, clearly signaled in a 'Reference files' section and linked inline at workflow step 7. This matches anchor 5's clear overview with well-signaled one-level-deep references.

5 / 5

Total

17

/

20

Passed

Description

91%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: it explicitly states both what the skill does and when to use it, with unusually thorough and natural trigger coverage including indirect triggers. The only weaknesses are a single-verb action statement and minor overlap risk with sibling performance/structured-data skills.

DimensionReasoningScore

Specificity

The description names the domain and enumerates concrete coverage areas ('crawlability, indexability, rendering, site architecture, structured data, page experience, security, and internationalization'), but the action is a single one ('Run a comprehensive technical SEO audit') rather than multiple distinct actions, matching anchor 4 with minor gaps rather than the comprehensive multi-action anchor 5.

4 / 5

Completeness

It explicitly answers what ('Run a comprehensive technical SEO audit covering...') and when ('Use this skill whenever the user asks about technical SEO, crawl issues, indexing problems...') with concrete trigger phrases, exactly matching anchor 5. Anchor 4 would apply only if the 'when' clause were less explicit.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive with natural terms, synonyms, and technical variants users would actually say ('crawl issues, indexing problems, sitemaps, robots.txt, canonical tags, schema markup, page speed, Core Web Vitals, hreflang, redirects, JSON-LD, mobile usability, HTTPS, security headers, render-blocking, JavaScript SEO'), plus indirect triggers ('traffic drops, or migration concerns, even if technical SEO is not said explicitly'). This matches the anchor 5 example's breadth; no significant natural term is missing, so it is not anchor 4.

5 / 5

Distinctiveness Conflict Risk

The technical-SEO niche is clear and most triggers (robots.txt, hreflang, canonical) are distinct, but terms like 'page speed, Core Web Vitals' and 'schema markup' carry minor overlap risk with closely related performance-optimization and structured-data skills that the description does not disambiguate, matching anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

18

/

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

rampstackco/claude-skills

Path

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