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
95%
1.20xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/lead-research-assistant/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 conveys the general purpose of lead generation and names a few actions, but lacks the specificity and explicit trigger guidance needed for reliable skill selection. It uses second person ('your product or service', 'your business') which is a style issue, and the 'Perfect for...' clause describes the audience rather than providing actionable trigger conditions.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'find leads', 'prospecting', 'identify potential customers', 'lead generation', 'outreach list'.
Replace vague phrases like 'analyzing your business' and 'actionable contact strategies' with concrete actions such as 'builds prospect lists with company names, contact info, and outreach templates'.
Switch from second person ('your product') to third person ('a given product or service') to match the expected voice.
| 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 is done). | 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 'Perfect for...' phrase 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
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, high-level description of a lead research process that reads more like a product requirements document than an actionable skill for Claude. It lacks concrete tool usage instructions (which search tools, APIs, or MCP servers to use), contains significant redundancy between sections, and explains many concepts Claude already understands. The output format template is useful but the skill fundamentally fails to tell Claude *how* to actually find leads.
Suggestions
Specify exactly which tools Claude should use to find leads (e.g., web_search, specific MCP servers, browser tool) with concrete examples of search queries and how to parse results.
Remove the 'When to Use This Skill', 'What This Skill Does', 'Tips for Best Results', and 'Related Use Cases' sections — these are marketing copy, not actionable instructions.
Consolidate the 'How to Use' and 'Instructions' sections into a single lean workflow with explicit tool calls at each step.
Move the output format template to a separate reference file or reduce it to a brief description, as Claude can generate well-structured markdown without a 30-line template.
| 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 bulk. 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 specific tools, APIs, commands, or code to run. Instructions like 'Search for companies matching the criteria' and 'Look for signals of need' are vague directions, not actionable steps. There's no indication of which tools Claude should use (web search, specific APIs, etc.) to actually find leads. | 1 / 3 |
Workflow Clarity | The steps are clearly numbered and 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 when searches yield poor results, and no guidance on what to do when information is unavailable or unreliable. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no bundle files to support it. Multiple sections (What This Skill Does, Instructions, Examples, Tips, Related Use Cases) could be consolidated or split out. The output template alone takes up significant space that could be in a separate reference file. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
857fe3a
- 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.