build-tam

Build a Total Addressable Market list by sourcing accounts and contacts from providers like Crustdata, Dropleads, and PDL.

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, executable, and well-structured as an overview that delegates detail to a one-level reference. Its only gap is the lack of an explicit validation/verification checkpoint in the execution workflow.

Suggestions

Add a verification step after the ordered workflow (e.g., confirm auth status and that the build-tam recipe is loaded before proceeding) to raise workflow_clarity.

Optionally note expected auth status output so Claude can detect a failed/no-op connection and retry.

Dimension	Reasoning	Score
Conciseness	The ~24-line body is lean: a quick-start code block, a one-line note, and a short ordered execution list, with no padding or explanation of concepts Claude already knows, matching the anchor 3 "lean and efficient; every token earns its place."	3 / 3
Actionability	It provides copy-paste-ready, executable commands (npm install, deepline auth register/wait/status) and explicit instructions to invoke deepline-gtm and read a specific recipe path, matching anchor 3 "fully executable code/commands; copy-paste ready."	3 / 3
Workflow Clarity	Steps are clearly sequenced (invoke deepline-gtm, follow routing, additionally read the recipe), but there is no validation/verification checkpoint (e.g., confirming the recipe loaded or auth completed) before proceeding; per the guidelines this keeps it at anchor 2.	2 / 3
Progressive Disclosure	The body is an overview that defers detail to a clearly signaled one-level-deep reference (../deepline-gtm/recipes/build-tam.md) and the governing meta-skill, with content appropriately split and easy navigation, matching anchor 3.	3 / 3
	Total	11 / 12 Passed

Description

37%

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 clearly states the deliverable and names specific providers, giving it good distinctiveness and reasonable specificity. Its main weakness is the complete absence of an explicit "Use when..." trigger clause, which caps completeness and limits natural discoverability.

Suggestions

Add an explicit "Use when..." clause (e.g., 'Use when building a TAM, prospect, or lead list from account/contact providers'), which would raise completeness.

Expand the action list beyond 'sourcing' to concrete steps like enrich, dedupe, filter, and export to lift specificity.

Add natural user phrasings (prospect list, lead list, target accounts) alongside 'TAM' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Build a Total Addressable Market list by sourcing accounts and contacts from providers like Crustdata, Dropleads, and PDL" names a concrete deliverable and the sourcing action plus specific providers, but does not enumerate multiple distinct concrete actions (e.g., enrich, dedupe, filter, export), so it sits at anchor 2 rather than 3.	2 / 3
Completeness	It answers "what" (build a TAM list by sourcing accounts/contacts) but provides no explicit "Use when..." trigger guidance; per the judging guidelines a missing explicit trigger clause caps completeness, and here the "when" is entirely absent, placing it at anchor 1 (the "when" is missing).	1 / 3
Trigger Term Quality	"Total Addressable Market", "TAM", "accounts and contacts", and the named providers give some relevant keywords, but it omits the common variations a user would naturally say (e.g., "build a prospect list", "lead list", "find target accounts"), leaving it at anchor 2.	2 / 3
Distinctiveness Conflict Risk	The combination of "Total Addressable Market list" with named providers (Crustdata, Dropleads, PDL) carves a distinct niche unlikely to conflict with unrelated skills, matching the anchor 3 "clear niche with distinct triggers."	3 / 3
	Total	8 / 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.