mcpbeat Sign in

User Personas Agent 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.

761 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
24819
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/phuryn/pm-skills --skill user-personas

The instruction itself

8 sections, as written by the author

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

Other skills for the same job

different authors, same section of the catalogue
Content Research Writer
by frostant
×10

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

4k tokens
Lead Research Assistant
by frostant
×8

Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.

2k tokens
Notebooklm
by ZhanlinCui
×6

Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.

26k tokens scripts
Biorxiv Database
by christophacham
×4

Efficient database search tool for bioRxiv preprint server. Use this skill when searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs, or conducting literature reviews.

9k tokens scripts
Openalex Database
by christophacham
×4

Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.

13k tokens scripts
Uspto Database
by christophacham
×4

Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.

21k tokens scripts
Denario
by christophacham
×3

Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication. This skill should be used when generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format. Supports end-to-end research pipelines with customizable agent orchestration.

11k tokens
Hypogenic
by christophacham
×3

Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.

7k tokens

How to use it

Copy the folder

Take phuryn/user-personas from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.