CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

geo-report

Generate a professional, client-facing GEO report combining all audit results into a single deliverable with scores, findings, and prioritized actions

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/geo-report/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.

The body is a highly actionable, copy-paste-ready report template with a clear input-to-output workflow, and the rubric's instruction-only provisions mean the absence of code is not penalized. Its weaknesses are the ~400-line monolithic structure with zero progressive disclosure and padding from a glossary of concepts Claude already knows plus verbose framing examples.

Suggestions

Split the report template, glossary, and tone/dollar-framing guidance into reference files (e.g. references/report-template.md, references/client-language.md), keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

Remove or drastically trim the glossary entries for concepts Claude already knows (JSON-LD, SERP, LCP, INP, CLS, E-E-A-T), keeping only genuinely domain-specific terms like GEO, llms.txt, and sameAs conventions.

Add validation checkpoints to the workflow — e.g. verify all required input report files exist before generating, confirm all 12 sections are present and the composite score matches the formula before writing the final GEO-CLIENT-REPORT.md.

DimensionReasoningScore

Conciseness

The template tables, score formula, and tone guidance earn their tokens, but the glossary explains concepts Claude already knows (JSON-LD, SERP, LCP, INP, CLS, E-E-A-T) and the repeated 'Translate for the client' and dollar-value framing blocks pad the document. It is mostly efficient with some genuinely unnecessary explanation that could be tightened.

3 / 5

Actionability

The guidance is fully executable: exact 12-section report structure, the composite score formula with component weights and rounding rules, complete table templates with placeholders, per-tier action criteria (e.g. 'Quick Win criteria: < 4 hours by one person'), and explicit tone rules — everything needed to produce the deliverable directly.

5 / 5

Workflow Clarity

'How to Use This Skill' gives a clear 5-step sequence with input dependencies and conditional branches (competitor section 'if competitor URLs provided', SSR callout), but there are no validation checkpoints such as verifying all input report files exist or confirming the generated report meets the stated completeness/length criteria. Not a destructive or batch operation, so the cap of 3 does not apply.

4 / 5

Progressive Disclosure

The document is well-sectioned and navigable, but it is a ~400-line monolith with no bundle files at all — the glossary, methodology/data-source appendix, and tone/dollar-framing guidance could live in reference files while SKILL.md stays an overview. Some structure exists, but content that could be separate is fully inlined with no references.

3 / 5

Total

15

/

20

Passed

Description

58%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 communicates a clear, concrete deliverable (a client-facing GEO report with scores, findings, and prioritized actions) in third-person voice, but it omits any explicit 'when to use this skill' trigger guidance and relies on the unexplained acronym 'GEO' without synonyms or natural user phrasings. These gaps leave it distinguishable but under-triggerable.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks for a GEO report, client deliverable, or executive summary of a GEO audit.'

Spell out 'generative engine optimization' on first use and include synonyms such as 'AI search readiness report' or 'AI visibility audit' to improve trigger-term coverage.

Briefly name the upstream audits being aggregated (platform, content, technical, schema) so the description is self-contained and distinct from generic reporting skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions and outputs — 'Generate a professional, client-facing GEO report', 'combining all audit results into a single deliverable', 'with scores, findings, and prioritized actions' — but 'audit results' is generic and does not name which audits, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

The 'what' is clear and concrete (generate a client-facing GEO report from audit results with scores, findings, and actions), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant keywords are present ('GEO report', 'client-facing', 'audit results', 'prioritized actions') but common variations and synonyms are missing — 'generative engine optimization' is never spelled out, and natural user phrasings like 'AI search readiness' or 'write a client report' are absent.

3 / 5

Distinctiveness Conflict Risk

'GEO report' plus 'audit results' carves a mostly distinct niche with clear triggers within a GEO skill suite, but the unexpanded acronym 'GEO' (readable as geographic/geospatial) and the generic word 'report' create minor overlap risk with other reporting skills.

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