Skip to content
Skills Library
Management & product · Analysis

validate-segment

/validate-segment

The Beachhead picker. Reads who is behind the top pains: their role, their context, the tools they already pay for and how often they complain. Picks the one group to build for first, with the evidence for and against. Use when the user asks "who is my customer", "who should I target", "which niche first", "pick a beachhead", or "who feels this most".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: segments.py

What it does and when to use it

The Beachhead picker. Reads who is behind the top pains: their role, their context, the tools they already pay for and how often they complain. Picks the one group to build for first, with the evidence for and against. Use when the user asks "who is my customer", "who should I target", "which niche first", "pick a beachhead", or "who feels this most".

Triggers from the description

who is my customerwho should I targetwhich niche firstpick a beachheadwho feels this most

Arguments

/validate-segment [theme]
Original author description

The Beachhead picker. Reads who is behind the top pains: their role, their context, the tools they already pay for and how often they complain. Picks the one group to build for first, with the evidence for and against. Use when the user asks "who is my customer", "who should I target", "which niche first", "pick a beachhead", or "who feels this most".

How it works

  1. The tool
  2. Step 1: run the table
  3. Step 2: pick one beachhead
  4. Step 3: write validator/segment.md
  5. Step 4: tell the user
  6. Honest limits, say them once
  7. Output
Original SKILL.md headings · 91 lines, 592 words
SKILL.md preview
---
name: validate-segment
description: >-
  The Beachhead picker. Reads who is behind the top pains: their role, their context, the tools
  they already pay for and how often they complain. Picks the one group to build for first, with
  the evidence for and against. Use when the user asks "who is my customer", "who should I
  target", "which niche first", "pick a beachhead", or "who feels this most".
argument-hint: "[theme]"
---

# validate-segment

A startup that sells to everyone sells to no one. This skill picks the one
group to build for first: the people who feel the top pain hardest, already
spend money on it, and can be found. The table comes from a script. The
choice is yours to argue, but only from that table and from real quotes.

What the user typed after `/validate-segment`: `$ARGUMENTS`

## The tool

```bash
python3 "${CLAUDE_SKILL_DIR}/segments.py" [--dir validator] [--min 3]
```

If the path is not expanded, use the base directory Claude Code printed for
this skill. It needs `validator/labels.jsonl`, so run `/validate-cluster` first.
`/validate-pain` should have run too, because you will need `pain.md`.

## Step 1: run the table

Run `segments.py`. It writes `validator/segments.md` and `segments.json` with two
cuts of the same complaints:

- **By stated role**: what the post says the writer does (recruiter, founder).
  Plurals and articles are merged ("Recruiters", "a recruiter").
- **By community**: where it was said (a subreddit, Hacker News, an app's
  reviews). Most posts never state a role, so the place is often the better
  clue to who someone is.

Each group shows its size, how many different people, money and workaround
signals (the same rules as the Pain Index), intensity and its top themes.
Lower `--min` to 2 if the data is small, and say that you did.

## Step 2: pick one beachhead

Read `segments.md` and `pain.md`. Pick ONE group by these four tests, in order:

1. **Feels a pain worth money.** Their top themes are the ones `pain.md` rated
   worth money or real.
2. **Already spends.** Money signals, and tools they named in `tried`
   (`themes.json`). A group with workarounds and no money talk is a maybe.
3. **Can be reached.** A community you can post in, or a role you can search
   for on LinkedIn. A group you cannot find is not a beachhead.
4. **Is big enough to matter**, now or as a first step to a bigger group.

If `idea.json` names a target and the data points elsewhere, say so plainly,
with the numbers. Do not edit `idea.json` yourself. The user decides whether to
change the target.

## Step 3: write validator/segment.md

```
# Beachhead: <group>

Why them: <the numbers from segments.md: complaints, people, money, workaround, top theme>
Against: <what is weak: small, few money signals, hard to reach, mostly one community>
In their words: <two or three quotes, each with its ID and link>
Runner-up: <the next group and why it lost>
Where to find them: <communities, job titles, events, newsletters, with links where known>
```

Quotes come only from the `quote` field in `labels.jsonl` (look them up with
`python3 "${CLAUDE_SKILL_DIR}/../validate-mine/store.py" show <id>` for the link),
or from `pain.md`. Those passed a word-for-word check. Anything you put in your
own words goes without quotation marks.

Mark every "where to find them" item you did not see in the data as a
suggestion, not a finding.

## Step 4: tell the user

Give them the beachhead in one line, the strongest number for it, the strongest
number against it, and the runner-up. Ask whether they agree before
`/validate-wtp` prices for that group.

## Honest limits, say them once

Roles come only from what people chose to say about themselves, so the role
cut is small and skews towards people who introduce themselves. Communities
are a proxy: not everyone in r/recruiting is a recruiter. Treat the beachhead
as the best bet from public talk, to be confirmed in interviews
(`/validate-interview`).

## Output

`validator/segments.md`, `validator/segments.json`, `validator/segment.md`.

Next: `/validate-wtp` reads what this group says about money.
Files in this package (2)
  • SKILL.md 4 KB
  • segments.py 6 KB

Versions

The database has no other skills named validate-segment.

Database snapshot: 13.11.2026 · package version 6123f37b384a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100beachhead-segment
    Scores candidate segments on Burning Pain, Willingness to Pay, Winnability and Referral Potential, with blocking gates, to pick your highest-priority beachhead. Use when choosing a first market or customer segment; the confirmed beachhead is written to brain Section 2 only on your say-so.
  • 85beachhead-segment
    Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
  • 100beachhead-segment-selection
    Use when the user has several possible markets and must choose one to win first - which industry, which company size, which grade level or subject, which kind of buyer. Also use when the user mentions beachhead, first market, ideal first segment, "we could serve ten industries,…
  • 100segmentation
    Segment a market or user base by needs and behavior — not just demographics — then size, score, and pick a beachhead segment with a defensible rationale. Use when someone says "segment this market", "who should we target first", "find our beachhead", "break our users into…
  • 100market-entry-analysis
    Use when sequencing market entry — geo / segment / vertical, beachhead selection, regulatory-delta. Triggers on 'should we enter market X', 'which segment first'.
  • 100reddit-demand
    Validate demand for a product, feature or content idea from Reddit - find threads where people describe the problem, ask for recommendations, complain about current tools or say what they would pay for - and summarize pains, workarounds, alternatives mentioned and exact…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.