build-tam

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

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/build-tam/SKILL.md

Quality

Content

92%

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

The content is lean, actionable, and clearly sequenced as a routing recipe into a meta-skill. Its main weakness is progressive disclosure: the single referenced recipe file does not exist in the bundle, so the signaled navigation is broken.

Suggestions

Ensure the referenced ../deepline-gtm/recipes/build-tam.md file exists in the bundle, or correct the path so the signaled reference resolves.

Consider noting in the body that deepline-gtm is a sibling skill bundle so the relative reference is unambiguous to the loader.

Dimension	Reasoning	Score
Conciseness	The body is lean (~20 lines) with no padding or explanations of concepts Claude already knows; every section earns its place (Quick Start commands, short execution order).	3 / 3
Actionability	Provides copy-paste-ready executable commands (npm install, deepline auth register/wait/status) and concrete routing instructions including a specific file path and Skill-tool invocation.	3 / 3
Workflow Clarity	Execution order is a clear numbered sequence with an explicit routing gate ("only when that gate routes you to it"); no validation loop is required because this is a routing recipe, not a destructive or batch operation.	3 / 3
Progressive Disclosure	The body is a concise overview pointing one level deep to ../deepline-gtm/recipes/build-tam.md, but that referenced file is not present in the bundle, so the signaled reference cannot be followed.	2 / 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 concrete actions and providers for a clear TAM-building niche. It is weak on completeness because it omits an explicit "Use when..." trigger clause, and trigger-term coverage could be broader.

Suggestions

Add an explicit "Use when..." clause, e.g., "Use when building a Total Addressable Market (TAM) list or sourcing accounts and contacts."

Include common trigger variations such as "TAM", "lead list", and "prospecting list" so the skill matches natural user phrasing.

Dimension	Reasoning	Score
Specificity	"Build a Total Addressable Market list by sourcing accounts and contacts" names multiple concrete actions (build TAM list, source accounts, source contacts) plus specific provider names.	3 / 3
Completeness	Clearly states what the skill does but provides no explicit "Use when..." trigger guidance, so the "when" side is only implied and completeness is capped at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes relevant natural terms like "Total Addressable Market", "accounts and contacts", and provider names, but lacks common variations (e.g., "TAM", "lead list", "prospecting") a user might naturally say.	2 / 3
Distinctiveness Conflict Risk	The TAM-building niche with named providers (Crustdata, Dropleads, PDL) is a clear, distinct scope unlikely to trigger for 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
Path: skills/build-tam/SKILL.md
Commit: 59a5bd2

Reviewed: about 11 hours 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.