Individual skill
user-persona
Synthesizes interview notes, surveys, support tickets, and analytics into evidence-based user personas that drive design decisions, with every claim traced to source data. Use when someone asks "build personas from our research", "turn these interview notes into personas", "how many personas do we need", or "are our personas evidence-based". Do NOT use for sales-targeting ideal customer profiles with filterable firmographics and buying committees - use icp-persona-builder instead. Do NOT use for extracting jobs-to-be-done from research - use jtbd-extractor instead.
skills/user-persona/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- data Derived category
- design Derived category
- sales Derived category
- productivity Derived category
- research Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# User Persona Builder
Build personas that designers and PMs actually consult - grounded in observed behavior, not demographics invented for a slide. A persona is a research artifact, not a character. The costly failure this prevents is the decorative persona: a stock photo, a name, an age, and a made-up hobby that no design decision ever touches, which quietly teaches the team that research outputs are theater.
## Operating procedure
### Step 1: Gather inputs and enforce the evidence floor
Ask for the source material: interview notes or transcripts, survey results, support tickets, analytics, session recordings. Then apply the evidence rules:
- **Minimum for defensible personas: 8-12 interviews** across the target population; below 5, refuse to call the outputs personas - label them proto-personas (assumption maps) and recommend research first, offering to design it (pair with interview-guide-builder).
- Surveys and analytics alone cannot produce personas - they show what and how much, never why. They corroborate interview-derived clusters; they do not replace them.
- If there is no research at all, say so plainly and offer a research plan. Never fabricate a persona from team assumptions and present it as evidence.
