market-segments
by phurynUse market-segments to identify 3-5 distinct customer segments with demographics, jobs-to-be-done, pain points, desired outcomes, and product fit. It supports market-segments for Market Research, target audience selection, new market evaluation, and clearer segmentation decisions.
This skill scores 70/100, which means it is worth listing for users who need a guided market-segmentation workflow, but it is not yet a high-confidence install for fully hands-off execution. The repository gives enough structure for agents to trigger the skill and follow a real analysis process, though directory users should expect some reliance on their own judgment because the supporting assets and executable aids are sparse.
- Clear trigger language for market segmentation, target audiences, and new market evaluation.
- Concrete workflow for producing 3-5 non-overlapping segments with demographics, JTBD, and product-fit analysis.
- Valid frontmatter and a substantial SKILL.md body with multiple headings and stepwise instructions, indicating real operational content.
- No scripts, references, resources, or install command, so agents have to rely on the markdown guidance alone.
- Output structure is partially truncated in the evidence, limiting confidence about how prescriptive the final deliverable really is.
Overview of market-segments skill
What market-segments does
The market-segments skill helps you turn a broad market into 3-5 usable customer segments with demographics, jobs-to-be-done, pain points, desired outcomes, and product fit analysis. It is best for Market Research tasks where you need a decision-ready segmentation view, not a generic brainstorm.
Who should use it
Use the market-segments skill if you are deciding which audience to target, comparing new markets, refining positioning, or pressure-testing whether your product solves a real need for different buyer groups. It is most useful when the question is “which segments matter most?” rather than “write copy for everyone.”
What makes it different
Compared with a normal prompt, this skill pushes for distinct, non-overlapping segments and asks you to evaluate opportunity, not just list audience traits. That makes it more useful when you need a practical market-segments guide for prioritization, TAM thinking, or launch planning.
How to Use market-segments skill
Install and open the right files
Use the market-segments install flow with npx skills add phuryn/pm-skills --skill market-segments. Then read SKILL.md first, since this repository does not include extra helper files like rules/, references/, or scripts. The skill is compact, so the main value comes from understanding the prompt shape and adapting it to your own market context.
Give the skill enough market context
The skill works best when you provide a specific product, category, or market question in $ARGUMENTS. Strong inputs include the product type, target geography, pricing model, customer type, and any existing research. Weak inputs are vague requests like “segment the market” because they leave the model guessing what level of segmentation is useful.
Shape your request for better output
A good market-segments usage prompt names the decision you need to make and the evidence available. For example: “Analyze segments for a B2B expense management app in mid-market US companies using the attached survey notes and competitor list; identify 3-5 non-overlapping segments and rank by fit and growth.” This is better than a generic ask because it clarifies scope, input sources, and the output format.
Workflow that usually produces the best result
Start broad, then narrow. First ask for candidate segments and opportunity signals, then refine based on your sales motion, ICP, or market constraints. If you already have customer interviews, win/loss notes, or CRM exports, feed them in directly; the skill is designed to synthesize those inputs into cleaner segment definitions for Market Research work.
market-segments skill FAQ
Is market-segments only for new products?
No. The market-segments skill is also useful for repositioning, entering adjacent markets, refining an ICP, or checking whether an existing market is actually made of several different buyers. It is especially helpful when the same product may solve different jobs for different audiences.
How is this different from a standard prompt?
A standard prompt often produces broad audience descriptions. The market-segments skill is more structured: it pushes for 3-5 distinct segments, compares their needs, and surfaces opportunity differences. That makes it more decision-oriented for Market Research, especially when you need to prioritize rather than describe.
What if I do not have research data yet?
You can still use it, but the results will be directional rather than validated. If you lack direct research, provide whatever you do have: product notes, competitor examples, sales anecdotes, or market assumptions. The skill is most reliable when it can ground segments in real evidence instead of pure inference.
When should I not use it?
Do not use market-segments if you only need a single ICP statement, a persona for marketing copy, or a full GTM plan. It is focused on segmentation and opportunity analysis, so broader strategy work may need a different skill or a follow-up prompt.
How to Improve market-segments skill
Provide better raw material
The biggest quality jump comes from better inputs: customer interview notes, firmographic data, search trends, CRM patterns, or product usage logs. If you want the market-segments skill to produce sharper segments, include real differences in behavior, budget, urgency, or context rather than asking it to invent those differences.
Ask for separation, not just description
Common failure mode: segments that sound different but are actually the same audience with different labels. Prevent that by asking for distinct segmentation logic, expected size, and why each segment is meaningfully separate. For example, request that each segment be validated by a unique JTBD or buying trigger.
Iterate on fit and prioritization
After the first pass, ask the skill to tighten the top 2 segments, remove weak overlaps, or re-rank by revenue potential versus ease of reach. That second iteration usually improves the final market-segments guide more than adding more segments, because it forces clearer tradeoffs and better decision quality.