CtrlK
BlogDocsLog inGet started
Tessl Logo

tam-sam-som-calculator

Calculate TAM, SAM, and SOM with explicit assumptions, methods, and caveats. Use when sizing a market for a product idea, business case, or executive review.

67

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is highly actionable with a real helper script and concrete recipe, but it is verbose and inlines material that should live in the missing template.md/examples files. Broken reference paths and weak validation checkpoints pull it below the top anchors.

Suggestions

Move the ~90-line inline output template into the referenced template.md (and actually ship that file) so SKILL.md stays a lean overview pointing one level deep.

Add explicit validation feedback loops (e.g., 'verify every figure has a citation before generating SAM; if missing, re-query') rather than framing validation only as end-of-output user questions.

Reconcile the helper script path so the inline command (scripts/market-sizing.py) matches the References path (skills/tam-sam-som-calculator/scripts/market-sizing.py), and either ship template.md/examples/sample.md or drop the references.

DimensionReasoningScore

Conciseness

The ~440-line body re-explains the TAM/SAM/SOM framework, restates the frontmatter intent in Purpose, and embeds a ~90-line output template inline, so while mostly useful it includes substantial unnecessary explanation that could be tightened.

2 / 3

Actionability

It provides an executable helper script with a concrete command, a named bottom-up recipe (Census/NAICS, BLS, Eurostat), enumerated questions with example data, and a copy-paste-ready output template, matching 'fully executable; copy-paste ready'.

3 / 3

Workflow Clarity

The Step 0 -> Q1-Q4 -> Output sequence is clearly ordered, but validation is framed as user-facing questions rather than explicit validate->fix->retry checkpoints, and the helper script path is cited inconsistently (scripts/ vs skills/tam-sam-som-calculator/scripts/), leaving validation gaps.

2 / 3

Progressive Disclosure

It signals references to template.md and examples/sample.md and to sibling skills, but those files do not exist in the bundle and the large output template is inlined rather than split out, so structure is present but navigation is broken and content is not appropriately separated.

2 / 3

Total

9

/

12

Passed

Description

100%

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 concise, third-person, and cleanly states both capability and trigger conditions with concrete, natural language. It hits the top anchor on every dimension with no fluff or over-claims.

DimensionReasoningScore

Specificity

"Calculate TAM, SAM, and SOM with explicit assumptions, methods, and caveats" names the domain and multiple concrete actions (calculate three named metrics) with output qualifiers, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It answers both what (calculate TAM/SAM/SOM with assumptions, methods, caveats) and when via the explicit "Use when sizing a market for a product idea, business case, or executive review" trigger clause.

3 / 3

Trigger Term Quality

"sizing a market", "product idea", "business case", and "executive review" are natural terms a user would say when requesting this skill, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

TAM/SAM/SOM market sizing is a clear niche with distinct, domain-specific triggers that are unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 suspicious

Warning

Total

14

/

16

Passed

Repository
deanpeters/Product-Manager-Skills
Reviewed

Table of Contents

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.