lead-research-assistant

Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.

1.33x

Quality

—

Does it follow best practices?

Impact

92%

1.33x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

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 body is well-structured and gives a clear end-to-end lead-research workflow with a usable output template, but it is verbose, lacks validation checkpoints in its batch workflow, and keeps all detail inline rather than splitting reference material into separate files.

Suggestions

Add a verification step to the workflow (e.g., confirm each lead's signals and contact info before presenting) to satisfy the batch-operation feedback-loop requirement.

Trim redundant sections — fold "What This Skill Does" into "Instructions" and consolidate "When to Use" with the description to reduce token cost.

Move the full output template and worked examples into separate referenced files (e.g., OUTPUT_TEMPLATE.md, EXAMPLES.md) and keep SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The ~195-line body is mostly efficient structured guidance but contains padding: "When to Use" overlaps the description, "What This Skill Does" recapitulates "Instructions," and the Tips/Related/Example sections add length that could be trimmed.	2 / 3
Actionability	Provides a concrete output template and specific factors (1-10 fit scores, decision-maker roles), but guidance is placeholder/template-driven and several steps are descriptive ("Search for companies matching the criteria") rather than commanding specific actions.	2 / 3
Workflow Clarity	A clear 7-step sequence is present, but there are no validation or verification checkpoints, which is a gap for batch lead generation and caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Sections are well-organized with headers, but the single ~195-line file is somewhat monolithic — the full output template and example sections are inline content that could be split into referenced files.	2 / 3
	Total	8 / 12 Passed

Description

60%

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 clearly states concrete capabilities and names its domain, but it lacks an explicit trigger clause and relies on only moderately distinct keywords, which limits its usefulness for skill selection.

Suggestions

Add an explicit "Use when..." clause naming natural user phrasings such as finding leads, building a prospect list, or identifying target accounts.

Replace fluffy qualifiers ("high-quality," "actionable") with more concrete capability verbs to sharpen specificity.

Differentiate from generic research skills by mentioning distinctive triggers like ideal-customer-profile matching or outreach/contact strategy generation.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "analyzing your business, searching for target companies, and providing actionable contact strategies" — matching the anchor for several specific actions, though "high-quality" and "actionable" are mildly fluffy.	3 / 3
Completeness	Answers "what" clearly but "when" is only implied via the audience clause "Perfect for sales, business development, and marketing professionals"; with no explicit "Use when..." trigger, completeness is capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	Includes relevant domain terms ("leads," "sales," "business development," "marketing") but omits the natural phrasing users actually say (e.g. "find me leads," "find customers") and offers no keyword variations.	2 / 3
Distinctiveness Conflict Risk	Lead research is a recognizable niche, but the triggers are generic enough (sales/marketing research) to overlap with general research skills rather than forming distinct, conflict-free triggers.	2 / 3
	Total	9 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: majiayu000/claude-skill-registry
Commit: 8271354

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