persona

Generate behavioral user personas from product descriptions, user data, or research notes.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill persona-kalilurrahman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: persona
Source: https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts/tree/main/09-product-management/persona
Command: npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill persona-kalilurrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often build for vague, demographic-based personas that never influence real decisions. This Skill turns product descriptions, user research, or support data into behavioral personas that directly shape what you build and what you deliberately skip. ## Core Features & Use Cases - Behavioral Persona Generation: Creates 2-4 distinct personas defined by goals, pain points, behavior patterns, and decision processes rather than demographics. - Strategic Prioritization: Ranks personas as primary, secondary, or excluded, and mandates an anti-persona defining who you are explicitly not building for. - Product Decision Mapping: Each persona includes concrete product implications so every profile changes at least one build decision. - Use Case: Paste your product concept and support ticket themes, and receive a prioritized persona set saved as personas-[product-name].md that guides roadmap and UX choices. ## Quick Start Generate user personas from this product description and our recent user research notes, then save them to a markdown file.

Frequently Asked Questions about persona

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

FAQPage Schema
How do I create user personas from product research?

Provide your product description, user research, or support tickets as input. The Skill identifies distinct user segments by goals and behaviors, then generates 2-4 personas with pain points, decision patterns, and product implications saved to a markdown file.

What makes a behavioral persona different from a demographic persona?

Behavioral personas focus on goals, pain points, usage frequency, and decision processes rather than age or location. This ensures each persona directly changes at least one product decision instead of serving as marketing decoration.

How many personas should a product have?

Aim for 2-4 personas maximum. If you need more, you have not made hard enough prioritization choices. Personas that would drive identical product decisions should be merged into one.

What is an anti-persona and why do I need one?

An anti-persona defines a user segment you are explicitly not building for, with a strategic reason such as compromising the core experience. Knowing who to exclude prevents scope creep and unfocused feature requests.

What if I don't have enough user research to build personas?

The Skill will tell you when the input lacks enough context to differentiate personas and ask for user research, support data, or behavioral observations rather than fabricating generic profiles.