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.

81

1.20x
Quality

73%

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

65%

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

The body is well-structured and highly actionable, with a concrete output template and clear step sequence for an instruction-only skill. It loses points for verbosity/redundancy, missing validation checkpoints, and a monolithic structure with no progressive disclosure.

Suggestions

Add a verification step before finalizing leads (e.g., confirm the company is active and the decision-maker role/current) to introduce a validation checkpoint into the workflow.

Collapse the redundant "What This Skill Does" and "Instructions" sections, and move the full output template and examples into a reference file to reduce the monolithic size.

Trim the restated-description opening and the "Tips for Best Results" / "Related Use Cases" overlap to tighten token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient and task-focused, but ~190 lines with redundancy between "What This Skill Does" and "Instructions", plus an opening that restates the description; could be tightened.

2 / 3

Actionability

Provides concrete, specific guidance — a copy-paste-ready markdown output template, per-lead fields, a 1-10 fit score, decision-maker role examples, and worked examples — which is actionable for an instruction-only skill.

3 / 3

Workflow Clarity

The seven numbered steps are clearly sequenced, but there are no validation or verification checkpoints (e.g., confirming a company or contact is still current) before producing the final lead list.

2 / 3

Progressive Disclosure

Well-organized with clear section headers, but it is a monolithic ~190-line single file with no bundle references; the large output template and examples are inline content that could be split out, and it exceeds the 50-line simple-skill exemption.

2 / 3

Total

9

/

12

Passed

Description

82%

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 is specific and distinct, naming several concrete actions and natural domain trigger terms. Its main weakness is the missing explicit "Use when..." trigger guidance, relying instead on an audience hint.

Suggestions

Add an explicit trigger clause such as "Use when the user asks to find leads, prospects, or target companies for a product or service."

Tighten "Perfect for sales, business development, and marketing professionals" into a concrete when-to-use condition rather than an audience descriptor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "analyzing your business", "searching for target companies", and "providing actionable contact strategies" — rather than vague language.

3 / 3

Completeness

Clearly states what it does, but the "when" is only implied via audience ("Perfect for sales, business development, and marketing professionals") with no explicit "Use when..." trigger clause, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Uses natural terms a user would say in this domain — "high-quality leads", "sales", "business development", "marketing", "target companies", "contact strategies" — with good coverage.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (lead research/prospecting) with distinct triggers around finding companies and contact strategies, making conflict with unrelated skills unlikely.

3 / 3

Total

11

/

12

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.

Validation15 / 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.