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.

1.33x

Quality

63%

Does it follow best practices?

Impact

92%

1.33x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./data/0d1e2f3a-4b5c-6d7e-8f9a-0b1c2d3e4f5a/SKILL.md

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, instruction-only skill with a clear workflow and concrete output format, but it is padded by redundant intro sections and vague on the actual lead-sourcing mechanics. No bundle files are present, and structure is good.

Suggestions

Consolidate the redundant intro sections ('When to Use This Skill', 'What This Skill Does', and the opening paragraph) into a single concise overview to cut tokens.

Add concrete research methods or data sources for finding leads (e.g. specific job-board searches, GitHub-repo signals, news/funding sources) instead of generic 'search for companies' guidance.

Insert an explicit verification checkpoint in the workflow (e.g. 'Confirm each lead still matches the ICP and validate decision-maker titles before output') to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body restates its purpose across three overlapping intro sections (opening paragraph, 'When to Use This Skill', 'What This Skill Does') and includes a long output template, which is more than minor padding though it avoids explaining basic concepts.	3 / 5
Actionability	Output guidance is concrete (named fields, 1-10 scoring, markdown template, worked examples), but the core research mechanics are vague ('Search for companies matching the criteria', 'Look for signals of need') with no specific sources or methods.	3 / 5
Workflow Clarity	A clear 7-step sequence (Understand Product, Define ICP, Research, Score, Provide Output, Format, Next Steps) is well ordered, but there are no explicit verification checkpoints before emitting the lead list.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well organized with clear section headers, though at ~195 lines it exceeds the 50-line simple-skill threshold and keeps some content (full output template, examples) inline that could be split out.	4 / 5
	Total	14 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 a clear purpose and audience with several concrete actions, but lacks an explicit 'Use when...' trigger clause, which limits its completeness. Trigger terms are good but could add common synonyms.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g. 'Use when finding sales leads, building prospect lists, or researching target companies for outreach.'

Broaden trigger term coverage with synonyms like 'prospects', 'lead generation', and 'find customers' so it matches more natural phrasings.

Tighten the action verbs toward more granular specifics (e.g. 'enriches decision-maker contact info' rather than 'providing actionable contact strategies') to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Names three concrete actions ('analyzing your business', 'searching for target companies', 'providing actionable contact strategies'), but they sit at a higher abstraction than the granular anchor-5 examples, leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clear, but there is no explicit 'Use when...' clause; the 'when' is only weakly implied via the audience phrase 'Perfect for sales, business development, and marketing professionals', which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('leads', 'target companies', 'sales', 'business development', 'marketing'), but misses common variations such as 'prospects', 'lead generation', or 'find customers'.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (lead research for sales/BD) with distinct triggers, carrying only minor overlap risk with general company-research or outreach skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: majiayu000/claude-skill-registry-data
Path: data/0d1e2f3a-4b5c-6d7e-8f9a-0b1c2d3e4f5a/SKILL.md
Commit: a1e9f44

Reviewed: about 18 hours ago

Table of Contents

Discovery Implementation Validation

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.