geo-technical

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

Quality

63%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/geo-technical/SKILL.md

Quality

Content

57%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 thorough, actionable audit reference with concrete commands and thresholds, but it is over-long for a SKILL.md, lacks validation checkpoints in its batch workflow, and keeps all content inlined with no progressive disclosure. Splitting reference material into bundled files and trimming known-concept explanations would materially improve it.

Suggestions

Add validation checkpoints to the audit workflow (e.g. confirm each fetch returns 200 before scoring, retry once on failure, verify raw-HTML vs rendered-DOM divergence before declaring SSR issues).

Move large reference blocks into bundled files under references/ (e.g. ai-crawlers.md for the crawler table, output-template.md for the GEO-TECHNICAL-AUDIT.md scaffold) and link to them from the body.

Trim explanations of basics Claude already knows (robots.txt directive syntax, viewport meta tag meaning) to lift conciseness toward the top band.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and reference-dense, but it re-explains concepts Claude already knows (basic robots.txt directive syntax, viewport meta basics) and at ~530 lines could be tightened without losing value.	3 / 5
Actionability	Provides concrete curl commands, exact header values, numeric thresholds, named crawler user-agents, and per-fix recommendations; minor gaps such as no ready-to-run sitemap validation snippet keep it just below fully copy-paste ready.	4 / 5
Workflow Clarity	A clear 5-step 'How to Use' sequence and per-category scoring exist, but a multi-page batch audit has no validation checkpoints (e.g. verify the fetch succeeded, retry on failure, confirm raw HTML vs rendered DOM), which caps workflow clarity at 3 per the batch-operations guideline.	3 / 5
Progressive Disclosure	Section structure is clear, but the skill is a single monolithic file with no bundle files or external references despite its length, so large reference tables and the output template are inlined rather than split out.	3 / 5
	Total	13 / 20 Passed

Description

70%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 specific and distinctive about a GEO-focused technical SEO audit, but it is missing an explicit 'Use when...' trigger clause, which caps its completeness. Adding natural trigger phrases would lift it to the top band.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when auditing a site's technical SEO, diagnosing crawl/indexing issues, or checking AI crawler access for GEO visibility.'

Include lay synonyms users actually say (e.g. 'SEO check', 'why isn't my site indexed', 'AI search visibility') alongside the technical terms.

Optionally surface one or two concrete audit verbs (fetch, validate, score) to push specificity from 4 toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain and lists six concrete check areas (crawlability, indexability, security, performance, SSR, AI crawler access), but does not enumerate the concrete audit verbs (fetch, validate, score), keeping it just short of comprehensive.	4 / 5
Completeness	It clearly states what the skill does but lacks any 'Use when...' trigger clause, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes domain-natural terms like 'SEO audit', 'crawlability', 'indexability', and 'SSR' that users would say, though it omits common synonyms such as 'SEO check' or 'why isn't my site indexed'.	4 / 5
Distinctiveness Conflict Risk	The GEO-specific technical SEO niche with SSR and AI crawler access framing is highly distinct and unlikely to trigger the wrong skill.	5 / 5
	Total	16 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: b26418a

Reviewed: 1 day 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.