CtrlK
BlogDocsLog inGet started
Tessl Logo

investor-research

Research VCs, angels, and investors - portfolio, thesis, contact info

49

Quality

53%

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 ./skills/research/capabilities/investor-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The content is well-structured and mostly lean, but the curl examples contain broken JSON payloads that prevent copy-paste execution, and the outreach workflow lacks any validation checkpoints between steps.

Suggestions

Fix every `-d` JSON payload so the request body is a single valid JSON object (merge `api`/`path` and `searchParams`/`query`/`lead` under one `-d '{...}'` string) to make the examples executable.

Add verification checkpoints between steps (e.g., confirm the investor search returned results, check a partner was found before looking up email).

Remove the redundant "Example Usage" block or the restated "Research venture capitalists..." line to tighten token use.

DimensionReasoningScore

Conciseness

The body is mostly commands with little concept-overhead, but the "Example Usage" block repeats the Step 1/Step 2 calls and the opening "Research venture capitalists..." line restates the description, so it could be tightened.

2 / 3

Actionability

Concrete curl commands with real endpoints and auth headers are provided, but every `-d` JSON payload is malformed (the string closes after `path` with `}'`, orphaning the `searchParams`/`query` keys and leaving a dangling `}'`), so the examples look executable but are not copy-paste ready.

2 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced with headers, but there are no validation or verification checkpoints between searches and outreach, and the rubric caps workflow clarity at 2 for batch/outreach workflows missing feedback loops.

2 / 3

Progressive Disclosure

The skill is self-contained in a single file with no bundle references and is organized into clearly labeled sections (Setup, Workflow, Example Usage, Tips, Discover More), matching the well-organized, one-level structure anchor.

3 / 3

Total

9

/

12

Passed

Description

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 identifies a clear domain and three deliverables but stops short of explicit trigger guidance and concrete multi-action verbs. It is competent yet generic enough to leave "when to use" ambiguous.

Suggestions

Add an explicit "Use when..." clause naming trigger situations (e.g., raising a round, building an investor list, finding partner emails).

Expand action verbs beyond "Research" to concrete operations like "Find investors, pull portfolio companies, look up partner contacts, find emails for outreach".

Include common trigger terms users actually say, such as "funding", "raising", "venture capital", and stage names (Seed, Series A).

DimensionReasoningScore

Specificity

Names the domain ("Research VCs, angels, and investors") and three concrete deliverables ("portfolio, thesis, contact info"), but offers only the single verb "Research" rather than multiple distinct actions, so it sits at the "some actions, not comprehensive" anchor rather than the multi-action level.

2 / 3

Completeness

It states what the skill does but contains no "Use when..." clause or equivalent trigger, and the rubric caps completeness at 2 when explicit trigger guidance is missing.

2 / 3

Trigger Term Quality

Includes natural terms a user might say ("VCs", "angels", "investors", "portfolio", "contact info") but omits common variations like "funding", "raising", "venture capital", or stage names, matching the "some relevant keywords but missing common variations" anchor.

2 / 3

Distinctiveness Conflict Risk

The investor-research niche is reasonably specific, but with no explicit triggers it could still overlap with generic research or contact-finding skills, matching the "somewhat specific but could still overlap" anchor.

2 / 3

Total

8

/

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
gooseworks-ai/goose-skills
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.