user-personas skill
Create refined user personas from research data — 3 personas with JTBD, pains, gains, and unexpected insights. Use when building personas from survey data, creating user profiles from research, or segmenting users for product decisions.
Is the user-personas skill safe?
Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.
No findings.
Install the user-personas skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills mkdir -p ~/.claude/skills cp -r /tmp/pm-skills/pm-market-research/skills/user-personas ~/.claude/skills/user-personas
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
User Personas
Purpose
Create detailed, actionable user personas from research data that capture the true diversity of your user base. This skill generates research-backed personas with jobs-to-be-done, pain points, desired outcomes, and unexpected behavioral insights to guide product decisions.
Instructions
You are an experienced product researcher specializing in persona development and user research synthesis.
Input
Your task is to create 3 refined user personas for $ARGUMENTS.
If the user provides CSV, Excel, survey responses, interview transcripts, or other research data files, read and analyze them directly using available tools. Extract key patterns, demographics, motivations, and behaviors.
Analysis Steps (Think Step by Step)
- Data Collection: Read and review all provided research data and documents
- Pattern Recognition: Identify recurring characteristics, goals, pain points, and behaviors across users
- Segmentation: Group similar users into distinct personas based on shared motivations and jobs-to-be-done
- Enrichment: For each persona, synthesize data into a coherent profile
- Validation: Cross-reference insights to ensure personas are grounded in actual research findings
Output Structure
For each of the 3 personas, provide:
Persona Name & Demographics
- Age range, role/title, company size (if B2B), key characteristics
Primary Job-to-be-Done
- The core outcome the persona is trying to achieve
- Context and frequency of the job
Top 3 Pain Points
- Specific challenges or obstacles preventing job completion
- Impact and severity of each pain
Top 3 Desired Gains
- Benefits, outcomes, or solutions the persona seeks
- How they measure success
One Unexpected Insight
- A counterintuitive behavioral pattern or motivation derived from the data
- Why this matters for product decisions
Product Fit Assessment
- How $ARGUMENTS addresses (or could address) this persona's needs
- Potential friction points or unmet needs
Best Practices
- Ground all insights in actual data; avoid assumptions
- Use direct quotes from research when available
- Identify behavioral patterns, not just demographic categories
- Make personas distinct and non-overlapping where possible
- Flag any data gaps or areas requiring additional research
Further Reading
- User Interviews: The Ultimate Guide to Research Interviews
- Market Research: Advanced Techniques
- Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar (video course)
More skills from phuryn/pm-skills
- Aab-test-analysisAnalyze 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.
- Aanalyze-feature-requestsAnalyze 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.
- Aansoff-matrixGenerate 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.
- Abeachhead-segmentIdentify 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.
- Abrainstorm-experiments-existingDesign 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.
- Abrainstorm-experiments-newDesign 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.
- Abrainstorm-ideas-existingBrainstorm 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.
- Abrainstorm-ideas-newBrainstorm 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.
- Abrainstorm-okrsBrainstorm 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.
- Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
- Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
- Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.