investor-hunting

通过搜索渠道主动发掘潜在投资人/投资机构，筛选匹配度，去重记录，可选触达。参照 BD lead-hunting 模式，针对投资人场景定制。

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./crews/main/skills/investor-hunting/SKILL.md

Quality

Content

100%

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 tight, actionable workflow with concrete commands, an explicit dedup validation checkpoint, and a thorough error-handling table. It avoids padding and is appropriately sectioned as an orchestrating overview.

Dimension	Reasoning	Score
Conciseness	Lean and table-driven with no explanation of concepts Claude already knows; every section (channels, steps, error handling) earns its place and assumes Claude's competence.	3 / 3
Actionability	Provides concrete executable commands with specific flags (init-db.sh, check-investor.sh --name/--firm, record-investor.sh with full arg list) plus a defined JSON output to gate on, making the guidance copy-paste ready.	3 / 3
Workflow Clarity	Steps 1–4 are clearly sequenced with an explicit dedup validation checkpoint (check-investor returns {"exists": true} → skip) and an error-handling table giving feedback loops (browser retry, risk-control handling) for the batch operation.	3 / 3
Progressive Disclosure	Well-organized into distinct sections (prerequisites, channels table, workflow, error handling) with one-level-deep references to sibling-skill scripts and no nested reference chains, keeping the overview navigable.	3 / 3
	Total	12 / 12 Passed

Description

60%

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 concretely names several actions and a clear investor-hunting niche, but lacks an explicit 'Use when' trigger and overlaps with the lead-hunting skill it references. Adding trigger guidance and natural user phrasings would raise completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause stating when to invoke this skill (e.g. when the user wants to find/research potential investors).

Surface natural user phrasings such as '寻找投资人', '找 VC', '发掘投资机构' as trigger terms.

Sharpen distinctiveness from the BD lead-hunting skill by naming the investor-specific inputs (stage, sector, fund size) that only this skill handles.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '发掘...投资人/投资机构', '筛选匹配度', '去重记录', '可选触达' — matching the anchor for multiple specific concrete actions rather than a single named action.	3 / 3
Completeness	Clearly answers 'what does this do' but provides no 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('投资人', '投资机构', '触达') but lacks common user phrasings like '寻找投资人' or '找投资' and is method-focused ('搜索渠道') rather than need-focused.	2 / 3
Distinctiveness Conflict Risk	It carves an investor-specific niche ('针对投资人场景定制') but explicitly references the sibling 'BD lead-hunting' skill it derives from, so overlap with that similar skill remains possible.	2 / 3
	Total	9 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: TeamWiseFlow/xiaobei
Path: crews/main/skills/investor-hunting/SKILL.md
Commit: bcef823

Reviewed: 3 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.