CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

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

Quality

Content

63%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 skill is highly actionable and clearly sequenced — command syntax, path conventions, tier logic, and the deliverable template are all concrete. Its main weakness is structure: the body is a monolith dominated by an inlined proposal template containing marketing boilerplate and time-sensitive claims, with no reference files to split it out and no final placeholder-validation step.

Suggestions

Move the ~240-line proposal template to a references/ file (e.g. references/proposal-template.md) and keep only the placeholder-filling rules and tier logic in SKILL.md, which would improve both conciseness and progressive_disclosure.

Add an explicit validation step to the workflow: after generating the document, verify no '[PLACEHOLDER]' strings remain before saving and reporting the proposal as client-ready.

Either add concrete PDF generation instructions (the description promises PDF output) or remove the PDF claim from the description and rely solely on the '/geo report-pdf' handoff.

DimensionReasoningScore

Conciseness

The command, workflow, and output sections are lean, but ~240 of ~330 lines are an inlined sales template whose generic marketing prose ('First-mover advantage is real') and time-sensitive claims ('+527% YoY', '25-40% of organic discovery by end of 2026') read as padding Claude could draft unaided. Mostly efficient but with unnecessary sections that could be tightened — anchor 3, not 2 because the pricing, package inclusions, and score-tier mappings are genuine data Claude does not know.

3 / 5

Actionability

Concrete throughout: exact command syntax with three worked examples, file paths for audit input and proposal output, a deterministic score-to-tier mapping, a fill-in template, and the exact confirmation output. Not 5 because the frontmatter promises PDF output while the body contains no PDF generation steps (only a pointer to '/geo report-pdf'), and 'update prospect record' lacks field-level specifics.

4 / 5

Workflow Clarity

Steps 1-3 are clearly sequenced and include an error-recovery path (missing audit → suggest '/geo quick' first). Not 5 because there is no validation checkpoint that all [PLACEHOLDERS] were actually replaced before declaring the document client-ready, leaving a silent placeholder-leakage risk in the final deliverable.

4 / 5

Progressive Disclosure

Sections are well-organized and navigable (Command, Workflow, Template, Output), but the ~240-line proposal template is precisely the content that belongs in a one-level-deep reference file, and no bundle files or references exist at all. Some structure with content that should be separate inlined — anchor 3 rather than 2 because the section organization itself is clear.

3 / 5

Total

14

/

20

Passed

Description

88%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 description: concrete, comprehensive deliverables in third-person voice with an explicit, well-specified trigger clause including multilingual synonyms. The only weaknesses are a few missing natural trigger variants and the generic weight of the word 'proposal' creating slight conflict risk with non-GEO document tasks.

DimensionReasoningScore

Specificity

Names the domain and enumerates the full deliverable set — 'executive summary, findings, recommended service packages (Basic/Standard/Premium), pricing, timeline, and terms' — in third-person voice, with no gaps in coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both questions: the 'what' via a concrete deliverable list ('Creates a full proposal in markdown and PDF including...') and the 'when' via an explicit 'Use when user says...' clause plus an event-based trigger ('after completing a GEO audit for a prospect').

5 / 5

Trigger Term Quality

Includes natural phrases ('proposal', 'generate proposal') plus multilingual synonyms ('proposta', 'offerta', 'preventivo'), but misses common variations like 'quote', 'estimate', or 'bid'. Good coverage, a few natural terms missing — matches anchor 4, not the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The GEO-proposal-from-audit niche is clear, but the bare trigger word 'proposal' is generic enough to also fire for non-GEO sales-document requests, giving minor overlap risk with general document-generation skills — anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

18

/

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