CtrlK
BlogDocsLog inGet started
Tessl Logo

investor-outreach

撰写投资人触达邮件、暖介绍请求、跟进邮件、投资人更新等融资沟通文案。 当用户需要向天使投资人、VC、战略投资人、加速器发起接触,或需要精简、个性化的投资人沟通文案时触发。

70

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, well-structured instruction-only skill with concrete rules, tables, a follow-up cadence, and a quality-gating checklist. Its main shortcoming is the lack of a fully worked example email and explicit validation/error-recovery phrasing in the workflow sections.

Suggestions

Add one fully worked example cold email (subject + body + Ask) so the 冷邮件结构 is copy-paste ready, lifting actionability toward 5.

Make the 质量门控 checklist an explicit validate-then-fix loop (e.g., 'if any box is unchecked, revise before delivery') to strengthen workflow_clarity's feedback-loop posture.

Clarify the ir-record handoff with a one-line concrete invocation example (e.g., `bash record-contact.sh --investor "..."`) so the cross-skill pointer is immediately executable.

DimensionReasoningScore

Conciseness

Lean throughout — short rules, tables, and a checklist with no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Concrete, specific guidance throughout (5-step 冷邮件结构, blurb format '谁+做什么+关键数据点+Ask', hard-ban phrase list, quality-gate checklist); as an instruction-only skill absence of code is fine, but it stops short of a full copy-paste example email that the 5 anchor implies.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (跟进节奏 day 0/4-5/10-12 table, 会议后更新 1-4, 冷邮件结构 1-5) with a delivery '质量门控' checklist as a validation checkpoint; not a destructive/batch skill so the cap does not apply, but error-recovery feedback loops are implicit rather than explicit.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one-level cross-skill pointers (market-research, investor-hunting, email-ops, ir-record); no bundle files exist so there is nothing to offload, and the body inlines structures that, while appropriate for a simple skill, keep it just below the optimal-split 5 anchor.

4 / 5

Total

17

/

20

Passed

Description

92%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 is specific, complete, and distinct: it names concrete communication artifacts and pairs them with an explicit bilingual trigger clause. It is a strong, low-fluff description whose only minor gap is synonym-level keyword breadth.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '撰写投资人触达邮件、暖介绍请求、跟进邮件、投资人更新等融资沟通文案' — covering cold outreach, warm intros, follow-ups, and updates, which is comprehensive for this domain.

5 / 5

Completeness

Explicitly answers both 'what' (撰写…融资沟通文案) and 'when' ('当用户需要…发起接触,或需要精简、个性化的投资人沟通文案时触发'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user-facing terms are present ('天使投资人、VC、战略投资人、加速器发起接触', '精简、个性化的投资人沟通文案'); strong but not fully comprehensive coverage of synonyms/variations, so sits just below the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (融资沟通 / 投资人触达) with distinct, domain-specific triggers unlikely to fire for unrelated skills; minimal conflict risk.

5 / 5

Total

19

/

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.