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.
60
Quality
41%
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
32%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 purpose of lead identification but suffers from lack of explicit trigger guidance and somewhat vague action descriptions. It uses second person voice ('your product', 'your business') which violates the third-person requirement. The 'Perfect for...' clause describes audience rather than selection criteria, making it harder for Claude to know when to choose this skill.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'find leads', 'prospecting', 'identify potential customers', 'B2B outreach', 'sales pipeline'
Rewrite in third person voice: 'Identifies high-quality leads by analyzing business context...' instead of 'your product or service'
Add more specific concrete actions such as 'research company profiles', 'identify decision-makers', 'draft outreach emails', 'score lead quality'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domain (lead identification) and some actions ('analyzing your business, searching for target companies, providing actionable contact strategies'), but actions remain somewhat abstract rather than listing concrete specific capabilities like 'scrape LinkedIn profiles' or 'generate email templates'. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or explicit trigger guidance. The phrase 'Perfect for...' describes target users, not when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'when' is so weak it warrants a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'leads', 'sales', 'business development', 'marketing', but misses common variations users might say such as 'prospecting', 'find customers', 'B2B outreach', 'lead gen', or 'cold outreach'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to lead generation/sales domain, but could overlap with general business analysis skills, CRM tools, or marketing automation skills. The broad terms 'analyzing your business' and 'contact strategies' increase conflict risk. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive framework for lead research but suffers from verbosity and lack of concrete tooling guidance. It explains what to do conceptually but doesn't specify how to actually search for companies or validate results. The structure is clear but would benefit from being more concise and including specific tool usage instructions.
Suggestions
Add specific tool/method instructions for company research (e.g., web search queries, specific data sources, or APIs to use for finding companies)
Remove or significantly condense the 'When to Use This Skill' and 'What This Skill Does' sections - Claude can infer these from the instructions
Add validation checkpoints such as 'Verify at least 3 data points per lead before including' or 'If fewer than X leads found, broaden search criteria'
Move the detailed output format template and examples to a separate reference file, keeping only a brief format summary in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains significant verbosity with sections like 'When to Use This Skill' and 'What This Skill Does' that explain obvious concepts Claude already understands. The detailed output format template and extensive examples add bulk that could be condensed. | 2 / 3 |
Actionability | The skill provides structured guidance and output templates, but lacks concrete executable code or specific tool commands. Instructions like 'Search for companies matching the criteria' are vague about HOW to actually perform the search (which tools, APIs, or methods to use). | 2 / 3 |
Workflow Clarity | The 7-step process is clearly sequenced, but lacks validation checkpoints. There's no guidance on verifying lead quality, handling cases where searches return poor results, or feedback loops for refining the ICP when initial results don't match expectations. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is monolithic with no references to external files. The extensive output format template and multiple examples could be split into separate reference files to keep the main skill leaner. | 2 / 3 |
Total | 8 / 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
6213d1a
- 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.