geo-report

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

Quality

68%

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

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 content is highly actionable with a complete, copy-paste-ready report template and a clear usage sequence, but it is weighed down by inline time-sensitive claims and a somewhat monolithic structure that underuses progressive disclosure.

Suggestions

Move time-sensitive claims (version dates, projected percentages, citation study years) into a clearly labeled 'deprecated/old patterns' or 'benchmarks as of [date]' section so conciseness is not penalized.

Add a validation checkpoint in 'How to Use This Skill' (e.g. verify all four audit report files exist and scores are present before generating) to push workflow clarity toward the top anchor.

Split the glossary and methodology/data-sources into a separate reference file (e.g. references/METHODOLOGY.md) and link to it from the appendix to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient template content, but it carries time-sensitive claims inline (e.g. 'December 2025 Quality Rater Guidelines', '25-40% of organic discovery by end of 2026', 'replaced FID in March 2024') and a glossary defining basic terms Claude already knows, which the rubric penalizes when not placed in a deprecated/old-patterns section.	3 / 5
Actionability	The body is fully executable: an explicit score formula, exact markdown table templates with column structures, section-by-section writing instructions with sentence counts, and concrete example actions, all copy-paste ready for the common cases.	5 / 5
Workflow Clarity	'How to Use This Skill' lays out a clear 5-step sequence ending in a named output file, but it lacks explicit validation checkpoints (e.g. confirming all audit inputs exist or that component scores sum correctly) before generating the report.	4 / 5
Progressive Disclosure	The skill is well-organized with clear section headers, but it is a single ~400-line monolithic file with no bundle references; secondary material like the glossary and methodology could live in separate reference files, and no one-level-deep references are signaled.	3 / 5
	Total	15 / 20 Passed

Description

66%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 is specific and largely distinct, clearly conveying what the skill produces, but it lacks any explicit 'when to use' trigger guidance, which caps its completeness and leaves some natural trigger terms uncovered.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks for a GEO client report or wants to combine GEO audit results into a client-facing deliverable.'

Broaden trigger terms with synonyms users might say, such as 'Generative Engine Optimization report', 'executive summary', or 'client deliverable'.

Make the concrete actions slightly more specific (e.g. name the composite 'GEO Readiness Score' and the prioritized action plan) to push specificity toward the top anchor.

Dimension	Reasoning	Score
Specificity	Names the GEO report domain and several concrete actions ('combining all audit results', 'scores, findings, and prioritized actions'), but the actions are somewhat high-level rather than maximally specific, placing it just below the comprehensive anchor 5.	4 / 5
Completeness	The description gives a clear 'what' (generate a GEO report with scores, findings, and prioritized actions) but provides no explicit 'Use when...' trigger clause, so per the rubric's cap, completeness cannot exceed 3.	3 / 5
Trigger Term Quality	Includes natural terms like 'GEO report', 'audit results', and 'client-facing report' that a user might say, but omits synonyms (e.g. 'Generative Engine Optimization report', 'executive summary', 'client deliverable') and file extensions, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	The 'GEO report combining all audit results' niche is tied to specific audit skills and is clearly distinguishable, with only minor overlap risk against generic report-generation skills.	4 / 5
	Total	15 / 20 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: b26418a

Reviewed: 1 day 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.