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

38%

Does it follow best practices?

Impact

92%

1.33x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/0d1e2f3a-4b5c-6d7e-8f9a-0b1c2d3e4f5a/SKILL.md

Quality

Content

27%

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

This skill is significantly over-engineered for what it delivers. It spends many tokens on meta-description (explaining what the skill does, when to use it, tips, related use cases) rather than providing concrete, tool-specific instructions for actually performing lead research. The output format template is the strongest element, but the lack of specific tool usage guidance (which search tools to use, how to verify information) and the excessive verbosity significantly reduce its effectiveness.

Suggestions

Remove the 'When to Use This Skill', 'What This Skill Does', 'Tips for Best Results', and 'Related Use Cases' sections entirely — they explain obvious concepts and waste tokens.

Add explicit tool usage instructions: specify that Claude should use web search to find companies, what search queries to construct, and how to verify company information.

Add a validation checkpoint after the research step (e.g., 'Verify at least 3 data points per lead before including in results; discard leads where key information cannot be confirmed').

Consolidate the 'How to Use' and 'Instructions' sections into a single concise workflow, eliminating the redundancy between describing the process and instructing on the process.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with many sections that explain obvious concepts Claude already knows (what lead research is, when to use it, what it does). The 'What This Skill Does' section is entirely redundant with the 'Instructions' section. The 'When to Use This Skill', 'Related Use Cases', and 'Tips for Best Results' sections add little actionable value. The entire file could be reduced to roughly 1/3 its size.	1 / 3
Actionability	The output format template is concrete and useful, and the step-by-step instructions provide some structure. However, there are no executable code examples (no actual search commands, no API calls, no concrete tool usage), and the skill doesn't specify which tools Claude should use to actually find leads (web search, specific APIs, etc.). The guidance remains largely descriptive rather than executable.	2 / 3
Workflow Clarity	The 7-step workflow is clearly sequenced and logically ordered, but lacks validation checkpoints. There's no guidance on what to do when searches return poor results, no verification step to confirm lead quality, and no feedback loop for refining the ICP if initial results don't match expectations. For a research task that could easily go wrong, these gaps are notable.	2 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files and no bundle structure. Multiple sections (When to Use, What This Skill Does, Related Use Cases, Tips) could be removed or consolidated. The output format template, examples, and detailed instructions are all inline when they could benefit from separation or at minimum better organization.	1 / 3
	Total	6 / 12 Passed

Description

50%

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 communicates the general domain of lead generation and lists some high-level actions, but lacks concrete specificity about outputs and methods. It is missing an explicit 'Use when...' clause, which limits Claude's ability to reliably select this skill. The use of second person ('your product', 'your business') also detracts from the expected third-person voice.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'find leads', 'prospecting', 'lead generation', 'identify potential customers', 'build a prospect list'.

List more concrete actions and outputs, e.g., 'Researches companies matching an ideal customer profile, compiles contact lists with names and emails, and drafts personalized outreach messages'.

Switch from second person ('your product', 'your business') to third person ('a given product or service', 'the user's business') to match expected voice conventions.

Dimension	Reasoning	Score
Specificity	Names the domain (lead generation) and some actions like 'analyzing your business', 'searching for target companies', and 'providing actionable contact strategies', but these are somewhat vague and not highly concrete (e.g., doesn't specify what outputs are produced or what specific analysis steps are taken).	2 / 3
Completeness	The 'what' is partially addressed (identifies leads, analyzes business, searches companies, provides contact strategies), but there is no explicit 'Use when...' clause or equivalent trigger guidance. The 'Perfect for...' phrase describes the audience, not when to invoke the skill.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'leads', 'sales', 'business development', 'marketing', and 'target companies', but misses common natural variations users might say such as 'prospecting', 'outreach', 'find customers', 'lead gen', 'pipeline', or 'ICP'.	2 / 3
Distinctiveness Conflict Risk	The lead generation focus provides some distinctiveness, but phrases like 'analyzing your business' and 'actionable contact strategies' are broad enough to overlap with general business analysis or marketing strategy skills.	2 / 3
	Total	8 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: majiayu000/claude-skill-registry-data
Commit: 5a9e167

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