CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

geo-technical

Technical SEO audit with GEO-specific checks — crawlability, indexability, security, performance, SSR, and AI crawler access

Quality

73%

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/geo-technical/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, well-structured audit rubric with executable commands, precise thresholds, and a complete output template — its strongest dimension by far. The weaknesses are moderate verbosity from explaining concepts Claude already knows and a monolithic single-file layout that inlines template and reference material that belongs in bundle files.

Suggestions

Trim explanations of concepts Claude already knows (what CLS/INP measure, what RFC 8288 and IndexNow are, why mobile-first indexing exists) and keep only the skill-specific thresholds, nuances, and decisions.

Move the full GEO-TECHNICAL-AUDIT.md output template and the AI-crawler user-agent table into references/ files (e.g., references/output-template.md, references/ai-crawlers.md), keeping a short pointer and the 2-3 most decision-critical rows inline.

Add error-handling guidance for the fetch steps (non-200 responses, unreachable robots.txt/sitemap, malformed XML) so the workflow has explicit recovery checkpoints rather than handling them only in Category 9.

DimensionReasoningScore

Conciseness

The body is mostly efficient — checklists, tables, thresholds, and point values rather than prose — but it includes several explanations of concepts Claude already knows, e.g., "INP ... Measures ALL interactions, not just first", "CLS ... Measures visual stability — unexpected layout movements", "IndexNow is an open protocol that allows websites to notify search engines instantly", and "RFC 8288 (Web Linking) defines the HTTP Link: response header". This fits the 'mostly efficient but includes some unnecessary explanation' anchor; it is not a 2 because the padding is incidental rather than structural, and not a 4 because the known-concept explanations recur across multiple categories.

3 / 5

Actionability

Guidance is fully executable throughout: exact commands ("curl -o /dev/null -s -w 'TTFB: %{time_starttransfer}s\n' [URL]", "curl -s [URL]"), precise thresholds (LCP < 2.5s, TTFB < 800ms, page weight < 2MB, 48x48px tap targets), a complete AI-crawler user-agent table, per-category point rubrics, and a copy-paste-ready output template. This matches the 'fully executable; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

"How to Use This Skill" gives a clear 5-step sequence (collect URL, fetch, run categories, score, generate report), reinforced by explicit interpretation bands (90-100 Excellent ... 0-29 Critical) and per-category Pass/Warn/Fail thresholds that act as checkpoints. It is a 4 rather than 5 because error-recovery loops are missing for the fetch steps (what to do when a fetch fails, a page returns non-200, or the sitemap is malformed — only Category 9 specifies skip-and-note behavior); it is not a 3 because the sequence, scoring checkpoints, and output validation via status thresholds are all present.

4 / 5

Progressive Disclosure

The single SKILL.md has no bundle files (no references/, scripts/, or assets/ exist), so all 533 lines — including the full output template, the 11-row AI-crawler table, and two full pages of boilerplate per-scenario markdown for the report — are inlined. Section headers provide reasonable navigation, but content that clearly belongs in separate reference files (e.g., OUTPUT-TEMPLATE.md, AI-CRAWLERS.md) sits inline, matching the 'some structure but content that should be separate is inline' anchor; it is not a 2 because the document is well-sectioned and navigable rather than an unstructured wall.

3 / 5

Total

15

/

20

Passed

Description

66%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 specific, well-scoped description in third person that clearly communicates what the skill audits, with good domain keywords. Its main weakness is the complete absence of a 'Use when...' trigger clause, which both caps completeness and weakens trigger-term coverage of natural user phrasings.

Suggestions

Append an explicit trigger clause, e.g., "Use when auditing a website's technical health, diagnosing why pages aren't indexed or cited by AI assistants, or checking robots.txt / AI crawler access."

Add natural trigger synonyms users would actually say, such as "site audit", "search visibility", "AI search optimization", and "Core Web Vitals", to improve both trigger-term quality and completeness.

Mention the remaining audit categories from the body (mobile optimization, Core Web Vitals, URL structure) so the description's coverage is comprehensive rather than partial.

DimensionReasoningScore

Specificity

The description names the domain ("Technical SEO audit") and lists several specific check areas ("crawlability, indexability, security, performance, SSR, and AI crawler access"), giving it concrete scope. It stays at the level of audit categories rather than concrete actions like 'extract' or 'generate', and coverage has minor gaps (e.g., mobile optimization and Core Web Vitals are prominent in the body but absent from the description), matching the score-4 anchor rather than the comprehensive score-5 anchor.

4 / 5

Completeness

The 'what' is clear and specific, but there is no 'Use when...' clause or any equivalent explicit trigger guidance (e.g., "Use when auditing a site's technical health or checking AI crawler access"), which caps completeness at 3 per the rubric guideline. It is not a 4 because the 'when' is entirely absent, not merely under-specified.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "Technical SEO audit", "crawlability", "indexability", "SSR", "AI crawler". However, common variations users would plausibly say — "site audit", "search visibility", "AI search", "Core Web Vitals" — are missing, which fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

"GEO-specific checks" and "AI crawler access" carve out a distinct niche that separates it from generic SEO or site-audit skills. Minor overlap risk remains with closely related SEO/GEO skills (e.g., content-focused GEO audits or general website audit skills) since the description does not state when this skill applies versus those siblings, so it fits the score-4 anchor rather than the minimal-conflict score-5 anchor.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (533 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

zubair-trabzada/geo-seo-claude

Path

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