CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

market-segments

Identify 3-5 potential customer segments with demographics, JTBD, and product fit analysis. Use when exploring market segments, identifying target audiences, evaluating new markets, or learning how to segment a market.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./pm-market-research/skills/market-segments/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured, instruction-only skill with a clear step sequence and a concrete, fielded output template that makes the deliverable unambiguous. The main costs are modest padding (role prompt, 'Think Step by Step', generic best practices) and analysis steps that give direction without calibration examples or explicit validation feedback loops.

Suggestions

Cut the role-persona line, the '(Think Step by Step)' label, and the Best Practices section that restates segmentation basics Claude already knows.

Add one compact example of a well-formed segment profile to calibrate output quality and make the analysis steps concrete.

Make validation actionable: state what to do when segments overlap (e.g., merge or re-split) rather than only 'validate distinctness'.

DimensionReasoningScore

Conciseness

The body is mostly efficient — the output template earns its tokens — but includes unnecessary padding Claude doesn't need: the role line 'You are a strategic market research expert skilled in...', the 'Analysis Steps (Think Step by Step)' label, and a Best Practices section restating segmentation basics ('Ensure segments are measurable, accessible, and distinct') that Claude already knows. Not a 2 because the core instruction and output sections are tight and purposeful rather than padded.

3 / 5

Actionability

As an instruction-only skill, the concrete per-segment output template (Name & Overview, Demographics, JTBD with frequency/stakes, Pain Points, Gains, Product Fit, Competitive Landscape with specific sub-fields) gives highly actionable guidance. Minor gaps keep it from a 5: the analysis steps are high-level directives ('Consider the full addressable market') with no worked example segment or concrete method for size estimation.

4 / 5

Workflow Clarity

The five numbered steps (Market Exploration → Segmentation Criteria → Segment Definition → Characterization → Opportunity Assessment) form a clear sequence, and checkpoints are mostly present ('validate distinctness', 'Validate segment assumptions with available data', 'Flag segments requiring additional market research'). Not a 5 because these checkpoints are one-line mentions without explicit feedback loops describing what to do when validation fails (e.g., merge overlapping segments).

4 / 5

Progressive Disclosure

The single-file body is well organized with clear sections and clearly signaled one-level-deep external links under 'Further Reading'; no bundle files exist and no references are buried. Not a 5 because the skill slightly exceeds a simple single-purpose skill (~76 lines vs. the under-50-line simple-skill benchmark), and the detailed output template and further-reading links could optionally be split out to keep SKILL.md a leaner overview.

4 / 5

Total

15

/

20

Passed

Description

83%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 with an explicit 'Use when...' clause, concrete deliverable framing (3-5 segments, named analysis dimensions), and natural trigger phrases in third-person voice. The main gaps are a few missing synonyms in the trigger list and slightly incomplete coverage of the analysis dimensions the skill actually delivers.

Suggestions

Add common synonyms to the trigger clause, e.g., 'identifying target audiences, customer segments, or buyer personas'.

Mention the remaining analysis dimensions the skill covers (pain points, competitive landscape, market sizing) for full coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Identify 3-5 potential customer segments with demographics, JTBD, and product fit analysis' — naming the deliverable count and three analysis dimensions. It falls short of a 5 because coverage has minor gaps (no mention of pain points, segment sizing, or competitive analysis that the body actually performs), but it clearly exceeds anchor 3's '1-2 concrete actions' scope.

4 / 5

Completeness

It explicitly answers both questions: the 'what' ('Identify 3-5 potential customer segments with demographics, JTBD, and product fit analysis') and the 'when' with concrete trigger phrases ('Use when exploring market segments, identifying target audiences, evaluating new markets, or learning how to segment a market'). This matches the anchor-5 good example structure directly.

5 / 5

Trigger Term Quality

Trigger phrases like 'exploring market segments', 'identifying target audiences', 'evaluating new markets', and 'learning how to segment a market' are natural phrasings users would actually say. Not a 5 because a few common synonyms are missing from the trigger list — e.g., 'customer segments', 'target customers', 'buyer personas', or 'ICP' — which would round out coverage.

4 / 5

Distinctiveness Conflict Risk

Market segmentation is a fairly distinct niche with specific triggers ('segment a market', 'exploring market segments'), but there is minor overlap risk with closely related skills a suite might carry, such as general market-research, competitor-analysis, or product-market-fit skills. Not a 5 because adjacent research skills could plausibly fire on 'evaluating new markets'.

4 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

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