CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

geo-platform-optimizer

Platform-specific AI search optimization — audit and optimize for Google AI Overviews, ChatGPT, Perplexity, Gemini, and Bing Copilot individually

Quality

71%

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-platform-optimizer/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 well-structured, information-dense skill with genuinely non-obvious platform citation data, deterministic scoring rubrics, and a concrete output format. Its main weaknesses are the absence of any progressive disclosure (everything is inlined in one long file) and scattered vague checklist items that give direction without executable steps.

Suggestions

Split each platform's section (selection logic + checklist + scoring rubric) into references/<platform>.md files, keeping SKILL.md as a short overview with the workflow, the cross-platform summary table, and links to each platform file.

Replace vague directives like "assess notability criteria" and "audit backlink profile for these sources" with the specific checks to perform and what evidence to record.

Add a validation step to the workflow for inaccessible or un-fetchable target URLs, so the audit does not proceed on missing data.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain knowledge Claude would not know (e.g. "92% of AIO citations come from pages already ranking in the top 10", "Wikipedia (47.9%)" domain share, the IndexNow key file path, the Aug 2023 FAQPage schema restriction) and avoids explaining concepts Claude already knows. It is not 5 because several items recur across platforms and the Cross-Platform Summary repeats checklist content (author bylines, YouTube, structured data, freshness).

4 / 5

Actionability

Guidance is highly concrete: exact file paths ("/.well-known/indexnow-key.txt"), quantified thresholds ("2000+ words", "sub-2-second load time", "within 6 months"), point-allocated scoring tables per platform, and a complete output template. It is not 5 because several checklist items are vague directives with no execution steps ("assess notability criteria", "audit backlink profile for these sources", "maintain an active GitHub presence").

4 / 5

Workflow Clarity

The "How to Use This Skill" section gives a clear 4-step sequence (collect URL/topic → run each platform checklist → score 0-100 → generate the report), and the deterministic scoring rubrics plus status thresholds (Strong/Moderate/Weak) act as structured checkpoints. It is not 5 because there are no explicit validation steps or error-recovery loops (e.g. what to do if the URL is unreachable or a platform check cannot be performed).

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so all five platform sections — each ~55 lines of selection logic, a 10-item checklist, and a scoring table — are inlined in a single ~276-line SKILL.md. Internal structure is good (per-platform headers, summary table, output template), but content that naturally belongs in separate per-platform reference files is inline, matching the 'some structure but could be better organized' anchor rather than the 'clear overview with well-signaled references' anchor.

3 / 5

Total

15

/

20

Passed

Description

61%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, third-person description with a clear 'what' and strong platform-name triggers, but it lacks any 'Use when...' trigger guidance and its action verbs ('audit and optimize') are generic. Adding an explicit when-to-use clause and naming concrete deliverables would lift it into the top band.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to improve how a site is cited or referenced by AI search engines (Google AI Overviews, ChatGPT, Perplexity, Gemini, Bing Copilot)."

Make the actions concrete: name the deliverable, e.g. "...produces a per-platform score (0-100), gap analysis, and prioritized action plan."

Include common synonyms such as "GEO" or "generative engine optimization" so users who say those phrases trigger this skill.

DimensionReasoningScore

Specificity

The description names two concrete actions ("audit and optimize") and a specific enumeration of five target platforms ("Google AI Overviews, ChatGPT, Perplexity, Gemini, and Bing Copilot"), matching the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage. It is not 4 because the actions themselves are generic — nothing specifies what the audit or optimization actually involves.

3 / 5

Completeness

The 'what' is clearly stated ("Platform-specific AI search optimization — audit and optimize for ... individually") and a 'when' is only weakly implied by the platform enumeration. A missing 'Use when...' clause or equivalent explicit trigger guidance caps completeness at 3 per the rubric guidelines; it is not 2 because the 'what' is concrete and specific rather than vague.

3 / 5

Trigger Term Quality

Strong natural triggers are present ("ChatGPT", "Perplexity", "Gemini", "Google AI Overviews", "Bing Copilot", "AI search") that users would actually say. It is not 5 because common synonyms like "GEO", "generative engine optimization", or "answer engine" are missing; not 3 because platform-name coverage is substantially better than 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche — per-platform AI search citation optimization — with five named-platform triggers that are unlikely to fire for unrelated skills. It is not 5 because "optimization"/"audit" leaves minor overlap risk with a generic SEO or site-audit skill; not 3 because the platform-specific framing is far more distinct than 'somewhat specific'.

4 / 5

Total

14

/

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

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

14

/

16

Passed

Repository

zubair-trabzada/geo-seo-claude

Path

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