CtrlK
BlogDocsLog inGet started
Tessl Logo

startup-business-analyst-market-opportunity

Generate comprehensive market opportunity analysis with TAM/SAM/SOM calculations

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/startup-business-analyst-market-opportunity/SKILL.md

The canonical home for this skill is startup-business-analyst-market-opportunity in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 a concrete, well-sequenced market-sizing methodology with formulas and validation, but it is padded with generic boilerplate and duplicated headers, and its single reference to supporting material is a dangling path with no actual bundle files. Progressive disclosure is weak because all detail lives inline.

Suggestions

Remove the generic '## Instructions' boilerplate and the '## Use this skill when / Do not use this skill when' sections that restate the description without adding detail, and merge the duplicate '## Instructions' and '## Instructions for Claude' headers.

Fix the dangling 'resources/implementation-playbook.md' reference by either creating the file or removing the pointer, and verify the 'market-sizing-analysis skill' dependency is real.

Move the large Section 1-9 report template into a referenced file (e.g. references/report-template.md) so SKILL.md stays a lean overview with one-level-deep navigation.

DimensionReasoningScore

Conciseness

The body is mostly efficient methodology with concrete formulas, but includes generic boilerplate ('Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.'), duplicated '## Instructions' and '## Instructions for Claude' headers, and Do/Don't padding, matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'. It is not a 4 because the boilerplate and redundancy are clearly trimmable.

3 / 5

Actionability

It provides concrete formulas (TAM = Σ Segment Size × ACV; SAM = TAM × Geographic % × Product Fit % × Market Readiness %), specific SOM percentages (2-3% Year 3, 4-6% Year 5), named data sources, and a defined report structure, fitting 'Mostly executable guidance; concrete code or commands with minor gaps'. As an instruction-only skill the absence of code is acceptable; it is not a 5 because there is no worked numeric example covering the common case.

4 / 5

Workflow Clarity

The process is clearly sequenced Step 1 through Step 9 with an explicit validation checkpoint (top-down within 30%, 'If variance > 30%, investigate and explain') and a dedicated 'Validation and Sanity Checks' section, matching 'Clear sequence with most checkpoints present; minor validation gaps'. It is not a 5 because the validation feedback loop is light (no re-computation loop) and checkpoints beyond the TAM variance check are descriptive rather than enforced.

4 / 5

Progressive Disclosure

Section structure exists, but the entire methodology/report template is inlined in SKILL.md and the one external reference ('resources/implementation-playbook.md') points to a file that does not exist in the bundle, plus a reference to an external 'market-sizing-analysis skill'; this matches 'Some structure but could be better organized; references present but not clearly signaled'. It is not a 4 because of the dangling reference and the lack of any real one-level-deep supporting files.

3 / 5

Total

14

/

20

Passed

Description

53%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 is specific and identifiable but incomplete: it states what the skill does without any explicit trigger guidance for when Claude should invoke it. Specificity and trigger coverage are adequate rather than comprehensive.

Suggestions

Add an explicit 'Use when...' clause to the description, e.g. 'Use when sizing a market, estimating TAM/SAM/SOM, or preparing an investor market-opportunity section.'

Broaden trigger terms with natural synonyms such as 'market sizing', 'addressable market', 'total addressable market', and 'serviceable obtainable market' to improve keyword coverage.

Tighten the action list to surface the validation/reporting deliverables (e.g., '...with bottom-up and top-down validation and a formatted report') for fuller specificity.

DimensionReasoningScore

Specificity

The description names the domain ('market opportunity analysis') and one concrete action set ('TAM/SAM/SOM calculations'), but does not enumerate the broader set of actions (e.g., bottom-up/top-down validation, report generation), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is above a 2 because the TAM/SAM/SOM framing is concrete, but below a 4 due to limited action coverage.

3 / 5

Completeness

A clear 'what' is present ('Generate comprehensive market opportunity analysis with TAM/SAM/SOM calculations') but there is no 'when' / 'Use when...' trigger guidance, so per the rubric guideline completeness is capped at 3, matching 'Has a clear what but when is missing or only weakly implied'. It is not a 4 because the when clause is entirely absent.

3 / 5

Trigger Term Quality

It surfaces relevant natural terms ('market opportunity analysis', 'TAM/SAM/SOM') that users would say, but misses common synonyms and variations such as 'market sizing', 'addressable market', or 'total addressable market', fitting the anchor 'Some relevant keywords but missing common variations or synonyms'. Not a 4 because coverage is narrow and concentrated in one phrase.

3 / 5

Distinctiveness Conflict Risk

The TAM/SAM/SOM framing carves a clear niche unlikely to collide with unrelated skills, matching 'Mostly distinct; minor overlap risk with closely related skills'. It is not a 5 because it could overlap with adjacent financial-projections or business-case skills without an explicit trigger boundary.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.