portfolio-prospecting

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

87%

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

The body is concise, actionable, and well-structured with a single clearly signaled external recipe reference. Its main gap is the absence of any validation checkpoint to confirm the delegated meta-skill and recipe path are correctly resolved.

Suggestions

Add a verification step after invocation, e.g. confirm the meta-skill loaded and that the recipe path exists before proceeding.

Note what to do if the relative recipe path is missing (fallback location or error handling) to close the workflow validation gap.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: a short Quick Start block and brief execution order with no padded explanation of concepts Claude already knows; every line earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands (npm install, deepline auth register/wait/status) and concrete routing actions with a specific recipe path.	3 / 3
Workflow Clarity	Steps are clearly sequenced (invoke meta-skill, follow routing, read recipe), but there are no validation checkpoints confirming the meta-skill loaded or the recipe path resolved — matching 'steps listed but validation gaps'.	2 / 3
Progressive Disclosure	Well-organized short body with a clearly signaled one-level-deep reference (../deepline-gtm/recipes/portfolio-prospecting.md) and no nested chains; empty bundle dirs match the body's references.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 and distinct, naming three concrete prospecting actions in a clear niche. It is held back by the absence of explicit 'Use when...' trigger guidance and limited coverage of natural keyword variations.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when prospecting companies backed by a specific VC, finding portfolio contacts, or building outbound sequences').

Broaden trigger-term coverage with common phrasings users would say, such as 'investor portfolio', 'accelerator companies', 'lead enrichment', or 'cold outreach'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Find companies backed by a specific investor or accelerator, then find contacts and build personalized outbound' — rather than vague language.	3 / 3
Completeness	Clearly answers 'what' but has no 'Use when...' or equivalent trigger guidance, which the rubric caps at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('companies', 'investor', 'accelerator', 'contacts', 'outbound') but lacks common variations and explicit trigger phrasing, matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (VC/portfolio prospecting) with distinct triggers, unlikely to conflict with unrelated skills.	3 / 3
	Total	10 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: getaero-io/gtm-eng-skills
Commit: 25492ee

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.