geo-report

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/geo-report/SKILL.md

Quality

Content

77%

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-sequenced for generating a client GEO report, but it is monolithic and somewhat verbose, bundling the entire template plus reference-style material into one file.

Suggestions

Move the reusable report template (sections 1–12) and glossary into a referenced file (e.g. references/report-template.md) and keep SKILL.md as a concise overview with one-level-deep links.

Trim the glossary and 'Translate for the client' / dollar-value framing examples, which restate concepts Claude already knows.

Add a brief verification checklist at the end (e.g. confirm every section is filled and the composite score reconciles with component weights) before outputting the report.

Dimension	Reasoning	Score
Conciseness	The body is mostly purposeful template specification, but a ~390-line single file that also defines well-known concepts (a glossary for GEO, AIO, E-E-A-T, SSR) and includes lengthy illustrative framing examples could be tightened.	2 / 3
Actionability	It provides copy-paste-ready section templates, exact tables, an explicit scoring formula, and score-interpretation ranges, giving concrete fill-in guidance throughout.	3 / 3
Workflow Clarity	A clear 5-step usage sequence precedes a well-ordered 12-section report template; while there are no validation checkpoints, report generation is non-destructive so they are not required.	3 / 3
Progressive Disclosure	The skill is a single monolithic file with no bundle files, and large blocks (the full template, glossary, methodology) that could live in separate references are kept inline.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 is clear and distinct about producing a client-facing GEO report, but it lacks explicit trigger guidance and relies on a single action verb with content components rather than multiple distinct actions.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks for a GEO/client audit report or wants to consolidate GEO audit results into a deliverable.'

Surface more natural keywords users would actually say ('GEO audit', 'client report', 'AI search readiness report') to broaden trigger coverage.

Convert report components into concrete action verbs (aggregate, score, prioritize, format) to lift specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (GEO report) and lists deliverable contents ('scores, findings, and prioritized actions'), but the only real action verb is 'Generate' — the rest are report components rather than distinct concrete actions.	2 / 3
Completeness	It clearly states what the skill does but provides no explicit 'when to use it' trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Relevant terms like 'GEO report' and 'audit results' are present, but coverage of natural phrasings a user would say is thin and there are no explicit 'Use when' trigger phrases.	2 / 3
Distinctiveness Conflict Risk	The GEO client-report aggregation niche is specific and clearly distinguishable from other skills, making accidental triggering unlikely.	3 / 3
	Total	9 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 9eec32f

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.