CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

geo

GEO-first SEO analysis tool. Optimizes websites for AI-powered search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) while maintaining traditional SEO foundations. Performs full GEO audits, citability scoring, AI crawler analysis, llms.txt generation, brand mention scanning, platform-specific optimization, schema markup, technical SEO, content quality (E-E-A-T), and client-ready GEO report generation. Use when user says "geo", "seo", "audit", "AI search", "AI visibility", "optimize", "citability", "llms.txt", "schema", "brand mentions", "GEO report", or any URL for analysis.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./geo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 orchestration overview with strong command/output mapping and genuinely executable PDF-generation commands, but it under-performs on two fronts: the market-stats table and dated references add payload Claude doesn't need, and the multi-phase audit workflow lacks validation checkpoints despite being a 50-page batch crawl operation. The PDF-report detail inlined in the overview should live in the geo-report sub-skill it duplicates.

Suggestions

Delete the 'Market Context (Why GEO Matters)' table and the '(February 2026)' date stamp — they are sales context, not execution guidance, and embed time-sensitive data outside any 'old patterns' section.

Add explicit validation checkpoints to the audit workflow (e.g., verify each sub-agent returned a complete report, spot-check fetched pages resolved correctly before scoring) to lift workflow clarity above the batch-operation cap of 3.

Move the 'PDF Report Generation' section's requirements, template paths, and bash commands into the referenced geo-report sub-skill, keeping only a one-line pointer in the Quick Reference so SKILL.md stays a true overview.

DimensionReasoningScore

Conciseness

Most of the body is dense, scannable tables with no re-teaching of concepts Claude already knows, but it carries unnecessary payload: the 10-row 'Market Context (Why GEO Matters)' stats table is sales-pitch material irrelevant to executing the skill, and it plus the '(February 2026)' title stamp embed time-sensitive data outside any 'old patterns' section. This matches the level-3 anchor (mostly efficient but includes some unnecessary content) rather than level 4, which requires only minor trims.

3 / 5

Actionability

The PDF workflow ships copy-paste-ready commands (full `pandoc ...` and `"/Applications/Google Chrome.app/..." --headless=new --print-to-pdf=...` invocations), commands are mapped to exact output files, and business-type detection gives concrete signal patterns. It falls short of level 5 because large portions (composite GEO Score calculation, sub-agent instructions, most of the 14 sub-skills' internals) are delegated to non-bundled files and left as descriptions rather than executable guidance — minor gaps, matching level 4.

4 / 5

Workflow Clarity

The audit workflow has a clear three-phase sequence (Discovery → 'Launch these 5 subagents simultaneously' → Synthesis), but validation/verification checkpoints are absent — no step verifies fetch results, sub-agent report completeness, or output-file correctness. Per the judging guidelines, a batch operation (crawling up to 50 external pages) without validation steps is capped at 3, and the quality gates (limits, timeouts, rate limiting) are guardrails, not feedback loops. Level 4 would require most checkpoints to be present.

3 / 5

Progressive Disclosure

The body is well organized as an overview with one-level-deep references clearly signaled via tables ('Sub-Skills (14 Specialized Components)' with `skills/geo-*/` directories, 'Subagents' with `agents/*.md` files), so navigation is easy. It stops short of level 5 because substantial content that belongs in those referenced files is inlined in SKILL.md — the entire 'PDF Report Generation' section (requirements, styling details, full bash workflow, template paths) duplicates the geo-report sub-skill, as does the scoring methodology. No bundle files were provided to verify against, so structure is scored on the body's signaling alone.

4 / 5

Total

14

/

20

Passed

Description

88%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 opens with a clear niche positioning ('GEO-first SEO analysis tool'), enumerates comprehensive concrete capabilities, and closes with an explicit trigger-term list. Its only weaknesses are a few missing natural synonyms (GEO never spelled out) and overly broad triggers ('schema', 'any URL') that create minor conflict risk with generic SEO/URL skills.

DimensionReasoningScore

Specificity

The description lists many concrete actions — 'Performs full GEO audits, citability scoring, AI crawler analysis, llms.txt generation, brand mention scanning, platform-specific optimization, schema markup, technical SEO, content quality (E-E-A-T), and client-ready GEO report generation' — comprehensive coverage of the tool's capabilities with no vague filler. It clearly matches the level-5 anchor (multiple specific concrete actions, comprehensive); level 4 would require noticeable gaps in coverage, which are absent.

5 / 5

Completeness

Both halves are explicit: the 'what' is a full enumerated capability list, and the 'when' is a literal 'Use when user says... [term list] or any URL for analysis'. This mirrors the level-5 exemplar (clear 'what' plus concrete trigger phrases). It is not level 4 because the 'when' clause is not merely present but enumerates specific concrete triggers.

5 / 5

Trigger Term Quality

Trigger list '"geo", "seo", "audit", "AI search", "AI visibility", "optimize", "citability", "llms.txt", "schema", "brand mentions", "GEO report"' covers natural phrasings users would actually say. Falls short of level 5 because common variations are missing — 'generative engine optimization' (GEO is never spelled out), 'AI SEO', 'ChatGPT visibility', 'Perplexity' as a trigger — so a few natural terms are absent, matching the level-4 anchor.

4 / 5

Distinctiveness Conflict Risk

The GEO/AI-search niche is distinct and well-branded ('GEO-first', 'citability', 'llms.txt', 'AI crawler'), so it won't be confused with unrelated skills. However, generic triggers like 'schema', 'audit', 'optimize', and especially 'or any URL for analysis' create minor overlap risk with general SEO, schema-markup, and URL-fetching skills — the level-4 anchor (mostly distinct, minor overlap risk) fits; level 5 would require minimal conflict risk, which the catch-all URL trigger precludes.

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

allowed_tools_field

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

Warning

Total

15

/

16

Passed

Repository

zubair-trabzada/geo-seo-claude

Path

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