Skip to content
SkillModel-led1,240 tokens in use

beachhead-segment

Choose the first customer segment to win by scoring candidates on burning pain, willingness to pay, winnable share and referral potential.

680 stars on the repository MIT Licensephuryn/product-engineering · product/skills/beachhead-segment
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 beachhead-segment costs

31tokens idle
1,240tokens in use
1,311tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. 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
  • Structure17/25
  • Examples0/15
  • Output12/15
  • Size15/15
  • Resources15/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

beachhead-segment helps an agent pick the first market a product should win before it expands. It lists candidate segments, scores each on four criteria, and recommends one with the evidence behind it.

The method follows Geoffrey Moore’s beachhead strategy from Crossing the Chasm. Every displayed score names its scale, and the output ends with a first acquisition test. A 90-day plan is added when you ask for it.

What You Get

  • A scored shortlist of three to five segments across the four criteria
  • One recommended beachhead with pain, pricing and share evidence
  • Referral and expansion paths to adjacent segments
  • A first acquisition test, and a 90-day plan or roadmap on request

Common Use Cases

  • Choosing which customer group a new product targets first
  • Deciding where to focus when time and budget are limited
  • Checking go-to-market assumptions against what early adopters say
  • Explaining to a team why one segment beats the runner-up

What Makes It Unique

The skill pairs the four classic beachhead criteria with rules that tie the answer to its evidence: every score names its scale, assumptions behind a market-share estimate are labelled, and the run closes with a check that each score has a source and the owner can say why the winner beats the runner-up. It also sits in a pack where it feeds the propose, value-proposition and value-curve skills.

Under The Hood

The skill is a single SKILL.md of instructions with no scripts. It loads into the agent’s context when the work matches, and the agent does the reasoning from the product context you pass in. The text mentions interviews, surveys and market research as ways to gather evidence, but the skill itself runs no commands, makes no calls and writes no files. A receipts.md file beside it records where each rule came from and is read only when a rule’s edge is unclear.

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