CtrlK
BlogDocsLog inGet started
Tessl Logo

market-sizing

Estimate market, segment, or opportunity size with transparent assumptions and uncertainty. Use for TAM/SAM/SOM, sizing scenarios, or comparing the scale of possible opportunities.

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 clear, actionable 7-step market-sizing workflow with concrete skill/lane routing and explicit validation checkpoints, organized into clean self-contained sections. Its only weakness is mild redundancy — the report-handoff rule and source-access guardrail are repeated and could be consolidated to save tokens.

Suggestions

Consolidate the report-handoff obligation so it is stated once (e.g., in step 7) rather than repeated across 'Related Skills' and step 7 with reinforcing clauses, removing the redundant 'This handoff is mandatory... do not infer a waiver' elaboration.

Tighten the Source Access Guardrail section to avoid restating step 3's source-gathering guidance; keep only the stop/continue decision rule that step 3 does not already cover.

The recurring 'label the gap and explain how it affects confidence' phrasing appears in both the guardrail and step 3 — define the gap-labeling expectation once and reference it.

DimensionReasoningScore

Conciseness

The body is efficient and does not explain concepts Claude already knows, but the report-handoff obligation is belabored (Related Skills, step 7, plus 'This handoff is mandatory... do not infer a waiver...') and the Source Access Guardrail restates points already in step 3's source gathering, so it could be tightened.

2 / 3

Actionability

Gives concrete, executable routing — specific skills ($visualize-data, $build-report, $jupyter-notebooks, $Spreadsheets, $validate-data, $gather-business-context), specific context lanes (~~structured_data, ~~company_docs, ~~team_communication, ~~dashboards_or_bi), and an explicit top-down/bottom-up/value-based/mixed decision framework; for an instruction-only skill this is specific and copy-ready.

3 / 3

Workflow Clarity

A clearly numbered 7-step sequence (Frame → Choose approach → Gather sources → Separate facts/assumptions → Build model → Test sensitivity → State estimate) with explicit checkpoints: the stop-if-required-source-missing guardrail, a sensitivity-test step, source verification before concluding, and a $validate-data review handoff.

3 / 3

Progressive Disclosure

No bundle files exist, and per the guideline a self-contained skill with no need for external references scores 3 with well-organized sections; the body is cleanly sectioned (Related Skills, Skill Configuration, numbered Workflow) with one-level $skill routing rather than deeply nested file references.

3 / 3

Total

11

/

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, names multiple concrete sizing actions, includes an explicit 'Use for' trigger with natural terms (TAM/SAM/SOM), and carves out a distinct niche. It cleanly satisfies all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Estimate market, segment, or opportunity size', 'comparing the scale of possible opportunities', and explicit output types (TAM/SAM/SOM, sizing scenarios) — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Estimate market, segment, or opportunity size with transparent assumptions and uncertainty') and when ('Use for TAM/SAM/SOM, sizing scenarios, or comparing the scale'), with an explicit 'Use for' trigger clause.

3 / 3

Trigger Term Quality

Includes the canonical natural terms users say for this task — 'TAM/SAM/SOM', 'market', 'opportunity size', 'sizing scenarios' — giving good coverage of natural trigger language.

3 / 3

Distinctiveness Conflict Risk

The market/opportunity-sizing niche with TAM/SAM/SOM triggers is a clear, distinctive domain unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
XiaomiMiMo/MiMo-Code
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.