sales-prospecting

Build targeted prospect lists with verified contact information

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/lead-generation/capabilities/sales-prospecting/SKILL.md

Quality

Content

50%

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

The content is well-sequenced and action-oriented but is held back by malformed, non-executable JSON payloads, duplicated pipeline content, and the absence of validation checkpoints. Fixing the JSON syntax and adding verify-before-proceed feedback loops would most improve the score.

Suggestions

Fix the malformed JSON in the curl -d payloads so each request body is a single valid, copy-paste-ready JSON object (the 'query'/'searchParams'/'lead' keys are currently orphaned outside the quoted JSON).

Remove or consolidate the 'Prospecting Pipeline' section, which duplicates the Step 1-6 endpoints, to eliminate redundant tokens.

Add explicit validation checkpoints, e.g. 'Only add leads to a sequence after Step 5 email verification passes', with a retry-on-failure feedback loop for batch operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude already knows, but the 'Prospecting Pipeline' section largely duplicates the Step 1-6 endpoints (company-search, people-search, domain-search, validate-email), so it could be tightened and not every token earns its place.	2 / 3
Actionability	It provides concrete curl commands against real endpoints, but the JSON payloads in Steps 1, 2, 4, and the Prospecting Pipeline are malformed — the -d string closes early and the 'query'/'searchParams'/'lead' objects sit outside the quoted JSON, so the commands are not executable or copy-paste ready as written.	2 / 3
Workflow Clarity	Steps are clearly sequenced (define companies, find decision makers, get emails, verify, enrich), but there are no validation checkpoints or feedback loops for the batch prospect-list build or email verification, which caps workflow clarity at 2 per the rubric's batch-operation guidance.	2 / 3
Progressive Disclosure	The skill is sectioned (Setup, Workflow, Prospecting Pipeline, Tips, Discover More) with no nested references, but at ~170 lines it exceeds the simple-skill threshold and keeps API endpoint reference content inline rather than splitting it to a clearly signaled one-level-deep reference file.	2 / 3
	Total	8 / 12 Passed

Description

57%

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 distinctive but falls short on trigger coverage and completeness. Adding an explicit 'Use when...' clause with broader natural trigger terms would raise the completeness and trigger_term_quality scores.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building lead lists, finding verified emails, or enriching prospect data for outreach.'

Broaden trigger terms to include common variations users would say, such as 'lead lists', 'verified emails', and 'B2B leads'.

Expand the action list beyond a single verb to name multiple concrete actions, e.g. 'Build targeted prospect lists, find decision-makers, and verify contact information.'

Dimension	Reasoning	Score
Specificity	The phrase 'Build targeted prospect lists with verified contact information' names a concrete domain and one action verb ('Build'), but 'with verified contact information' describes an output attribute rather than listing multiple distinct actions, so it is not comprehensive enough for a 3.	2 / 3
Completeness	It states what the skill does (build prospect lists with verified contacts) but provides no 'Use when...' trigger clause or equivalent explicit guidance on when to invoke it, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	It includes some natural terms a user might say ('prospect lists', 'contact information', 'prospecting'), but misses common variations like 'lead lists', 'verified emails', or 'B2B leads', giving partial rather than broad coverage.	2 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche (sales prospecting / verified contact data) with distinct triggers that are unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/lead-generation/capabilities/sales-prospecting/SKILL.md
Commit: 8866b2a

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.