Skip to content
SkillModel-led568 tokens in use

market-segments

Identify three to five distinct customer segments and evaluate each one's jobs to be done, pains, product fit and competing alternatives.

680 stars on the repository MIT Licensephuryn/product-engineering · product/skills/market-segments
claude plugin install product@product-engineering
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing market-segments costs

28tokens idle
568tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure23/25
  • Examples0/15
  • Output10/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance100
  • Community44
  • Maturity4
  • Momentum40

market-segments has an agent split the addressable market for a product into three to five distinct, non-overlapping customer segments and profile each one. It reads any research, market studies or segmentation documents you supply and looks for behavioral patterns and distinct needs.

Each segment gets a profile with size, demographics, jobs to be done, pains, desired gains, product fit and the competing solutions it uses today.

What You Get

  • Three to five named segments that do not overlap
  • A profile per segment: overview, demographics or firmographics, jobs to be done, pains and desired gains
  • A product fit analysis with adoption barriers for each segment
  • The existing solutions and workarounds each segment uses

Common Use Cases

  • Exploring who a new product could serve
  • Prioritizing target audiences for a launch
  • Evaluating a new market before expanding into it
  • Feeding the beachhead-segment and value-proposition skills with defined segments

What Makes It Unique

The skill defines a good segment as a group with a distinct job and pain, and its closing check asks whether the owner can say which segment to explore first. It flags segments that need more research. It is the segmentation step in the product pack, positioned ahead of beachhead-segment.

Under The Hood

The skill is a single SKILL.md of instructions with no scripts or linked files. The agent reads any research files you hand it and reasons from them. The skill does not tell the agent to fetch web pages, call services, run commands or write files.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers