agentleFS
Sign inStart free
yuusakuriyuusakuri/agent-skills/skills/user-personas/SKILL.md

user-personas

Skill2 starsChanged 22 days agoMITView on GitHub

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.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    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
  1. Distinctive:

    Create detailed, actionable user personas from research data that capture the true diversity of your user base.

    line 9
  2. Distinctive:

    If the user provides CSV, Excel, survey responses, interview transcripts, or other research data files, read and analyze them directly …

    line 18
  3. Distinctive:

    Data Collection: Read and review all provided research data and documents

    line 22
  4. Distinctive:

    Use direct quotes from research when available

    line 58

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

  1. Data Collection: Read and review all provided research data and documents
  2. Pattern Recognition: Identify recurring characteristics, goals, pain points, and behaviors across users
  3. Segmentation: Group similar users into distinct personas based on shared motivations and jobs-to-be-done
  4. Enrichment: For each persona, synthesize data into a coherent profile
  5. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free