CtrlK
BlogDocsLog inGet started
Tessl Logo

investor-hunting

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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-structured, actionable workflow with concrete commands, explicit validation checkpoints, and a real error-recovery feedback loop. It is concise and assumes Claude's intelligence; the only thing keeping it from the top band is that some search/extraction steps delegate to other skills without concrete detail.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanations of what investors or databases are), using tables and compact step lists; the only padding is the intro line repeating the frontmatter description, keeping it just short of a 5.

4 / 5

Actionability

Provides copy-paste-ready bash commands with full argument flags (init-db.sh, check-investor.sh, record-investor.sh) and concrete field-extraction lists, but the search/extract steps defer to other skills ("使用 smart-search 构造搜索 URL") without showing how, a minor gap.

4 / 5

Workflow Clarity

Clear Step 1–4 sequence with an explicit dedup validation checkpoint (skip if {"exists": true}), a browser retry feedback loop (wait 30s → retry → reopen → stop), a match-criteria checklist, and a final statistics summary; the batch cap is not triggered because validation is present, but per-record write verification is only implicit.

4 / 5

Progressive Disclosure

Well-organized into clear sections (前置条件, 搜索渠道, 执行流程, 错误处理) with clearly signaled one-level-deep cross-skill references and no nested bundle references; at ~107 lines it exceeds the simple-skill (<50 line) exception that would allow a 5, so it sits at 4.

4 / 5

Total

16

/

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 gives a clear, concrete picture of what the skill does across a four-stage investor pipeline, but omits any explicit trigger guidance and leans on a referenced sibling skill for distinctiveness. It is solid but not exemplary, with the main weakness being the missing 'when to use' clause.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user wants to find, research, or build a list of potential investors for fundraising.'

Include natural trigger synonyms users would actually say — 找投资人, 融资, VC/PE, 天使投资人, FA — alongside 投资人/投资机构 to improve trigger_term_quality.

Briefly specify what '匹配度筛选' covers (investment stage / sector / fund size) in the description to lift specificity above generic verbs.

DimensionReasoningScore

Specificity

Quotes a concrete four-stage pipeline — "发掘潜在投资人/投资机构,筛选匹配度,去重记录,可选触达" — naming several specific actions, but the verbs stay generic and don't specify what 'match' entails, so it stops short of comprehensive (5).

4 / 5

Completeness

It clearly answers 'what' (discover, filter, dedupe, outreach) but has no 'Use when...' or equivalent trigger guidance, so per the rubric cap completeness stays at 3 even though the 'what' is clear.

3 / 5

Trigger Term Quality

Relevant keywords are present ("投资人", "投资机构", "发掘", "触达"), but common natural synonyms users would say — 找投资人, 融资, VC/PE, 天使投资人, FA — are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The investor-hunting niche is mostly distinct, but the phrase "参照 BD lead-hunting 模式" explicitly ties it to a sibling lead-hunting skill, signaling minor overlap risk rather than the minimal-conflict niche of a 5.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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