CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

73

1.33x
Quality

69%

Does it follow best practices?

Impact

92%

1.33x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/lead-research-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body is a well-organized, actionable instruction skill: a clearly sequenced 7-step workflow, a concrete output contract, and two worked examples. Its main weaknesses are token inefficiency — the workflow is described twice ('What This Skill Does' vs 'Instructions') and the long output template and examples are inlined rather than split into reference files — and the absence of any validation checkpoint before presenting batch research results.

Suggestions

Merge 'What This Skill Does' (items 1–5) with the 'Instructions' workflow — they describe the same process twice and could be collapsed into one section, the single biggest token saving.

Move the ~40-line output template and the Examples section into references/output-template.md and references/examples.md, keeping one condensed example inline — this would raise progressive_disclosure given no bundle files currently exist.

Add a validation step before presenting results, e.g. re-check each lead against the ICP criteria and drop or down-rank any without at least two concrete fit signals, tightening the batch output.

DimensionReasoningScore

Conciseness

Quotes: 'What This Skill Does' (items 1–5: Understands Your Business, Identifies Target Companies, Prioritizes Leads, Provides Contact Strategies, Enriches Data) and 'Instructions' (steps 1–7) enumerate the same workflow twice, and 'Tips for Best Results' plus 'Related Use Cases' add further padding. This is 'mostly efficient but could be tightened' — it never explains concepts Claude already knows and stays well-structured, so it does not fall to the 2 anchor's 'several unnecessary explanations'.

3 / 5

Actionability

Quotes: 'Create a fit score (1-10) for each lead', the full copy-paste markdown output template specifying every required field (Company Name, Priority Score, Decision Maker, LinkedIn URL, Conversation Starters), and two worked examples with concrete user prompts. The guidance is concrete and executable, but a few directions remain abstract ('Check for budget indicators', 'Consider growth indicators (funding, expansion, hiring)') without how to verify them, keeping it just below the fully-executable 5 anchor.

4 / 5

Workflow Clarity

Quotes: the seven sequenced instruction steps ('1. Understand the Product/Service' → '7. Offer Next Steps') with the explicit checkpoint 'Ask clarifying questions about the value proposition' early in step 1. Sequence and most checkpoints are present, matching the 4 anchor; it is not 5 because there is no validation of lead fit or data accuracy before presenting the batch of results, only a weak 'If available' qualifier on LinkedIn URLs.

4 / 5

Progressive Disclosure

Quotes: the ~40-line inline output template under '6. Format the Output' and the full 'Examples' section are prime content for separate reference files, and none exist — the skill ships no references/, scripts/, or assets/ at all. This matches anchor 3 ('content that should be separate is inline'); it is not 4 because at ~195 lines the skill far exceeds the under-50-lines simple-skill case, and not 2 because headers are clear and nothing is deeply nested or buried.

3 / 5

Total

14

/

20

Passed

Description

58%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 has a clear, concrete statement of what the skill does and occupies a reasonably distinct niche, but it completely lacks an explicit 'Use when...' trigger clause — the trailing audience sentence ('Perfect for...') names who it's for, not when to invoke it. Natural trigger phrasings users would actually say ('find leads', 'prospecting', 'lead generation', 'potential customers') are also missing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to find prospects, generate a lead list, or research companies that match their ideal customer profile.' — this would raise completeness from its current cap of 3.

Include natural synonyms users actually say — 'lead generation', 'prospecting', 'potential customers', 'B2B outreach', 'sales pipeline' — alongside the current 'leads' and 'target companies'.

Tighten 'analyzing your business' to a more concrete action such as 'analyzing your product, value proposition, and ideal customer profile' to sharpen specificity.

DimensionReasoningScore

Specificity

Quotes: 'analyzing your business, searching for target companies, and providing actionable contact strategies' — several distinct actions listed, matching the 'lists several specific actions; minor gaps' anchor. 'Analyzing your business' is generic, and coverage is narrower than the comprehensive 5 anchor, so it sits at 4 rather than 5.

4 / 5

Completeness

Quotes: 'Identifies high-quality leads... by analyzing your business, searching for target companies, and providing actionable contact strategies' is a clear 'what', but the only 'when' signal is the audience statement 'Perfect for sales, business development, and marketing professionals', which is not an explicit trigger clause — per the guideline, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Quotes: 'high-quality leads', 'target companies', 'sales, business development, and marketing' — relevant keywords, but the natural phrases a user would say ('find leads', 'lead generation', 'prospecting', 'potential customers', 'B2B outreach') are missing. This matches 'some relevant keywords but missing common variations or synonyms' better than the good-coverage 4 anchor.

3 / 5

Distinctiveness Conflict Risk

Quotes: 'Identifies high-quality leads', 'searching for target companies', 'actionable contact strategies' — a mostly distinct lead-generation niche with vocabulary unlikely to pull in unrelated skills. It is not 5 because it could still overlap with general company-research, marketing, or outreach-related skills given the audience breadth ('sales, business development, and marketing professionals').

4 / 5

Total

14

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

maslennikov-ig/claude-code-orchestrator-kit

Path

.claude/skills/lead-research-assistant/SKILL.md

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.