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

84%

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 orchestrator skill: the four-phase workflow is explicitly sequenced with user-confirmation checkpoints at every boundary, and the guidance is highly actionable via literal question blocks, search templates, and a fill-in context object. The only weaknesses are minor — a few trimmable rationale asides and a longish inline question bank/template that could live in a reference file.

Dimension	Reasoning	Score
Conciseness	The body is lean, structured instruction with no explanations of concepts Claude already knows, but contains minor trimmable asides: "it makes the output analysis 10x more useful" and parenthetical rationales like "a $500/yr tool targets different companies than a $50k/yr platform". Efficient with minor instances of over-explanation — the 4 anchor, not the every-token-earns-its-place 5.	4 / 5
Actionability	Guidance is copy-paste-ready for an instruction-only skill: literal question blocks, search-query templates ("[product category] alternatives", "[competitor name] vs"), a fill-in shared-context template, and concrete counts and costs (5-10 competitors, 3-8 repos, ~$5-10 Reddit, ~$0.05-0.20/lead). Specific examples cover the common cases with no gaps.	5 / 5
Workflow Clarity	Phases 1-4 are clearly sequenced and each ends in an explicit validation checkpoint: "ask them to confirm or correct", "Present your research findings to the user for confirmation before proceeding", "Ask them to confirm, add, or remove items", "Ask the user which sources they want to run". Confirm/correct feedback loops appear at every phase boundary, matching the top anchor.	5 / 5
Progressive Disclosure	Sections are well-organized and all content is core orchestration logic appropriately kept inline (no bundle files exist in references/, scripts/, or assets/). At ~175 lines with an inline question bank and context-object template, light extraction would tighten the overview — good structure with minor organization gaps rather than the ideal split of the 5 anchor.	4 / 5
	Total	18 / 20 Passed

Description

80%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 its orchestrator role, lists multiple concrete actions, and includes an explicit when-clause ("runs first for lead generation requests"). It falls just short of the top tier on triggers and completeness because it omits the natural phrasings users actually say ("find leads", "generate leads", "outbound", "prospects").

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — "Gathers business context via website analysis or questions", "identifies competitors", "builds ICP", "routes to signal skills with pre-filled inputs" — comprehensively covering the orchestration flow. Coverage of its stated scope is complete rather than having minor gaps, so it matches the top anchor.	5 / 5
Completeness	Both what (gather context, identify competitors, build ICP, route to signal skills) and when ("runs first for lead generation requests") are present, satisfying explicit trigger guidance, so the 3-cap does not apply. The when could be more specific — it lacks concrete trigger phrases like "find leads" or "do outbound" that would earn a 5.	4 / 5
Trigger Term Quality	"lead generation requests", "website", "competitors", and "signal skills" are natural terms users would say, but common variations like "outbound", "prospects", or "B2B" are absent (they appear only in the body, not the description). Good coverage with a few natural terms missing — not the comprehensive synonym coverage of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	"Orchestrator that runs first for lead generation requests" carves a clear niche, but "routes to signal skills" creates minor overlap risk with the sibling signal skills (github-repo-signals, job-signals, etc.) for requests like "scan this repo for leads". Mostly distinct with minor overlap against closely related skills — the 4 anchor.	4 / 5
	Total	17 / 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: a9f4676

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