geo-proposal

Auto-generate a professional, client-ready GEO service proposal from audit data. Creates a full proposal in markdown and PDF including executive summary, findings, recommended service packages (Basic/Standard/Premium), pricing, timeline, and terms. Use when user says "proposal", "proposta", "offerta", "preventivo", "generate proposal", or after completing a GEO audit for a prospect.

Quality

74%

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-proposal/SKILL.md

Quality

Content

57%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, mostly actionable proposal-generation skill, but it inlines a very large template that should be split into a reference file and omits validation checkpoints for its generative/computational steps.

Suggestions

Move the ~220-line proposal template into a references file (e.g. references/proposal-template.md) and reference it from SKILL.md to improve progressive disclosure and token efficiency.

Add explicit validation checkpoints to the workflow — e.g. verify the audit file exists and the GEO score is numeric before generating, and confirm the proposal file was written and prospect record updated before reporting success.

Replace vague ROI placeholders like '€[LOW]/€[MED]/€[HIGH]' with the actual calculation formula or a documented assumption table so Claude can compute concrete values.

Dimension	Reasoning	Score
Conciseness	The body is mostly purposeful, but the ~220-line verbatim proposal template and repeated marketing-style benchmark tables ('+527% YoY', '900M+ users') pad the skill with material Claude could generate from the placeholders alone; it could be tightened without losing clarity.	3 / 5
Actionability	Concrete command syntax with flags, file paths, score-to-tier thresholds, and a fully specified fill-in template give mostly executable guidance; minor gaps are that some placeholders (e.g. ROI '€[LOW/MED/HIGH]') lack the calculation method.	4 / 5
Workflow Clarity	The three-step workflow is sequenced, but it lacks validation/verification checkpoints for a batch-style generative operation (score computation, file write, prospect-record update), and the guideline caps such skills at 3 — confirmed not a 2 because the sequence is explicit, and not a 4 because no checkpoints exist.	3 / 5
Progressive Disclosure	Sections are clearly labeled, but the entire proposal template is inlined in SKILL.md with no bundle files present; the template is the kind of large reusable artifact that belongs in a separate reference file, so it lands at the mid-anchor.	3 / 5
	Total	13 / 20 Passed

Description

91%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, third-person description that concretely states capabilities and gives explicit, even multilingual, trigger phrases. It clearly answers what and when with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Names several specific outputs — 'executive summary, findings, recommended service packages (Basic/Standard/Premium), pricing, timeline, and terms' — which is comprehensive, though 'auto-generate' and 'client-ready' lean slightly generic so it sits just below a perfect 5.	4 / 5
Completeness	Explicitly answers both 'what' (auto-generate a full proposal in markdown and PDF with named sections) and 'when' (a concrete 'Use when...' clause with specific trigger phrases).	5 / 5
Trigger Term Quality	Excellent coverage of natural user phrases including multilingual synonyms ('proposal', 'proposta', 'offerta', 'preventivo', 'generate proposal') plus a contextual trigger ('after completing a GEO audit').	5 / 5
Distinctiveness Conflict Risk	The GEO-proposal niche with named packages and audit-trigger phrasing is clearly distinct; minor overlap risk only with a generic SEO-audit skill, keeping it just below 5.	4 / 5
	Total	18 / 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-proposal/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.