market-research

When the user needs to estimate market size, understand market dynamics, or validate that a market opportunity is large enough to pursue.

Quality

51%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/market-research/SKILL.md

Quality

Content

62%

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

This is a solid market research skill with a well-structured workflow and clear output format that would guide Claude effectively through TAM/SAM/SOM analysis. Its main weaknesses are moderate verbosity (some best practices Claude already knows) and the lack of fully concrete worked examples—the examples use placeholders rather than demonstrating a complete calculation chain. The progressive disclosure could be improved by moving the extensive best practices and detailed output templates to referenced files.

Suggestions

Provide at least one fully worked-through example with real numbers showing every calculation step (e.g., 'Global developer tools market: $45B (Gartner 2024) → Developer productivity subset: 18% → $8.1B → North America: 42% → $3.4B TAM') rather than using $[X]B placeholders.

Move the 12-item 'Frameworks & Best Practices' section to a separate MARKET-RESEARCH-FRAMEWORKS.md file and keep only the 3-4 most critical principles inline (both top-down and bottom-up, vanity TAM warning, assumption sensitivity).

Trim the 'When to Use' section—the trigger phrases list is unnecessary since Claude can infer when market sizing is relevant from context.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient and covers genuinely useful frameworks, but includes some unnecessary verbosity—particularly in the 'When to Use' trigger phrases, the extensive 'Frameworks & Best Practices' section (some points like 'consider currency and purchasing power parity' are things Claude already knows), and the 'Related Skills' section which adds marginal value. Could be tightened by ~30%.	2 / 3
Actionability	The workflow steps are clear and the output format is well-specified with concrete table structures and formulas (e.g., customers x conversion x ACV). However, there's no executable code, no actual data sources with URLs, and the examples use placeholder values like '$[X]B' rather than showing a fully worked-through calculation. The guidance is structured but still somewhat abstract—it tells Claude what to produce rather than showing exactly how to compute it.	2 / 3
Workflow Clarity	The 7-step workflow is clearly sequenced with logical progression from market definition through estimation methods to assumption mapping. Step 7 (map assumptions) serves as a validation checkpoint, and the reconciliation step explicitly calls out investigating gaps >3x. The sensitivity analysis in best practices adds another verification layer. For a non-destructive analytical task, this level of workflow clarity is excellent.	3 / 3
Progressive Disclosure	The skill references related skills (competitive-analysis, prd-writing, roadmap-planning) which is good, but the main content is a long monolithic document. The extensive 'Frameworks & Best Practices' section (12 bullet points) and detailed output format could be split into referenced files. The content is well-organized with clear headers but everything is inline rather than appropriately distributed.	2 / 3
	Total	9 / 12 Passed

Description

40%

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 structured as a 'when' clause but lacks specificity about what the skill actually does — it describes the user's need rather than the skill's concrete capabilities. The market-related trigger terms provide some natural language coverage but miss important variations. The description would benefit significantly from listing specific actions and outputs the skill produces.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Calculates TAM/SAM/SOM, builds bottom-up and top-down market models, analyzes competitive landscape, and estimates revenue potential.'

Include additional natural trigger terms users would say, such as 'TAM', 'SAM', 'SOM', 'addressable market', 'market sizing', 'market research', 'market analysis'.

Restructure to lead with 'what it does' followed by a clear 'Use when...' clause, e.g., 'Estimates total addressable market (TAM/SAM/SOM) using top-down and bottom-up approaches... Use when the user asks about market size, market opportunity, or needs to validate a business idea.'

Dimension	Reasoning	Score
Specificity	The description lacks concrete actions. It mentions 'estimate market size', 'understand market dynamics', and 'validate market opportunity' but these are vague goals rather than specific actions the skill performs. There are no concrete outputs or methods described (e.g., 'calculate TAM/SAM/SOM', 'build bottom-up market models', 'analyze competitor landscape').	1 / 3
Completeness	The description addresses 'when' fairly well with 'When the user needs to...' but the 'what' is weak — it doesn't clearly describe what the skill actually does or produces. The 'when' clause doubles as a vague capability statement rather than providing explicit trigger guidance alongside concrete actions.	2 / 3
Trigger Term Quality	Includes some relevant natural keywords like 'market size', 'market dynamics', and 'market opportunity', which users might naturally say. However, it misses common variations like 'TAM', 'SAM', 'SOM', 'addressable market', 'market analysis', 'market research', 'go-to-market', or 'market sizing'.	2 / 3
Distinctiveness Conflict Risk	The focus on market sizing and market opportunity gives it some distinctiveness, but 'understand market dynamics' is broad enough to overlap with competitive analysis, business strategy, or general research skills. It could conflict with broader business analysis or strategy skills.	2 / 3
	Total	7 / 12 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: shawnpang/startup-founder-skills
Commit: 4ad31b4

Reviewed: 3 months 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.