The body is a tight, highly actionable recipe shortcut: executable setup commands, a numbered execution order, and a clearly gated one-level-deep reference. The only weaknesses are minor — a thrice-repeated governance caveat that could be trimmed and no guidance for recovering from auth failures.

Dimension	Reasoning	Score
Conciseness	The ~28-line body is lean with executable commands and no concept over-explanation, but the point that "the deepline-gtm governs the entire session" is repeated three times (intro line, step 2, closing line), matching 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place level 5.	4 / 5
Actionability	Quick Start gives copy-paste-ready commands including a sandbox-safe install fallback with explanatory inline comments, and the execution order specifies the exact Skill-tool invocation (`deepline-gtm`) and an exact relative path (`../deepline-gtm/recipes/portfolio-prospecting.md`) — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	A clear ordered sequence (install → auth wait/status → invoke meta-skill → follow routing → conditionally read recipe) with checkpoints like `deepline auth wait` and `deepline auth status`, but there is no explicit error-recovery loop (e.g. what to do if auth fails after the timeout), matching 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files, well-organized into Quick Start and Execution order sections, and its single reference (the recipe, read 'only when that gate routes you to it') is clearly signaled and exactly one level deep — meeting the simple-skill exception for a top score.	5 / 5
	Total	18 / 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.

The description states a clear, concrete multi-step capability in third person with a distinctive niche, but it omits any 'use when' trigger clause, which both caps completeness and weakens trigger discoverability. Adding explicit trigger guidance and common synonyms (portfolio companies, leads, outreach) would lift it substantially.

Suggestions

Append a trigger clause, e.g. "Use when the user asks to find a VC's or accelerator's portfolio companies, build prospect lists, or create personalized outreach for investor-backed companies."

Add natural synonyms such as "portfolio companies", "prospects", "leads", and "cold outreach" so the description matches how users actually phrase these requests.

Make the outbound step slightly more concrete (e.g. "build personalized email/LinkedIn outreach") to close the minor specificity gap.

Dimension	Reasoning	Score
Specificity	Three concrete chained actions — "Find companies backed by a specific investor or accelerator", "find contacts", "build personalized outbound" — cover the pipeline, but the outbound step leaves the channel unspecified and e.g. enrichment/messaging details are absent, matching the 'several specific actions; minor gaps' anchor rather than the fully comprehensive level 5.	4 / 5
Completeness	The 'what' is clear (portfolio discovery → contacts → personalized outbound) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; it is not a 4 because 'when' is entirely absent rather than merely weak.	3 / 5
Trigger Term Quality	Natural terms "investor", "accelerator", "contacts", "personalized outbound" are present, but common user phrasings like "portfolio companies", "leads", "outreach", or "cold email" are missing, fitting 'good keyword coverage; a few natural terms missing' rather than the synonym-complete level 5.	4 / 5
Distinctiveness Conflict Risk	The investor/accelerator-backed qualifier gives a clear niche with distinct triggers, but "find contacts and build personalized outbound" overlaps with generic sales/lead-generation skills, matching 'mostly distinct; minor overlap risk' rather than the minimal-conflict level 5.	4 / 5
	Total	15 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: getaero-io/gtm-eng-skills
Path: skills/portfolio-prospecting/SKILL.md
Commit: a9b9731

Reviewed: 6 days 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.