CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

1.20x
Quality

59%

Does it follow best practices?

Impact

95%

1.20x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

57%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 delivers a coherent, actionable lead-research workflow with a strong output specification, but it is held back by redundant sections, absent validation checkpoints for a batch-output process, and a monolithic single-file structure. Trimming the duplicated overview sections and adding verification steps would lift it substantially.

Suggestions

Cut the "What This Skill Does" and "Related Use Cases" sections (they duplicate "Instructions" and "How to Use") and fold "Tips for Best Results" into the usage prompts to remove padding.

Add an explicit validation step to the workflow, e.g. "Verify each lead: confirm the company is active, the website/LinkedIn URL resolves, and stated signals (job postings, funding) are current before including it".

Move the full output template and the two examples into references/ files (e.g. references/output-template.md, references/examples.md) and link to them from a lean SKILL.md overview.

DimensionReasoningScore

Conciseness

The core Instructions and output template are efficient, but "What This Skill Does" nearly duplicates the Instructions section, "Tips for Best Results" restates "How to Use", and "Related Use Cases" adds padding — several sections could be cut or tightened. It is not a 2 because the guidance avoids explaining concepts Claude already knows and the bulk of the body is direct instruction, not conceptual filler.

3 / 5

Actionability

Concrete, executable guidance throughout: copy-paste user prompt templates, a 1-10 fit-score scheme with named factors, an exact per-lead output field list (Company Name, Priority Score, Decision Maker, LinkedIn URL, Conversation Starters), and a full markdown output template. It is not a 5 because the research steps themselves ("Search for companies matching the criteria", "Check for budget indicators") remain high-level hints with no concrete search strategies or commands.

4 / 5

Workflow Clarity

A clear 7-step sequence is present (understand product → define ICP → research → score → output → format → next steps), but there are no validation checkpoints — nothing verifies that identified companies are real, currently operating, or match the stated criteria, which is a batch operation producing 10-20 lead profiles. The rubric's cap for batch operations without validation holds it at 3; it is not a 2 because the sequence itself is coherent and well defined.

3 / 5

Progressive Disclosure

The body has good section headers but is a single ~195-line file with no bundle files; the 40-line output template and the Examples section are content that could live in one-level-deep reference files. It is not a 2 because structure is solid with clear, navigable sections; not a 4-5 because nothing is split out and the file is well over the ~50-line threshold where inline-only organization would suffice.

3 / 5

Total

13

/

20

Passed

Description

61%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 clearly conveys what the skill does and is reasonably rich in natural keywords, but it lacks an explicit "Use when..." trigger clause and uses second-person voice ("your product or service"), which both depress its scores. It carves out a recognizable niche with modest conflict risk against adjacent research skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to find leads, prospects, or target companies for their product, or mentions lead generation, prospecting, or sales outreach."

Rewrite in third person ("Identifies high-quality leads for a product or service by analyzing the business...") to avoid the second-person specificity penalty.

Include common synonyms users actually say — "lead generation", "prospecting", "prospects", "outreach" — to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "analyzing your business, searching for target companies, and providing actionable contact strategies" — but "actionable contact strategies" is padded and coverage has gaps, fitting the several-actions anchor at 4; however, the second-person voice ("your product or service", "your business") triggers the mandated 1-point reduction, landing it at 3. It is not a 2 because the domain (lead identification) is named with more than minimal generic actions.

3 / 5

Completeness

The "what" is clear (identifies high-quality leads via business analysis, company search, and contact strategies), but there is no "Use when..." clause — "Perfect for sales, business development, and marketing professionals" names an audience, not an explicit trigger, so the rubric's cap of 3 applies. It is not a 2 because the "what" is concrete, and not a 4 because the "when" is only weakly implied through audience framing.

3 / 5

Trigger Term Quality

Good natural keyword coverage — "leads", "target companies", "sales", "business development", "marketing", "contact strategies" — terms users would plausibly say when needing this skill. It is not a 5 because common synonyms like "lead generation", "prospecting", "prospects", and "outreach" are missing; not a 3 because multiple natural phrases are present rather than just a bare domain mention.

4 / 5

Distinctiveness Conflict Risk

The lead-research/prospecting niche is fairly distinct — "high-quality leads", "target companies", "contact strategies" — with only minor overlap risk against general company-research or market-analysis skills. It is not a 5 because terms like "analyzing your business" are broad enough that a generic market-research request could plausibly trigger it.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.