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.20x

Quality

38%

Does it follow best practices?

Impact

95%

1.20x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/lead-research-assistant/SKILL.md

Quality

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 communicates the general domain of lead generation and names a few high-level actions, but lacks the concrete specificity and explicit trigger guidance needed for reliable skill selection. It uses second person ('your product or service', 'your business'), which violates the third-person voice requirement. The absence of a 'Use when...' clause and natural trigger term variations limits its effectiveness in a multi-skill environment.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'find leads', 'prospecting', 'identify potential customers', 'lead generation', 'build a prospect list', 'outreach strategy'.

Replace second-person voice ('your product', 'your business') with third-person voice (e.g., 'Analyzes a business's target market and searches for matching companies').

List more concrete actions and outputs, such as 'generates prospect lists with company names, contact info, and outreach templates' to improve specificity.

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 steps occur).	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 phrase 'Perfect for sales, business development...' 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

27%

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

This skill is significantly over-engineered for what is essentially a research and formatting task. It spends excessive tokens on explaining concepts Claude already knows (lead qualification, ICP definition, scoring) and lacks concrete tool-usage instructions (which search tools to use, how to verify data). The output template is useful but the surrounding content could be reduced by 60-70% without losing actionable information.

Suggestions

Cut the 'When to Use This Skill', 'What This Skill Does', 'Tips for Best Results', and 'Related Use Cases' sections entirely — they explain concepts Claude already understands and add no actionable value.

Add specific tool usage instructions: which MCP tools or web search capabilities to use for finding companies, verifying information, and locating LinkedIn profiles.

Add validation checkpoints: e.g., 'After identifying initial leads, verify each company is still active and confirm industry/size before scoring' and 'Present top 3 leads to user for feedback before completing the full list.'

Move the detailed output format template to a separate reference file and keep only a brief summary in the main skill body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive sections explaining concepts Claude already understands (what lead research is, what an ICP is, how to score leads). The 'When to Use This Skill' and 'What This Skill Does' sections are largely redundant with the instructions. The full markdown output template, tips, related use cases, and examples add significant token bloat without proportional value.	1 / 3
Actionability	The skill provides a structured workflow and output format template, which is somewhat concrete. However, it lacks executable code/commands (no actual search tool usage, no API calls, no specific web search queries). The guidance is procedural but abstract — 'Search for companies matching the criteria' doesn't tell Claude how to search. No specific tools or MCP servers are referenced.	2 / 3
Workflow Clarity	Steps are clearly numbered and sequenced (understand product → define ICP → research → prioritize → output), but there are no validation checkpoints or feedback loops. There's no guidance on what to do when searches return poor results, how to verify company information accuracy, or when to ask the user for clarification mid-process.	2 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files. Everything is inline — the output template, examples, tips, related use cases — resulting in a very long single document. The output format template alone could be a separate reference file. No content is split or cross-referenced.	1 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 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: Lingjie-chen/MT5
Commit: 3069d33

Reviewed: 26 days 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.