startup-business-analyst-market-opportunity

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

Quality

41%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/startup-business-analyst-market-opportunity/SKILL.md

Quality

Content

38%Scale 1-5

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

This skill provides a comprehensive but overly verbose walkthrough of market opportunity analysis. It covers the right topics and has a logical structure, but it over-explains concepts Claude already knows, lacks executable artifacts, and references files that don't exist in the bundle. The content would benefit significantly from trimming explanatory text, adding concrete examples with actual numbers, and properly structuring supporting materials into referenced files.

Suggestions

Reduce content by ~50% by removing explanations of basic concepts (what TAM/SAM/SOM are, what data sources exist) and generic advice Claude already knows. Focus on the specific formulas, thresholds, and decision points.

Extract the report template (Step 8) into a separate referenced file like 'resources/report-template.md' and provide the actual file in the bundle.

Add a concrete worked example with real numbers (e.g., a complete mini-analysis for a hypothetical SaaS product) rather than the current illustrative conversation snippet.

Either provide the referenced 'resources/implementation-playbook.md' and 'market-sizing-analysis skill' files, or remove those references to avoid dead-end navigation.

Dimension	Reasoning	Score
Conciseness	The skill is significantly verbose, with extensive explanations of concepts Claude already knows (what TAM/SAM/SOM are, how to calculate them, what data sources exist). The 'Use this skill when' / 'Do not use this skill when' sections are generic filler. The 'What This Command Does' section redundantly previews the steps that are then fully detailed. Tips like 'Be conservative on SOM' and 'Cite all data sources' are basic analytical practices Claude already understands.	2 / 5
Actionability	The skill provides structured steps and formulas (e.g., SAM = TAM × Geographic % × Product Fit % × Market Readiness %), which is somewhat concrete. However, there is no executable code, no actual data lookup examples, and the guidance remains at the level of structured instructions rather than copy-paste ready artifacts. The example usage is illustrative but not deeply actionable.	3 / 5
Workflow Clarity	The 9-step workflow is clearly sequenced and logically ordered. However, validation is limited to a single variance check (Step 5's 30% threshold) with no explicit feedback loop for error recovery. The 'Validation and Sanity Checks' in Step 8 is just a report section heading, not an actual validation step in the workflow. There's no checkpoint to verify data quality before proceeding.	3 / 5
Progressive Disclosure	The skill references 'resources/implementation-playbook.md' and a 'market-sizing-analysis skill' but no bundle files are provided, making these references unverifiable dead ends. The content is a monolithic ~200-line document that would benefit from splitting the report template, data source lists, and methodology details into separate files. The report template in Step 8 alone is substantial enough to warrant its own reference file.	2 / 5
	Total	10 / 20 Passed

Description

45%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 identifies a clear domain (market opportunity analysis) and a specific methodology (TAM/SAM/SOM), which gives it reasonable distinctiveness. However, it lacks a 'Use when...' clause, misses common synonym trigger terms like 'market sizing' or 'addressable market', and doesn't enumerate the full range of capabilities beyond TAM/SAM/SOM calculations.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about market sizing, addressable market, TAM, SAM, SOM, market opportunity, or go-to-market analysis'.

Expand the capability list to include specific outputs or sub-tasks, e.g., 'identifies target segments, estimates market size using top-down and bottom-up approaches, generates revenue projections'.

Include natural synonyms and related terms such as 'market sizing', 'addressable market', 'market research', 'business opportunity assessment' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (market opportunity analysis) and one concrete action (TAM/SAM/SOM calculations), but doesn't elaborate on what the analysis includes beyond that single methodology — e.g., competitor analysis, market sizing approaches, data sources, output format.	3 / 5
Completeness	Provides a 'what' (generate market opportunity analysis with TAM/SAM/SOM calculations) but has no 'when' clause or trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 3, and the 'what' itself is only moderately detailed, placing this at a 2.	2 / 5
Trigger Term Quality	Includes relevant terms like 'market opportunity analysis' and 'TAM/SAM/SOM' which are natural for users familiar with business strategy, but misses common synonyms and variations like 'market sizing', 'addressable market', 'market research', 'go-to-market', or 'business plan'.	3 / 5
Distinctiveness Conflict Risk	The specificity of TAM/SAM/SOM and 'market opportunity analysis' creates a fairly distinct niche that is unlikely to overlap with most other skills, though it could potentially conflict with broader business strategy or financial analysis skills.	4 / 5
	Total	12 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/startup-business-analyst-market-opportunity/SKILL.md
Commit: 57c135b

Reviewed: 15 hours 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.