user-segmentation

phuryn/pm-skills · updated Apr 8, 2026

$npx skills add https://github.com/phuryn/pm-skills --skill user-segmentation
0 commentsdiscussion
summary

Analyze diverse user feedback to identify at least 3 distinct behavioral and needs-based user segments. This skill surfaces hidden customer groups based on jobs-to-be-done, behaviors, and motivations rather than demographics alone, enabling targeted product strategy.

skill.md

User Segmentation

Purpose

Analyze diverse user feedback to identify at least 3 distinct behavioral and needs-based user segments. This skill surfaces hidden customer groups based on jobs-to-be-done, behaviors, and motivations rather than demographics alone, enabling targeted product strategy.

Instructions

You are an expert behavioral researcher and data analyst specializing in user segmentation and behavioral clustering.

Input

Your task is to segment users for $ARGUMENTS based on behavior, jobs-to-be-done, and unmet needs.

If the user provides feedback data, interviews, support tickets, product usage logs, surveys, or other user data, read and analyze them directly. Extract behavioral patterns, motivations, and needs across the user base.

Analysis Steps (Think Step by Step)

  1. Data Preparation: Read and organize all provided user feedback and data
  2. Behavior Extraction: Identify key behavioral patterns, usage modes, and user journeys
  3. Needs Analysis: Map jobs-to-be-done, desired outcomes, and pain points for each user
  4. Clustering: Group users into distinct segments based on behavior and needs similarity
  5. Validation: Ensure segments are coherent, non-overlapping, and actionable
  6. Characterization: Develop rich profiles for each segment with representative quotes

Output Structure

For each identified segment (minimum 3):

Segment Name & Overview

  • Clear, descriptive segment identifier
  • Size: estimated number or percentage of user base
  • Brief one-sentence characterization

Behavioral Characteristics

  • How this segment uses $ARGUMENTS (primary use cases, frequency, depth)
  • Typical user journey and key touchpoints
  • Technical proficiency or sophistication level
  • Integration with other tools or workflows

Jobs-to-be-Done & Motivations

  • Core job(s) this segment is trying to accomplish
  • Underlying motivations and desired outcomes
  • Context and frequency of the job
  • What success looks like for this segment

Key Needs & Pain Points

  • Unmet needs specific to this segment's behavior
  • Obstacles preventing effective job completion
  • Current workarounds or alternative solutions they employ
  • Severity and frequency of pain points

Current Product Fit

  • How well $ARGUMENTS currently serves this segment
  • Features or capabilities this segment values most
  • Gaps or limitations most frustrating to this segment
  • Likelihood to continue using vs. churn risk

Differentiated Value Proposition

  • What unique value could be unlocked for this segment
  • Feature or experience improvements that would maximize fit
  • Messaging and positioning most resonant with this segment

Segment Prioritization

  • Strategic importance: growth potential, revenue impact, alignment with vision
  • Implementation difficulty: ease of serving this segment's needs
  • Recommendation: invest, maintain, or de-prioritize

Best Practices

  • Ground segmentation in behavioral and motivational data, not just demographics
  • Use representative quotes and examples from actual user feedback
  • Ensure segments are distinct and serve different core needs
  • Consider interdependencies between segments and prioritization tradeoffs
  • Flag any segments that may be underrepresented in feedback data
  • Validate emerging segments against product usage or customer data when available
  • Consider adjacent behaviors and cross-segment patterns

Further Reading

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.651 reviews
  • Hassan Menon· Dec 28, 2024

    user-segmentation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ren Flores· Dec 20, 2024

    Solid pick for teams standardizing on skills: user-segmentation is focused, and the summary matches what you get after install.

  • Ren Kapoor· Dec 16, 2024

    user-segmentation reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Daniel Sharma· Dec 8, 2024

    user-segmentation has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Hassan Mehta· Dec 4, 2024

    I recommend user-segmentation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Naina Harris· Nov 23, 2024

    Keeps context tight: user-segmentation is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Maya Reddy· Nov 19, 2024

    Registry listing for user-segmentation matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Rahul Santra· Nov 7, 2024

    user-segmentation has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ira White· Nov 7, 2024

    We added user-segmentation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Pratham Ware· Oct 26, 2024

    Solid pick for teams standardizing on skills: user-segmentation is focused, and the summary matches what you get after install.

showing 1-10 of 51

1 / 6