portfolio-prospecting

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

Quality

33%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/portfolio-prospecting/SKILL.md

Quality

Content

35%

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

This skill is essentially a thin routing shim that delegates entirely to another skill ('deepline-gtm') and a recipe file. It provides no concrete, actionable guidance for portfolio/VC prospecting itself—no commands, no code, no examples, no actual workflow steps. While it's concise, it sacrifices all actionability and substantive workflow clarity by being purely a redirect.

Suggestions

Add at least a brief summary of what the portfolio-prospecting workflow actually does (e.g., key steps like identifying portfolio companies, finding contacts, crafting outbound messages) so the skill has standalone value.

Include concrete examples of inputs and expected outputs (e.g., 'Given investor X, find their portfolio companies and generate personalized outreach emails').

Provide at least one actionable step or command that Claude can execute directly, rather than delegating everything to external files.

If the skill truly requires the meta-skill, clarify what happens if the meta-skill or recipe file is unavailable, and add a fallback or validation step.

Dimension	Reasoning	Score
Conciseness	Reasonably brief but includes some unnecessary meta-commentary ('This is a recipe shortcut') and explanation that could be tightened. The repeated emphasis on the meta-skill governing the session is somewhat redundant.	2 / 3
Actionability	The skill provides no concrete code, commands, or executable guidance. It merely delegates to another skill ('deepline-gtm') and a recipe file without providing any actual steps for portfolio/VC prospecting. There's nothing copy-paste ready or directly actionable.	1 / 3
Workflow Clarity	There is a numbered sequence of 3 steps, but they are essentially 'invoke another skill and follow its instructions,' which is vague. There are no validation checkpoints, no error handling, and no concrete workflow for the actual prospecting task.	2 / 3
Progressive Disclosure	References to the meta-skill and recipe file are present with a relative path, but no bundle files are provided to verify the structure. The skill is essentially a thin redirect with one level of reference, but the lack of any overview content or quick-start guidance means it doesn't serve well as a standalone entry point.	2 / 3
	Total	7 / 12 Passed

Description

32%

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 conveys a reasonable sense of the skill's purpose—finding companies backed by specific investors/accelerators and building outbound campaigns—but lacks explicit trigger guidance ('Use when...') and concrete specifics about outputs. The trigger terms are decent but miss common user vocabulary like 'VC', 'portfolio companies', 'cold email', or 'prospecting'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to prospect companies from a VC portfolio, accelerator cohort, or investor-backed company list.'

Include more natural trigger terms users would say, such as 'VC', 'portfolio companies', 'YC', 'cold email', 'prospecting', 'lead generation', 'sales outreach'.

Be more specific about the concrete outputs—e.g., 'generates personalized cold emails', 'builds a contact list with LinkedIn profiles', 'creates a CSV of target companies'.

Dimension	Reasoning	Score
Specificity	Names the domain (investor/accelerator-backed companies) and some actions (find companies, find contacts, build personalized outbound), but the actions are somewhat vague—'build personalized outbound' is not concrete about what form the output takes (emails, lists, campaigns?).	2 / 3
Completeness	Describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when' clause caps completeness at 2, and since the 'what' is also somewhat vague, this scores at 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'investor', 'accelerator', 'contacts', 'outbound', but misses common variations users might say such as 'VC', 'portfolio companies', 'cold email', 'prospecting', 'lead generation', 'sales outreach', or specific accelerator names like 'YC'.	2 / 3
Distinctiveness Conflict Risk	The combination of investor/accelerator-backed company research with contact finding and outbound is somewhat distinctive, but 'find contacts and build personalized outbound' could overlap with general sales prospecting or CRM skills.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: getaero-io/gtm-eng-skills
Commit: 449bc08

Reviewed: 1 day 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.