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.
61
42%
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 names a few high-level actions, but lacks the concrete specificity and explicit trigger guidance needed for reliable skill selection. It uses second person ('your product or service', 'your business'), which violates the third-person voice requirement. The absence of a 'Use when...' clause and natural trigger term variations limits its effectiveness in a multi-skill environment.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'find leads', 'prospecting', 'identify potential customers', 'lead generation', 'outreach list', 'ICP'.
Replace second-person voice ('your product', 'your business') with third-person descriptions (e.g., 'Analyzes a business profile to identify high-quality leads').
List more concrete outputs and actions, such as 'generates ranked prospect lists, identifies decision-maker contacts, suggests personalized outreach messaging'.
| 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 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 or equivalent trigger guidance. The phrase 'Perfect for sales, business development...' 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 |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is overly verbose, spending many tokens on descriptions of what the skill does and when to use it rather than focusing on actionable instructions. The output format template is a strength, but the lack of specific tool usage guidance (e.g., which MCP tools or web search commands to use for finding leads) significantly weakens actionability. The content would benefit from aggressive trimming and adding concrete tool/command references.
Suggestions
Remove the 'When to Use This Skill', 'What This Skill Does', 'Tips for Best Results', and 'Related Use Cases' sections entirely—these describe obvious context that wastes tokens.
Specify concrete tools to use for research (e.g., web_search queries, specific search patterns like 'site:linkedin.com/company [industry] [location]') instead of vague 'search for companies matching criteria'.
Add validation checkpoints: e.g., 'After identifying 5 leads, confirm with the user that the direction matches their expectations before researching the remaining leads.'
Move the detailed output format template to a separate TEMPLATE.md file and reference it from the main skill to reduce the SKILL.md size.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with significant padding. Sections like 'When to Use This Skill', 'What This Skill Does', 'Related Use Cases', and 'Tips for Best Results' explain obvious concepts Claude already understands. The entire file could be reduced to ~30% of its current size without losing actionable information. | 1 / 3 |
Actionability | Provides a structured workflow and output template which is somewhat concrete, but lacks executable code/commands. The 'research and identify leads' step is vague—it says 'search for companies' without specifying which tools to use (web search, specific APIs, etc.). The examples describe outputs conceptually rather than showing actual concrete results. | 2 / 3 |
Workflow Clarity | Steps are listed in a clear sequence (understand product → define ICP → research → prioritize → output), but there are no validation checkpoints or feedback loops. No guidance on what to do when search results are poor, when the user's ICP is too narrow/broad, or how to verify lead quality before presenting results. | 2 / 3 |
Progressive Disclosure | Content is structured with headers and sections, but everything is in one monolithic file with no references to external files. The output template, examples, and detailed instructions could be split into separate reference files. The inline content is quite long for a single SKILL.md. | 2 / 3 |
Total | 7 / 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
3dd3ac0
- 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.