CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-geo

Audit and improve content for AI Overviews and answer engines, including citability, entity clarity, crawler access, brand signals, and passage structure. Use when the user asks about AI Overviews, AI Mode, ChatGPT, Perplexity or Gemini citations, GEO, or AI search visibility.

Quality

82%

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

75%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 content is highly actionable and well-structured for conducting a GEO audit, with concrete commands, tables, output templates, and error-recovery guidance. Its main weakness is token efficiency: repeated crawler-distinction explanations, restated llms.txt conclusions, and inline time-sensitive statistics that inflate the body and could be consolidated or moved to the existing reference files.

Suggestions

Consolidate the crawler-distinction guidance: the claim-to-bot mapping table, the four bold bullets that re-explain the same OAI-SearchBot/GPTBot, Google-Extended, Claude-SearchBot, and Applebot-Extended distinctions, and the closing 'do not use interchangeably' prose all cover the same ground — keep the table and one summary line, cutting the rest.

Move the Key Statistics table and the Ahrefs correlation table into a dated reference file (e.g. references/stats.md) and keep only the few figures needed during an audit inline, since the body itself warns these figures go stale.

After the pointer to references/llmstxt-evidence.md, reduce the multi-paragraph llms.txt restatement to the single operative rule ('never recommend llms.txt as a Google ranking or citation lever') plus the template.

DimensionReasoningScore

Conciseness

The body is dense and mostly free of padding, but the OAI-SearchBot/GPTBot/Claude-SearchBot distinction is explained three separate times (mapping table, four bold bullets, closing prose), the llms.txt conclusion is restated at length after pointing to references/llmstxt-evidence.md, and large date-stamped statistics tables are inlined rather than deferred to references — matching the 'mostly efficient but could be tightened' anchor.

3 / 5

Actionability

Guidance is fully executable for an instruction-only skill: a copy-paste command ("claude-seo run seo_updates.py --kind product --kind core --limit 0 --json"), a 10-item GEO-ANALYSIS.md output template, a claim-to-bot mapping table, a ready-to-use llms.txt template, and an error-handling table with specific actions for each failure scenario.

5 / 5

Workflow Clarity

The output template and error-handling table provide clear checkpoints and recovery paths, but the audit's step sequence (fetch URL, check robots.txt, evaluate content criteria, produce report) must be inferred from the topic ordering and Output section rather than being explicitly sequenced, leaving minor validation gaps relative to the 5 anchor.

4 / 5

Progressive Disclosure

Both referenced files (references/google-ai-optimization-guide.md and references/llmstxt-evidence.md) exist, are clearly signaled in the body, and are one level deep, with well-organized sections throughout; however, the bulk of working detail (statistics and crawler tables) lives inline in a 413-line SKILL.md rather than being split into further reference files, which keeps this at 'good structure; minor organization gaps'.

4 / 5

Total

16

/

20

Passed

Description

83%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 with an explicit two-part structure: concrete capability areas in the what-clause and a rich set of natural trigger terms in the when-clause. Its only weaknesses are slightly limited verb-level action coverage and a few missing synonyms for the GEO domain.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas ("citability, entity clarity, crawler access, brand signals, and passage structure") but uses only two verbs ("Audit and improve"), leaving minor gaps in coverage relative to the comprehensive multi-action anchor at 5.

4 / 5

Completeness

It explicitly answers both what ("Audit and improve content for AI Overviews and answer engines, including...") and when ("Use when the user asks about...") with concrete trigger phrases, matching the 5 anchor; the 4 anchor's weaker 'when' clause does not apply here.

5 / 5

Trigger Term Quality

Trigger terms "AI Overviews, AI Mode, ChatGPT, Perplexity or Gemini citations, GEO, or AI search visibility" give good natural keyword coverage including platform names and the key acronym, but common variations like the spelled-out "generative engine optimization" or "AEO" are missing, so it falls just short of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The GEO/AI-search-citation niche has distinct triggers (AI Overviews, GEO, Perplexity citations), but as an SEO-category skill in an SEO plugin it has minor overlap risk with sibling general-SEO skills on broad search-visibility queries, fitting the 4 anchor rather than 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

AgriciDaniel/claude-seo

Path

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