CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

market-sizing-analysis

Comprehensive market sizing methodologies for calculating Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) for startup opportunities.

Quality

66%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/market-sizing-analysis/SKILL.md

The canonical home for this skill is market-sizing-analysis in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body delivers genuinely actionable market-sizing guidance with concrete formulas, thresholds, and a worked example, and the six-step workflow is clearly sequenced with a validation step. However, it is padded with boilerplate and explanations of concepts Claude already knows, and its progressive disclosure is largely broken: five of the six referenced files do not exist in the bundle, leaving the reader stranded at nearly every "see file" pointer.

Suggestions

Fix the dangling references: either create the advertised files (`references/methodology-deep-dive.md`, `references/industry-templates.md`, the three `examples/` files) or remove the pointers — and correct the `resources/implementation-playbook.md` path to the actual `references/` directory.

Cut the boilerplate sections ("Use this skill when", "Do not use this skill when", generic "Instructions") and the restated "When to Use Each Methodology" section, and delete the verbatim repetition of the frontmatter description at the top of the body.

Move the industry-specific TAM formulas and the investor/strategy presentation structures into real reference files, keeping SKILL.md as a lean overview with one-level-deep, verified links.

DimensionReasoningScore

Conciseness

The 420-line body contains several padded or redundant sections: generic boilerplate ("Use this skill when... working on market sizing analysis tasks", "Clarify goals, constraints, and required inputs"), a verbatim repeat of the frontmatter description, and explanations of standard business concepts Claude already knows (what TAM/SAM/SOM are, definitions of top-down vs bottom-up). The "When to Use Each Methodology" section is then restated nearly in full inside "Three-Methodology Framework". This matches the "noticeably verbose; several unnecessary explanations or padded sections" anchor rather than the mostly-efficient anchor 3.

2 / 5

Actionability

For an instruction-only skill the guidance is concrete: explicit formulas ("SAM = TAM × 0.40 × 0.30 × 0.60 = $720M"), a fully worked numeric example, named data sources per methodology, and quantified heuristics (2-5% capture rate, 30% triangulation tolerance, red-flag thresholds). This lands on the "mostly executable guidance with minor gaps" anchor; it stops short of anchor 5 only because some guidance remains directional (e.g., "Review with industry experts") without a concrete procedure.

4 / 5

Workflow Clarity

Steps 1-6 (plus Quick Start) form a clear, well-sequenced process, and Step 6 "Validate and Triangulate" provides explicit checkpoints ("should be within 30%", "SOM > 10% in 5 years" red flags). It sits at anchor 4 rather than 5 because validation signals are listed but there is no explicit feedback loop instructing what to revise and re-check when a red flag triggers.

4 / 5

Progressive Disclosure

Scored against the actual bundle: of the six files referenced in the body (`resources/implementation-playbook.md`, `references/methodology-deep-dive.md`, `references/industry-templates.md`, and three `examples/` files), only `references/data-sources.md` exists — five references are dangling, and the directory is even misnamed (`resources/` vs `references/`). Additionally, substantial content that belongs in those files (industry-specific templates, presentation structures, worked examples) is inlined in the monolithic body. This matches anchor 2 (minimal effective structure, content inlined that belongs in separate files) rather than anchor 3, because most advertised navigation points are broken.

2 / 5

Total

12

/

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 solid, specific description with excellent natural trigger terms (TAM/SAM/SOM in both acronym and full form) for the startup domain. Its main defect is the absence of any "Use when..." trigger guidance, which caps completeness and leaves activation conditions entirely implicit.

Suggestions

Append an explicit trigger clause, e.g., "Use when the user asks about market size, market opportunity, TAM/SAM/SOM, or when preparing startup pitch materials, investor decks, or business plans."

Trim the subjective opener "Comprehensive" and instead name the concrete approaches offered (top-down, bottom-up, value theory) to sharpen specificity.

Add one or two common user phrasings such as "market opportunity" or "how big is the market" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain and several concrete calculation targets — "calculating Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM)" — with only minor padding from the word "Comprehensive". It falls between anchor 3 (1-2 concrete actions) and anchor 5 (fully comprehensive action list) because the single verb "calculating" applied to three named metrics is specific but not a broad set of distinct actions.

4 / 5

Completeness

The "what" is explicit and clear (market sizing methodologies for TAM/SAM/SOM for startup opportunities), but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3, which this fits exactly: clear what, when absent.

3 / 5

Trigger Term Quality

Strong natural keyword coverage: "market sizing", "TAM", "SAM", "SOM", and the full spellings of all three terms are exactly what a user asking for this work would say. A few natural synonyms ("market opportunity", "market analysis", "market research") are missing, matching the "good keyword coverage; a few natural terms missing" anchor rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The TAM/SAM/SOM terminology carves out a clear niche that is unlikely to fire for adjacent skills (e.g., competitive analysis, financial modeling), matching the "mostly distinct" anchor. Minor overlap risk remains with general business-planning or market-research skills since "market sizing methodologies" is broadly phrased, so it does not reach the clear-niche anchor 5.

4 / 5

Total

15

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/market-sizing-analysis/SKILL.md

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.