CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

market-research

Use when doing upstream market-research methodology — sizing a market as TAM/SAM/SOM computed BOTH top-down and bottoms-up (never a single unsourced number), planning a survey sample size with finite-population correction and per-segment minimums, or scoring candidate market segments against Kotler's measurable/substantial/accessible/differentiable/actionable criteria. Outputs always show the method and the assumptions. For market-research analysts and product-marketing at the sizing/survey/segmentation moment. Distinct from marketing-skill (campaign analytics, attribution, demand-gen) — this is the evidence-building methodology, not live-campaign optimization.

70

Quality

88%

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

The canonical home for this skill is market-research in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-engineered body: fully executable commands, a gated multi-step workflow, and clearly signaled one-level-deep references. The main costs are duplicated boundary-keeping (Do-NOT-use vs the Distinct-from table), an inline forcing-question library that should be a reference file, and a missing explicit recovery step for failed triangulation.

Suggestions

Move the forcing-question library (lines 122–146) to a reference file such as references/forcing_questions.md and keep a one-line pointer in SKILL.md — it trims ~25 lines from the always-loaded context and improves progressive disclosure.

Merge the "Do NOT use this skill to" paragraph with the "Distinct from" table into a single boundary section to remove the duplicated neighbor-skill enumeration.

Add an explicit recovery step to the sizing workflow for a failed triangulation flag (e.g., revisit assumptions register → adjust serviceable fraction → re-run market_sizer.py → re-check divergence) to close the validate-fix-retry loop.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific — no space is spent explaining concepts Claude already knows (Kotler, Cochran, TAM are cited, not taught). It falls short of lean because the "Do NOT use this skill to…" paragraph duplicates the "Distinct from" table, and the ~25-line forcing-question library is inline content that could live in a reference file.

4 / 5

Actionability

Commands are copy-paste ready and cover the common cases: `market_sizer.py --input market.json --method both --profile {b2b-saas|consumer|…}`, `sample_size_planner.py --population 62000 --confidence 0.95 --moe 0.05`, `python3 scripts/onboard.py --show`, a complete `/ar:setup` block, and a documented `--help`/`--sample`/`--output {human,json}` contract for every tool.

5 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with substantive checkpoints — "Reconcile the top-down/bottoms-up delta before quoting anything", "Fund the per-segment floors", "Drop segments failing the substantiality/accessibility gate" — and the sizer "flags failed triangulation". It stops short of 5 because the main workflow lacks an explicit recovery loop (what to do after a failed triangulation flag other than "reconcile"), and the brief step has no validation before sizing proceeds.

4 / 5

Progressive Disclosure

Structure is good: a dedicated References section lists three clearly-labeled one-level-deep files, scripts are tabulated, and the asset template is named. However, no bundle files (references/, scripts/, assets/) are present in this copy to verify, and the inline forcing-question library is content that belongs in a separate reference file, which keeps it below the clear-overview 5 anchor.

4 / 5

Total

17

/

20

Passed

Description

92%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 strong description: concrete, comprehensive capability enumeration with an explicit Use-when clause, a named audience, and an explicit boundary against the nearest neighbor skills. The only gap is a handful of natural trigger synonyms ("how big is the market", "addressable market") that users might phrase differently from the included jargon.

DimensionReasoningScore

Specificity

The description enumerates three concrete, comprehensive capabilities with methodology specifics: "sizing a market as TAM/SAM/SOM computed BOTH top-down and bottoms-up", "planning a survey sample size with finite-population correction and per-segment minimums", and "scoring candidate market segments against Kotler's measurable/substantial/accessible/differentiable/actionable criteria". Coverage is comprehensive with no minor gaps (the 4 anchor), and the voice is third-person/imperative so no voice penalty applies.

5 / 5

Completeness

Both questions are answered explicitly and concretely: the what is the three enumerated methodology capabilities, and the when is the opening "Use when doing upstream market-research methodology — sizing… planning… or scoring…" reinforced by "For market-research analysts and product-marketing at the sizing/survey/segmentation moment". This matches the 5 anchor (explicit what AND when with concrete trigger phrases) rather than the 4 anchor's "when could be more explicit".

5 / 5

Trigger Term Quality

Natural terms are present — "market-research", "sizing a market", "survey sample size", "market segments" — giving good keyword coverage. It falls short of the 5 anchor because common phrasings users actually say are missing: "how big is the market", "addressable market", "market size", and "competitive landscape" appear nowhere in the description.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche and actively disambiguates: "Distinct from marketing-skill (campaign analytics, attribution, demand-gen) — this is the evidence-building methodology, not live-campaign optimization". Trigger terms (TAM/SAM/SOM, survey sample size, segment scoring) are upstream-methodology-specific, so conflict risk with neighboring marketing skills is minimal.

5 / 5

Total

19

/

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: 13 missing

Warning

Total

14

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/market-research/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.