CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

geo-prospect

CRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit history, notes, deal values, and generate pipeline summaries. Use when user says "prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi cliente", or when managing the business side of GEO services.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 highly actionable, well-structured instruction skill: exact command syntax, per-command numbered procedures, a concrete data schema, and explicit storage layout. Its main weakness is absent validation/feedback loops for the JSON database mutations (status changes, won/lost transitions, note appends), which caps workflow clarity.

Suggestions

Add validation checkpoints to database-mutating workflows: verify the prospect exists before updating, confirm the JSON parses after each save, and confirm with the user before irreversible won/lost transitions.

Include an error-recovery path for common failures (unknown ID/domain, prospects.json missing or corrupted) so Claude knows to re-check and retry rather than proceed blindly.

Trim the second ASCII mockup in '/geo prospect pipeline' or the duplicated list output, since both illustrate the same rendering style and partially repeat the same information.

DimensionReasoningScore

Conciseness

Efficient and free of concept over-explanation, but the two long ASCII output mockups and the full example JSON record duplicate information and could be trimmed, keeping it below the lean anchor 5 while clearly above anchor 3's unnecessary explanations.

4 / 5

Actionability

Copy-paste-ready command table, numbered orchestration steps per command, exact storage paths, a concrete mkdir command, and a specific decision threshold ("If score < 55…") fully cover the common cases for an instruction-only skill.

5 / 5

Workflow Clarity

Steps are clearly sequenced per command, but every workflow mutates the prospects.json database with no validation checkpoints — no existence check before updates, no post-save verification, and no confirmation before semi-destructive won/lost transitions — which per the scoring notes caps database-operation workflows at 3.

3 / 5

Progressive Disclosure

No bundle files exist, and the body is well organized into clearly navigable sections (Commands, Data Structure, Orchestration Instructions, Storage, Stage Definitions) with only minor organization gaps such as interleaving output examples with instructions.

4 / 5

Total

16

/

20

Passed

Description

83%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: it states concrete capabilities in third person, defines the pipeline stages, and includes an explicit 'Use when' clause with natural trigger terms in both English and Italian. The only weaknesses are a few missing common synonyms (customer, deal, sales) and uncovered capabilities (audits, won/lost transitions).

DimensionReasoningScore

Specificity

Lists several concrete actions ("Track leads through the full sales pipeline", "Store audit history, notes, deal values", "generate pipeline summaries") with only minor gaps — running audits and won/lost status transitions are not mentioned, keeping it below the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both what ("CRM-lite… Track leads… Store… generate pipeline summaries") and when ("Use when user says 'prospect', 'lead', 'client'…") with concrete trigger phrases, matching the top anchor exactly; it is clearly not anchor 4 since the 'when' clause is fully explicit.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi cliente") including synonym and Italian variants, but common terms like "customer", "deal", and "sales" are missing, so it falls short of anchor 5's comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The GEO-agency sales niche with domain-specific triggers is mostly distinct, but broadly generic terms like "client", "pipeline", and "crm" carry minor overlap risk with general sales/business skills, placing it just below anchor 5.

4 / 5

Total

17

/

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