Agent Skill
Beachhead Segment skill
beachhead-segmentphuryn/pm-skillspm-go-to-market/skills/beachhead-segment/SKILL.md
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.
always on
58 tokname + description
once used
1,146 tokSKILL.md body
bundled files
0
repo stars
27kGitHub
Install the Beachhead Segment skill
Skills CLI (Claude Code, Codex, Cursor and others)
npx skills add https://github.com/phuryn/pm-skills --skill beachhead-segment
Claude Code, by hand (all projects)
git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills mkdir -p ~/.claude/skills cp -R /tmp/pm-skills/pm-go-to-market/skills/beachhead-segment ~/.claude/skills/beachhead-segment
For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.
What it costs your context
Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.
| When | What loads | Cost |
|---|---|---|
| Every session | Name and description | 58 tok |
| When the agent uses it | The SKILL.md instructions | 1,146 tok |
| Only if opened | No bundled files | — |
Until it is used, beachhead-segment costs about 23× less than the median MCP server we measured (1,362 tokens on every turn). Installing all 69 skills from phuryn/pm-skills would load 3,626 tokens of descriptions. Skills vs MCP study
Checks
Our checks found nothing to flag: it follows the Agent Skills specification's naming and size guidelines and doesn't pipe downloads into a shell.
Checked 2026-10-22 · method
What's inside
The headings of its SKILL.md. Read the full file on GitHub.
- Beachhead Segment
- Overview
- When to Use
- Key Evaluation Criteria
- 1. Burning Pain Point
- 2. Willingness to Pay
- 3. Winnable Market Share
- 4. Referral Potential
- How It Works
- Step 1: List Potential Segments
- Step 2: Research Pain Points
- Step 3: Assess Willingness to Pay
- Step 4: Evaluate Winnability
- Step 5: Identify Referral Pathways
- Step 6: Select Beachhead
- Input Format
- Output
- Framework
- Tips
- Further Reading
More skills from phuryn/pm-skills
- ab-test-analysisphuryn/pm-skills
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
27k54 tok idle · 818 in use - analyze-feature-requestsphuryn/pm-skills
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
27k45 tok idle · 425 in use - ansoff-matrixphuryn/pm-skills
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
27k44 tok idle · 1,071 in use - brainstorm-experiments-existingphuryn/pm-skills
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
27k48 tok idle · 465 in use - brainstorm-experiments-newphuryn/pm-skills
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
27k59 tok idle · 509 in use - brainstorm-ideas-existingphuryn/pm-skills
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
27k51 tok idle · 554 in use - brainstorm-ideas-newphuryn/pm-skills
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
27k49 tok idle · 437 in use - brainstorm-okrsphuryn/pm-skills
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
27k49 tok idle · 913 in use