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 sales prospecting but lacks the precision and explicit trigger guidance needed for reliable skill selection. It uses second-person voice ('your product', 'your business') which is discouraged, and the 'Perfect for...' clause describes the audience rather than providing actionable selection criteria. The description would benefit from more concrete actions and an explicit 'Use when...' clause.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'find leads', 'prospecting', 'identify potential customers', 'lead generation', 'outreach strategy', 'B2B sales'.
Replace vague phrases like 'analyzing your business' and 'actionable contact strategies' with specific concrete actions such as 'researches company profiles, identifies decision-makers, generates outreach email templates, and scores leads by fit'.
Switch from second-person voice ('your product', 'your business') to third-person voice ('Identifies high-quality leads by analyzing a given business profile and searching 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 could be more narrowly scoped. | 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 and descriptive rather than actionable. It spends significant tokens explaining what the skill does and when to use it — information Claude can infer — while lacking specifics on how to actually execute the research (which tools to use, which APIs to call, how to search). The output template is the strongest element, but the overall content reads more like a product description than an operational guide.
Suggestions
Remove the 'When to Use This Skill', 'What This Skill Does', 'Tips for Best Results', and 'Related Use Cases' sections — these describe rather than instruct and waste tokens on things Claude can infer.
Add specific tool usage instructions: which search tools to use (e.g., web_search), what queries to run, and how to verify results. The 'Research and Identify Leads' step is too vague without this.
Add validation checkpoints: e.g., 'After identifying initial leads, present 2-3 to the user for feedback before completing the full list' to ensure the ICP interpretation is correct.
Consider splitting the detailed output template and examples into a referenced file to keep the main skill lean and focused on the core workflow.
| 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 output template and step-by-step workflow, which is somewhat concrete. However, there's no executable code, no specific tool usage instructions (e.g., which search tools to use, how to query them), and the 'Research and Identify Leads' step is vague about how to actually find companies. The examples are illustrative summaries rather than concrete demonstrations. | 2 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (understand product → define ICP → research → prioritize → output), but there are no validation checkpoints. No guidance on what to do if search results are poor, how to verify lead quality, or when to ask the user for clarification mid-process. The workflow reads more like a description of activities than an actionable process. | 2 / 3 |
Progressive Disclosure | Content is organized with clear headers and sections, but it's monolithic — everything is in one long file with no references to external files. The output template, examples, and detailed instructions could be split into separate referenced documents. The 'Related Use Cases' section at the end hints at content that could be linked but isn't. | 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
6770aaa
- 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.