lead-discovery

Orchestrator that runs first for lead generation requests. Gathers business context via website analysis or questions, identifies competitors, builds ICP, and routes to signal skills with pre-filled inputs.

Quality

86%

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

Quality

Content

88%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 well-structured, actionable orchestration skill with clear phased workflow and confirmation checkpoints. The main improvement is trimming the redundant Key Rules section and considering whether the context template warrants a separate reference file.

Suggestions

Collapse the 'Key Rules' section into the relevant phases or remove rules already stated inline to reduce redundancy.

Consider extracting the shared context object template and/or question banks into a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-organized, but the 'Key Rules' section reiterates guidance already stated in the phases (ask in blocks, reuse context, cost transparency), which could be trimmed.	4 / 5
Actionability	Highly actionable for an instruction-only skill: specific extraction fields, numbered question blocks, concrete search-query patterns, a copy-paste-ready shared context object template, and named skills with cost figures.	5 / 5
Workflow Clarity	The four phases are clearly sequenced with explicit user-confirmation checkpoints after each phase ('ask them to confirm or correct', 'for confirmation before proceeding'), and the shared context object acts as a checklist.	5 / 5
Progressive Disclosure	Good single-file structure with clear section headers and cohesive interdependent phases, but at ~167 lines with no bundle files, some content (e.g., the shared context template or question banks) could optionally be split out.	4 / 5
	Total	18 / 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, third-person description that names several concrete actions and a clear trigger context. It would reach the top level by adding explicit 'Use when...' phrasing with natural user terms like 'find leads' or 'do outbound'.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'find leads', 'generate leads', 'do outbound', 'find prospects').

Include common synonyms such as 'prospects' and 'outbound' alongside 'lead generation' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Gathers business context via website analysis or questions, identifies competitors, builds ICP, and routes to signal skills with pre-filled inputs' — giving comprehensive coverage of the orchestrator's behavior.	5 / 5
Completeness	The 'what' is clear (gathers context, identifies competitors, builds ICP, routes) and 'when' is present via 'runs first for lead generation requests', but it lacks an explicit 'Use when...' clause with concrete trigger phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	'lead generation requests' and 'signal skills' are relevant, but common natural phrases users actually say ('find leads', 'prospects', 'outbound') are absent from the description.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche as the orchestrator entry point distinct from the downstream signal skills it routes to, with minimal conflict risk.	5 / 5
	Total	18 / 20 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: gooseworks-ai/goose-skills
Path: skills/lead-generation/packs/lead-gen-devtools/lead-discovery/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.