sales-prospecting

Build targeted prospect lists with verified contact information

Quality

51%

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%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 body provides a concrete, well-sectioned prospecting workflow but ships with malformed, non-executable JSON in almost every example and no validation checkpoints for batch email operations. Fixing the JSON payloads and removing the duplicated pipeline section are the highest-impact improvements.

Suggestions

Fix every -d JSON body so the examples are copy-paste executable: close all braces and move query/searchParams fields inside the JSON object (e.g. Step 1's "query" and Step 2's "searchParams").

Remove the redundant "Prospecting Pipeline" section or replace it with a brief orchestration note that references Steps 1-4 instead of duplicating them.

Add explicit validation feedback loops, e.g. after Step 5 verify email deliverability and only proceed to outreach when valid, retrying enrichment on failure.

Dimension	Reasoning	Score
Conciseness	Prose is mostly efficient, but the "Prospecting Pipeline" section duplicates Steps 1-4 verbatim and could be tightened, matching the anchor for mostly efficient content with some unnecessary material.	3 / 5
Actionability	Concrete curl commands with real parameters are provided, but nearly every JSON body is malformed (mismatched braces, fields placed outside the -d JSON string), so the examples are not executable as written, fitting the anchor for concrete guidance with missing key details.	3 / 5
Workflow Clarity	Steps 1-6 are sequenced, but there are no validation checkpoints or feedback loops, and email verification plus lead enrichment are batch operations, which per the judging guideline caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	The skill is a single inline file with no bundle files and reasonable section headers, but content that could live in a separate reference (the endpoint catalog) is inlined and the "Discover More" section is muddled, fitting the 3 anchor.	3 / 5
	Total	12 / 20 Passed

Description

53%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.

The description is concise and names concrete actions but lacks any "Use when..." trigger guidance and omits common natural-language keywords, so it lands at the midpoint across most dimensions. Adding explicit trigger phrasing and synonyms would lift completeness and trigger-term quality.

Suggestions

Append a "Use when..." clause naming concrete triggers (e.g. "Use when building lead lists, finding B2B contacts, or verifying prospect emails").

Add natural synonyms users actually say, such as "lead lists", "find emails", and "decision-maker contacts".

Specify one or two more concrete actions (e.g. "enrich with company data") to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Build targeted prospect lists with verified contact information" names the domain and two concrete actions (build lists, verify contacts) but is not comprehensive, matching the anchor for domain plus 1-2 concrete actions; it lacks the multiple specific actions of a 4.	3 / 5
Completeness	It gives a clear "what" (build prospect lists with verified contact information) but no "Use when..." clause, so per the judging guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	"prospect lists" and "verified contact information" are relevant domain keywords but common user phrasings like "find emails", "lead lists", or "B2B contacts" are missing, matching the anchor for some relevant keywords without common variations.	3 / 5
Distinctiveness Conflict Risk	"targeted prospect lists" carves a fairly distinct sales-prospecting niche with minor overlap risk against generic CRM/contact skills, fitting just above the 3 anchor but without the fully distinct triggers of a 5.	4 / 5
	Total	13 / 20 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: 2523432

Reviewed: 7 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.