persona-definition

Define evidence-based user personas from multiple data sources.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hpsgd/claude-marketplace --skill persona-definition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: persona-definition
Source: https://github.com/hpsgd/claude-marketplace/tree/main/plugins/product/ux-researcher/skills/persona-definition
Command: npx skills add https://github.com/hpsgd/claude-marketplace --skill persona-definition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Personas are essential for aligning product decisions with real user needs, but many teams rely on demographics or stereotypes instead of evidence-based profiles.

Core Features & Use Cases

  • Grounded personas built from multiple data sources (tickets, interviews, analytics)
  • Clear context sections (segment, goals, frustrations, behavior patterns)
  • Validation checks to ensure personas map to real customer segments

Quick Start

Write a persona for the most critical user segment in your product, using at least three data points per attribute.

Frequently Asked Questions about persona-definition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create data-driven user personas from multiple research sources?

Yes, you can validate existing user segments by applying validation checks against newly gathered data sources. This process ensures your current behavioral profiles accurately map to real customer segments rather than relying on outdated demographic stereotypes.

How many data sources do I need for a validated persona?

You need at least three data points per attribute to build a validated persona. Gathering evidence from multiple data sources such as analytics, tickets, and interviews ensures your user segments are grounded in real behavioral patterns instead of assumptions.

What is the best way to structure a persona for product discovery?

The best way to structure a persona for product discovery is to use a structured format detailing segment context, goals, frustrations, and behavior patterns. This ensures product decisions align with validated, data-supported user needs throughout the design process.

Why should I use evidence-based personas instead of demographic profiles?

You should use evidence-based personas because demographic profiles often rely on stereotypes rather than real user needs. Grounding your user segments in multiple data sources ensures product decisions are driven by validated behavioral patterns.

When should I not use this structured persona definition approach?

You should not use this structured persona definition approach when you lack access to multiple data sources for validation. Without enough underlying evidence from interviews, analytics, or tickets, the resulting behavioral profiles may not accurately map to real customer segments.