build-tam

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

Quality

55%

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/build-tam/SKILL.md

Quality

Content

27%

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

This skill functions purely as a routing shim, delegating all actual content and logic to external files (deepline-gtm meta-skill and build-tam recipe) without providing any standalone value. It contains no concrete, actionable guidance for building a TAM list—no code, no examples, no provider-specific instructions. The multi-level indirection (skill → meta-skill → sub-docs → recipe) makes it difficult to follow and violates progressive disclosure principles.

Suggestions

Add concrete, actionable content about TAM building—at minimum, summarize the key steps, provider APIs (Apollo, Crustdata, PDL), and expected inputs/outputs so the skill has standalone value.

Include at least one executable code example or specific command for sourcing accounts/contacts from a provider.

Flatten the reference chain: instead of routing through a meta-skill that routes to sub-docs, directly reference the specific files needed with clear one-level-deep links.

Add validation checkpoints (e.g., 'verify account count meets minimum threshold before proceeding to contact enrichment') to improve workflow clarity.

Dimension	Reasoning	Score
Conciseness	Reasonably brief but includes some unnecessary explanation (e.g., 'This is a recipe shortcut' preamble and the final sentence restating what was already implied). Could be tighter.	2 / 3
Actionability	No concrete code, commands, or executable guidance. The skill is entirely meta-routing instructions ('invoke X', 'follow Y', 'read Z') with no actual TAM-building steps, examples, or specific commands. All real content is deferred elsewhere.	1 / 3
Workflow Clarity	There is a numbered 3-step sequence, but it lacks any validation checkpoints, error handling, or feedback loops. The steps are also vague ('follow the meta-skill's full routing instructions') rather than concrete.	2 / 3
Progressive Disclosure	The skill is essentially a pointer to other files (deepline-gtm meta-skill, build-tam recipe) with no substantive content of its own. There are no bundle files provided to support the references, and the references chain through multiple levels (this skill → meta-skill → sub-docs → recipe), creating deeply nested indirection.	1 / 3
	Total	6 / 12 Passed

Description

82%

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 strong in specificity and distinctiveness, naming concrete actions and specific data providers that create a clear niche. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are naturally aligned with what sales/marketing users would say.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about building a TAM list, prospecting, sourcing leads, finding accounts or contacts, or mentions Apollo, Crustdata, or PDL.'

Dimension	Reasoning	Score
Specificity	Lists specific concrete actions: 'Build a Total Addressable Market list', 'sourcing accounts and contacts', and names specific providers (Apollo, Crustdata, PDL). Multiple concrete actions and tools are identified.	3 / 3
Completeness	Clearly answers 'what does this do' (build TAM lists by sourcing accounts and contacts from specific providers), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'Total Addressable Market', 'TAM list' (implied via 'Total Addressable Market list'), 'accounts', 'contacts', 'Apollo', 'Crustdata', 'PDL'. These are terms sales/marketing professionals naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: TAM list building using specific data providers (Apollo, Crustdata, PDL). This is unlikely to conflict with other skills due to the specific domain and named tools.	3 / 3
	Total	11 / 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.