CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

build-tam

Build a Total Addressable Market list: size the audience, source companies from ICP filters, then find contacts at those companies at scale.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/build-tam/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-structured delegation skill: a short, clearly sequenced routing body that defers all substantive content to a meta-skill and a conditionally-gated recipe file. Main weaknesses are redundant restatement of the delegation rule, an unexplained CLI quick start, and a hard dependency on external files that cannot be verified from the skill itself.

Suggestions

State what 'deepline -h' is for (or replace it with the command that actually pre-selects the build-tam recipe) and clarify how the CLI relates to the Skill-tool invocation.

Collapse the three restatements of 'the meta-skill governs everything' into a single instruction to save tokens.

Add a fallback for when the deepline-gtm skill or ../deepline-gtm/recipes/build-tam.md is unavailable (e.g., an error message to surface to the user).

DimensionReasoningScore

Conciseness

The body is short and mostly earns its tokens, but the delegation rule is restated three times ('deepline-gtm governs the entire session', 'Do not skip docs just because a recipe is pre-selected', 'The meta-skill handles everything else the user asked for'), which could be trimmed.

4 / 5

Actionability

Instructions are literal and executable (npm install -g deepline, deepline -h, invoke deepline-gtm via the Skill tool, read a specific recipe path), but the purpose of 'deepline -h' and the relationship between the CLI and the Skill-tool flow are never stated — a minor gap.

4 / 5

Workflow Clarity

The three-step execution order is clearly sequenced with a conditional routing gate ('only when that gate routes you to it. Conditional access and safety checks still apply'), though there is no fallback or verification if the meta-skill or recipe file is unavailable.

4 / 5

Progressive Disclosure

A thin wrapper with well-organized sections and a single, clearly signaled, one-level-deep conditional reference; however, the referenced path points outside the skill bundle to a sibling skill's file (../deepline-gtm/recipes/build-tam.md) that is not present in this environment, and the skill ships no bundle files of its own.

4 / 5

Total

16

/

20

Passed

Description

58%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.

The description states a clear 'what' with three concrete, sequenced actions in a distinct sales-GTM niche, but omits any 'when to use this' guidance and misses the most natural trigger term users would actually say ('TAM'). Adding an explicit trigger clause with TAM/lead-list synonyms would lift completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks to build a TAM (total addressable market) list, size an audience, or generate a lead/account list from ICP criteria.'

Include the acronym 'TAM' and common synonyms ('lead list', 'prospecting list', 'account list') so the description matches the phrasing users actually type.

Optionally name the output artifacts (e.g., a company list with contacts) to close the minor coverage gaps and reach the comprehensive-specificity anchor.

DimensionReasoningScore

Specificity

Lists three concrete, sequenced actions ('size the audience, source companies from ICP filters, then find contacts at those companies at scale') covering most of the TAM-building pipeline; minor gaps (no mention of enrichment, verification, or output/export) keep it short of the comprehensive anchor.

4 / 5

Completeness

The 'what' is clear and concrete (build a TAM list via sizing, ICP-based company sourcing, contact finding), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Relevant domain terms are present ('Total Addressable Market', 'ICP filters', 'source companies', 'find contacts') but the most natural user phrasing — the acronym 'TAM' itself — plus common synonyms like 'lead list' or 'prospecting list' are missing, matching the 'missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The GTM/sales vocabulary (Total Addressable Market, ICP, contact sourcing at scale) carves out a distinct niche with only minor overlap risk against generic lead-generation or prospecting skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Revision

6776244

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill