CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

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

63%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, mostly actionable skill body with clear phased workflows and executable command examples. It loses points on conciseness and progressive disclosure because substantial reference material (market context, scoring weights, per-command specs) is inlined rather than offloaded to the referenced sub-skill/agent/template files.

Suggestions

Move the Market Context table and detailed Scoring Methodology/Business Type Detection tables into a bundled reference file (e.g., references/geo-context.md) and link to it, reducing inline tokens.

Add explicit validation feedback loops for batch crawl operations (e.g., 'if a page fetch times out, retry once then skip and log') to strengthen workflow_clarity to a 5.

Verify the referenced sub-skill (skills/geo-*/), subagent (agents/*.md), and template (templates/*.css, *.html) paths actually exist as bundled files; if absent, either add them or remove the references to keep progressive disclosure one-level-deep and real.

DimensionReasoningScore

Conciseness

Mostly efficient and table-driven, but the Market Context table (10 rows of market stats), Business Type Detection, and the large command/output tables are reference material Claude largely doesn't need inline and could be trimmed or moved to bundled files, landing at the 'mostly efficient but could be tightened' anchor.

3 / 5

Actionability

Provides concrete executable commands and a complete, copy-pasteable pandoc + Chrome PDF-generation bash block, with only minor gaps (subagent orchestration steps are described rather than given as runnable scripts), fitting the 4 anchor.

4 / 5

Workflow Clarity

The full audit is clearly sequenced into Discovery, parallel Analysis, and Synthesis phases with a scoring methodology, and the PDF workflow is a numbered pipeline; Quality Gates act as checkpoints. It lacks explicit validate→fix→retry feedback loops for the destructive/batch crawl operations, so it stays at 4 rather than 5.

4 / 5

Progressive Disclosure

Structure is clear with sections and references to sub-skills/subagents by path, but all detailed content (market stats, scoring weights, business types, every command spec) is inlined in SKILL.md rather than split into referenced files, and the referenced skills/agents/ and templates/ paths are not bundled here, so organization is mid-level.

3 / 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, specific description with comprehensive trigger terms and an explicit 'Use when' clause covering both what and when. Third-person voice is used correctly. Minor overlap risk on generic terms like 'seo' and 'audit' keeps distinctiveness just under perfect.

DimensionReasoningScore

Specificity

Lists numerous 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') — multiple specific actions with only minor gaps in coverage, fitting the 4 anchor.

4 / 5

Completeness

Explicitly answers both what ('GEO-first SEO analysis tool... Performs...') and when ('Use when user says...'), with concrete trigger phrases, matching the 5 anchor for both what and when.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural trigger terms a user would actually say ('geo', 'seo', 'audit', 'AI search', 'AI visibility', 'optimize', 'citability', 'llms.txt', 'schema', 'brand mentions', 'GEO report', plus 'any URL for analysis'), including synonyms and platform names, matching the 5 anchor.

5 / 5

Distinctiveness Conflict Risk

It carves a clear GEO/AI-search niche with distinct triggers, but very broad term 'seo' and generic 'optimize'/'audit' could overlap with general SEO or other audit skills, so it sits just below the minimal-conflict 5 anchor.

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.

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