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 ./skills/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 sales prospecting but lacks the specificity and explicit trigger guidance needed for reliable skill selection. It uses second-person voice ('your product or service', 'your business') which is discouraged, and the 'Perfect for...' clause describes the audience rather than providing actionable selection criteria. The description would benefit from concrete actions, explicit 'Use when...' triggers, and more natural keyword variations.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'find leads', 'prospecting', 'lead generation', 'find potential customers', 'B2B outreach', 'sales pipeline'.
Replace vague phrases like 'providing actionable contact strategies' with concrete outputs such as 'generates prospect lists with company details, decision-maker contacts, and personalized outreach templates'.
Switch from second-person voice ('your product', 'your business') to third-person voice ('Analyzes a given business profile', 'Searches for target companies').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (lead generation/sales) 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 occur). | 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 strategy or marketing skills. The description doesn't carve out a sufficiently narrow niche. | 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 extremely verbose and lacks actionable, concrete guidance. It reads more like a product description or user manual than an instruction set for Claude. The core problem is that it describes WHAT to do at length but never specifies HOW—there are no tool calls, search strategies, or executable steps that Claude can follow to actually find and research leads.
Suggestions
Replace abstract instructions ('Search for companies matching the criteria') with concrete tool usage—specify which tools Claude should use (web search, file reading) and provide example queries/commands.
Cut the 'When to Use This Skill', 'What This Skill Does', 'Tips for Best Results', and 'Related Use Cases' sections entirely—they add no actionable value and waste tokens.
Add validation checkpoints such as confirming the ICP with the user before searching, and verifying search results meet minimum quality thresholds before presenting.
Move the detailed output format template to a separate reference file and keep only a brief summary in the main skill body.
| 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') without specifying HOW Claude should actually perform these searches. The 'examples' describe expected outputs rather than showing actual execution. | 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 | The content is a monolithic wall of text with no references to external files and no bundle structure. Everything is inline in a single long document, including the full output template, all examples, tips, and related use cases. Content like the output template and detailed examples could be split into separate reference files. | 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
- Commit
d156cd1
- 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.