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.
54
31%
Does it follow best practices?
Impact
92%
1.33xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/0d1e2f3a-4b5c-6d7e-8f9a-0b1c2d3e4f5a/SKILL.mdQuality
Discovery
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 the concrete specificity and explicit trigger guidance needed for reliable skill selection. It uses second person ('your product', 'your business'), which violates the third-person voice requirement. The absence of a 'Use when...' clause limits Claude's ability to confidently select this skill over similar ones.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'find leads', 'prospecting', 'identify potential customers', 'lead generation', 'outreach list'.
Replace second person ('your product', 'your business') with third person voice (e.g., 'Identifies high-quality leads by analyzing a business's target market').
List more concrete actions and outputs, such as 'compiles prospect lists with company details, identifies decision-maker contacts, drafts outreach email templates'.
| 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. The phrase 'Perfect for sales, business development, and marketing professionals' describes the audience, not when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'leads', 'sales', 'business development', 'marketing', and 'target companies', but misses common variations users might say such as 'prospecting', 'outreach', 'lead gen', 'find customers', 'B2B', or 'pipeline'. | 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 |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a lengthy, abstract description of a lead research process that reads more like a product requirements document than actionable instructions for Claude. It lacks any concrete mechanisms (tool calls, search strategies, specific commands) for actually finding leads, and explains many concepts Claude already understands. The output format template is useful but the overall document is far too verbose for the actionable content it delivers.
Suggestions
Replace abstract instructions like 'Search for companies matching the criteria' with concrete tool usage (e.g., specific web search queries to run, how to use browse tool to check company websites, specific search operators to find companies by criteria).
Cut the 'When to Use This Skill', 'What This Skill Does', 'Tips for Best Results', and 'Related Use Cases' sections entirely — these waste tokens on information Claude can infer.
Add concrete validation steps, such as verifying company websites are active, confirming company size claims, or cross-referencing multiple sources before scoring a lead.
Split the output format template and examples into a separate reference file to reduce the main skill's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with many sections that explain obvious concepts Claude already knows (what lead research is, what an ICP is, when to use this skill). The 'What This Skill Does' section is redundant with the 'Instructions' section. The output template, examples, tips, and related use cases add significant token bloat. Much of this could be cut by 60%+ without losing actionable content. | 1 / 3 |
Actionability | Despite its length, the skill provides no concrete, executable guidance. There are no actual tool calls, no specific search commands, no API endpoints, no code to run. The instructions are entirely abstract ('Search for companies matching the criteria', 'Look for signals of need') with no concrete mechanism for how Claude should actually find leads. The 'examples' describe expected outputs rather than showing actual executable steps. | 1 / 3 |
Workflow Clarity | The steps are clearly sequenced (understand product → define ICP → research → prioritize → output), and the output format template is well-structured. However, there are no validation checkpoints, no feedback loops for verifying lead quality, and no guidance on what to do when search results are insufficient or when the user's criteria are too broad/narrow. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files and no references to external resources. All content is inline in a single long document, including a full output template, multiple usage examples, tips, and related use cases that could be separated. The document is over 150 lines with no progressive structure. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
100%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
b1a95aa
- Reviewed
Table of Contents
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.