CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

portfolio-prospecting

Find companies backed by a specific investor or accelerator, then find contacts and build personalized outbound.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/portfolio-prospecting/SKILL.md
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.

An exemplary lean delegation skill: no padding, concrete commands and precise routing instructions with a conditional gate. Its only real weaknesses are the unexplained relationship between the CLI quick-start and the Skill-tool invocation, and its reliance on a cross-bundle file reference it cannot itself guarantee. As an instruction-only router skill, the absence of extensive code is appropriate.

Suggestions

Clarify how the 'deepline' CLI quick-start relates to the Skill-tool invocation of 'deepline-gtm' (e.g. whether the CLI is required, or just an optional entry point) to close the actionability and workflow-clarity gaps.

DimensionReasoningScore

Conciseness

Roughly 20 lean lines with zero padding: no concept explanations, no filler, and every sentence directs behavior ('Invoke deepline-gtm', 'Read the portfolio-prospecting recipe at ... only when that gate routes you to it'). Matches anchor 5's 'every token earns its place'.

5 / 5

Actionability

Provides executable commands ('npm install -g deepline', 'deepline -h') and concrete steps naming the exact skill ('deepline-gtm'), tool ('the Skill tool'), and file path ('../deepline-gtm/recipes/portfolio-prospecting.md'). Falls short of anchor 5 because the role of the CLI quick-start versus the Skill-tool invocation is never explained, leaving a minor gap in how to execute the overall flow.

4 / 5

Workflow Clarity

A clear 1-2-3 execution sequence with an explicit conditional gate ('only when that gate routes you to it') and guardrails ('Do not skip docs just because a recipe is pre-selected'). Not anchor 5 because there are no explicit validation/feedback checkpoints, and the connection between the CLI step and the meta-skill invocation is implicit; not a destructive/batch skill so the validation cap does not apply.

4 / 5

Progressive Disclosure

A well-organized overview ('Quick Start', 'Execution order') with a clearly signaled, one-level-deep, conditional reference. Short of anchor 5 because the sole reference points outside the skill's own bundle into a sibling skill's directory ('../deepline-gtm/recipes/'), which is a cross-skill dependency rather than an appropriately split internal structure — a minor organization gap per anchor 4.

4 / 5

Total

17

/

20

Passed

Description

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

A concise, third-person description with concrete actions and good natural trigger terms for the VC-prospecting niche. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness at 3, plus some absent synonyms like 'portfolio companies' and 'leads'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to prospect a VC's or accelerator's portfolio companies, find contacts at those companies, or draft personalized outbound messages.'

Include common synonyms users would naturally say — 'portfolio companies', 'VC-backed', 'leads', 'prospects' — to strengthen trigger term coverage.

Briefly specify the outbound medium (e.g. 'personalized outreach emails') to sharpen the final action's specificity.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Find companies backed by a specific investor or accelerator', 'find contacts', 'build personalized outbound') with only minor gaps such as the unspecified outbound channel. It lists more than the 1-2 actions of anchor 3 but lacks the comprehensive coverage of anchor 5.

4 / 5

Completeness

Has a clear 'what' (find portfolio companies, find contacts, build outbound) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than merely under-specified; not 2 because the 'what' is concrete.

3 / 5

Trigger Term Quality

Contains natural terms users would say ('investor', 'accelerator', 'contacts', 'personalized outbound') giving good keyword coverage, but misses common synonyms like 'portfolio companies', 'VC', 'leads', or 'prospects'. Better than anchor 3's partial keyword set, short of anchor 5's synonym/extension completeness.

4 / 5

Distinctiveness Conflict Risk

The investor/accelerator portfolio niche is mostly distinct with clear domain-specific triggers, but generic phrases like 'find contacts' and 'build personalized outbound' create minor overlap risk with general sales-outreach or contact-enrichment skills. Clearer than anchor 3's broad overlap, less airtight than anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

getaero-io/gtm-eng-skills

Path

skills/portfolio-prospecting/SKILL.md

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.