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

90%

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

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Actionable and concise instruction content with concrete steps and output formats, but workflows that write to the persistent JSON database lack validation/error-handling checkpoints, and the single-file body carries inline detail that could be split into references.

Suggestions

Add validation/feedback steps to the database-mutating commands: verify the prospect exists before status/note/audit updates, and re-read the JSON file after writing to confirm validity before confirming to the user.

Extract the detailed per-command orchestration and the ASCII pipeline/list output templates into a references file (e.g., COMMANDS.md) referenced from the body, leaving the SKILL.md as a concise overview with the command table and data structure.

Define explicit not-found and invalid-status error handling for `status`, `note`, and `audit` commands rather than assuming the prospect always resolves.

Dimension	Reasoning	Score
Conciseness	The body is lean and instruction-focused — command tables, a JSON schema, numbered orchestration steps, and a storage tree — without padding in concepts Claude already knows; the ASCII mockups illustrate concrete output rather than over-explaining.	3 / 3
Actionability	It provides concrete executable guidance per command: exact file paths, sequential IDs, a `mkdir -p` command, the full JSON record shape, and precise output formats, satisfying the instruction-only-skill expectation.	3 / 3
Workflow Clarity	Steps are clearly sequenced for each command, but operations that mutate the persistent JSON database (status, audit, note) lack validation checkpoints or error handling (e.g., prospect-not-found, JSON validity after write), which the rubric caps at 2 for database operations.	2 / 3
Progressive Disclosure	The skill is well-sectioned but is a single ~180-line file with no bundle files or one-level-deep references; the per-command orchestration and verbose ASCII pipeline mockups are inline content that could be externalized or trimmed, exceeding the 50-line simple-skill exception.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, specific description that clearly states capabilities, provides natural trigger terms including language variations, and explicitly covers both the what and the when in third-person voice. No substantive weaknesses to address.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ("Track leads through the full sales pipeline", "Store audit history, notes, deal values", "generate pipeline summaries") rather than vague abstractions.	3 / 3
Completeness	It explicitly answers both what it does (manage prospects, track pipeline, store data, generate summaries) and when to use it via the explicit "Use when user says…" clause.	3 / 3
Trigger Term Quality	It gives natural terms a user would actually say ("prospect", "lead", "client", "pipeline", "crm") plus Italian variations ("nuovo prospect", "aggiungi cliente"), covering common phrasings.	3 / 3
Distinctiveness Conflict Risk	The GEO-agency CRM niche plus distinctive Italian trigger phrases make it unlikely to fire for unrelated skills; it uses third-person imperative voice with no first/second person.	3 / 3
	Total	12 / 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-prospect/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.