market-segments
Skill2 starsChanged 10 days agoMITView on GitHub
Identify 3-5 potential customer segments with demographics, JTBD, and product fit analysis. Use when exploring market segments, identifying target audiences, evaluating new markets, or learning how to segment a market.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
If research data, market studies, customer databases, or existing segmentation documents are provided, read and analyze them directly.
- Distinctive: line 22
Market Exploration: Consider the full addressable market for $ARGUMENTS
- Distinctive: line 24
Segment Definition: Create 3-5 distinct, non-overlapping customer segments
- Distinctive: line 66
Ensure segments are measurable, accessible, and distinct
- Distinctive: line 69
Consider both greenfield opportunities and underserved segments
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Market Segments
Purpose
Identify and analyze 3-5 distinct customer segments for your product, understanding their unique jobs-to-be-done, desired outcomes, pain points, and product fit. Use this skill to evaluate market opportunities, prioritize target audiences, or expand into new market segments.
Instructions
You are a strategic market research expert skilled in market segmentation, customer profiling, and total addressable market (TAM) analysis.
Input
Your task is to identify and analyze potential customer segments for $ARGUMENTS.
If research data, market studies, customer databases, or existing segmentation documents are provided, read and analyze them directly. Look for behavioral patterns, demographic clusters, and distinct needs across segments.
Analysis Steps (Think Step by Step)
- Market Exploration: Consider the full addressable market for $ARGUMENTS
- Segmentation Criteria: Identify logical segmentation dimensions (behavioral, demographic, firmographic, needs-based)
- Segment Definition: Create 3-5 distinct, non-overlapping customer segments
- Characterization: For each segment, synthesize profiles and validate distinctness
- Opportunity Assessment: Evaluate market size, growth potential, and competitive intensity per segment
Output Structure
For each of the 3-5 segments, provide:
Segment Name & Overview
- Clear, memorable segment identifier
- Size estimate (% of total market or absolute numbers if data available)
- Growth trajectory and market dynamics
Key Demographics & Firmographics
- Core characteristics (age, role, company size, industry, geography, etc.)
- Decision-maker profiles if B2B
Jobs-to-be-Done
- Primary job and desired outcome for this segment
- Frequency, context, and stakes of the job
- Success criteria and desired outcomes
Key Pain Points & Obstacles
- Barriers to job completion specific to this segment
- Consequences of not solving the problem
Desired Gains & Success Factors
- What outcomes matter most to this segment
- Preferred solution characteristics
- Cost and time constraints
Product Fit Analysis
- How well $ARGUMENTS serves this segment's needs
- Unique value proposition for this segment
- Potential adoption barriers or resistance
Competitive Landscape
- Existing solutions or workarounds this segment uses
- Alternative approaches or competitors
Best Practices
- Ensure segments are measurable, accessible, and distinct
- Prioritize segments with clear jobs-to-be-done and pain points
- Validate segment assumptions with available data
- Consider both greenfield opportunities and underserved segments
- Flag segments requiring additional market research
Further Reading
Other versions8 projects use a version of this.
Word for word · 8
- The-Utopia-Studio/skills★ 6100% same
- Adhamxon/claude-code-skills★ 2100% same
- skytiger6724/qwen-skills★ 2100% same
- daviszhen/agent-skills★ 1100% same
- miovrag/claude-skills★ 1100% same
- maeng777/claude-skills★ 0100% same
- stefanomartiradonna/claude-skills★ 0100% same
- vijaysuperpositionist/skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository100 other files it gives its agents.
- ab-test-analysisSkill
- analyze-feature-requestsSkill
- ansoff-matrixSkill
- api-and-interface-designSkill
- beachhead-segmentSkill
- brainstorm-experiments-existingSkill
- brainstorm-experiments-newSkill
- brainstorm-ideas-existingSkill
- brainstorm-ideas-newSkill
- brainstormingSkill
- brainstorm-okrsSkill
- browser-testing-with-devtoolsSkill
- business-modelSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- cohort-analysisSkill
- competitive-battlecardSkill
- context-engineeringSkill
- customer-journey-mapSkill
- debugging-and-error-recoverySkill
- define-hypothesisSkill
- define-jtbd-canvasSkill
- define-opportunity-treeSkill
- define-problem-statementSkill
- deliver-acceptance-criteriaSkill
- deliver-edge-casesSkill
- deliver-prdSkill
- deprecation-and-migrationSkill
- develop-solution-briefSkill
- discover-competitive-analysisSkill
- discover-interview-synthesisSkill
- discover-market-sizingSkill
- document-architectureSkill
- documentation-and-adrsSkill
- draft-ndaSkill
- dummy-datasetSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- grammar-checkSkill
- growth-loopsSkill
- gtm-motionsSkill
- gtm-strategySkill
- ideal-customer-profileSkill
- identify-assumptions-existingSkill
- identify-assumptions-newSkill
- incremental-implementationSkill
- intended-vs-implementedSkill
- interview-meSkill
- interview-scriptSkill
- job-storiesSkill
- lean-canvasSkill
- marketing-ideasSkill
- measure-experiment-designSkill
- metrics-dashboardSkill
- modern-web-guidanceSkill
- monetization-strategySkill
- north-star-metricSkill
- observability-and-instrumentationSkill
- outcome-roadmapSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

