build-tam

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

Quality

79%

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

82%Weight 40%Scale 1-5

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

An efficient, actionable delegation skill: lean quick-start commands, a clear execution order, and a cleanly signaled external recipe reference. Its gaps are the missing error-recovery guidance for the auth flow and the reliance on a recipe path outside its own bundle.

Dimension	Reasoning	Score
Conciseness	The ~28-line body is lean: an executable quick-start block with terse inline comments ("completes Cowork/browser approval; no-op if already connected") and a numbered execution order with zero padding. It explains nothing Claude already knows and every token earns its place.	5 / 5
Actionability	The bash block is copy-paste ready (install with sandbox fallback, auth register/wait/status), and the execution order gives concrete instructions ("Invoke deepline-gtm using the Skill tool", an explicit recipe path). Not 5 because the skill's core task guidance lives in an external recipe file that is not part of this bundle, leaving the actual TAM-building steps unverifiable from here.	4 / 5
Workflow Clarity	A clear two-phase sequence: setup (install, auth register/wait/status as a connection checkpoint) then a numbered 3-step delegation flow with an explicit routing gate. Not 5 because there is no error-recovery feedback loop (e.g., what to do if auth status fails or the meta-skill is unavailable).	4 / 5
Progressive Disclosure	Well-organized sections (Quick Start, Execution order) with the detailed material correctly pushed to a single, clearly signaled one-level-deep reference ("Read the build-tam recipe at ../deepline-gtm/recipes/build-tam.md"). Not 5 because that referenced path is external to the skill's own bundle (no references/, scripts/, or assets/ directories exist here) and does not resolve from this location, making navigation fragile.	4 / 5
	Total	17 / 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.

A specific, provider-anchored description with a clear "what" and good natural trigger terms. Its main weakness is the complete absence of a "when" clause, which caps completeness and slightly limits trigger-term strength.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to build a TAM/account list, source B2B contacts, or asks about data providers like Crustdata, Dropleads, or PDL."

Include natural variations of the core terms — "TAM", "lead list", "prospect list", "account enrichment" — to broaden trigger coverage.

State what the output looks like (e.g., a structured account/contact list or CSV export) to sharpen the "what" without adding fluff.

Dimension	Reasoning	Score
Specificity	"Build a Total Addressable Market list" and "sourcing accounts and contacts" name several concrete actions, reinforced by named providers (Crustdata, Dropleads, PDL). Not 5 because it omits what building a TAM list otherwise entails (enrichment, filtering, export); not 3 since it goes beyond 1-2 generic actions with provider-specific sourcing.	4 / 5
Completeness	It clearly answers "what" (build a TAM list by sourcing accounts and contacts from named providers) but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines. The "when" is entirely absent rather than merely weakly implied.	3 / 5
Trigger Term Quality	"Total Addressable Market", "accounts", "contacts", and the three provider names are natural terms a user would say when needing this skill. Not 5 because common variations like "TAM", "lead list", or "prospect list" are absent; not 3 since coverage is good rather than merely partial.	4 / 5
Distinctiveness Conflict Risk	"Build a Total Addressable Market list ... from providers like Crustdata, Dropleads, and PDL" carves out a distinct TAM-sourcing niche anchored by provider names. Not 5 because it could still overlap with generic lead-generation or sales-data skills; not 3 because the provider specificity makes wrong-skill triggering unlikely.	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/build-tam/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.