SKILL FILE

Persona Generator with AI

Build behavioural buyer and user personas with Pragmatic Institute use scenarios and Jobs-to-be-Done analysis — grounded in real research, not invented.

Download Skill File ↓

What this skill file teaches Claude

Drop one markdown file into your repo. Claude Code learns how to run this entire workflow.

1

Buyer vs User separation

For B2B especially, the buyer and the user are often different people with different motivations. Generated personas keep them distinct.

2

Use scenarios (Pragmatic format)

Persona + Goal + Problem + Frequency for each key workflow — actionable rather than descriptive.

3

Buying-process map

How B2B buyers evaluate, decide, and purchase — useful for sales and pricing decisions.

4

Jobs-to-be-done overlay

Layered on each persona so you see what they're trying to accomplish, not just demographics.

5

Evidence tracking

What's validated by research vs what's an inference. Honest about confidence.

6

Anti-personas defined

Who you're explicitly NOT building for — and why. As useful as the positive personas.

What you can build with this

New product launch

Build the persona library before the first line of code so the team agrees on who you're building for.

Update stale personas

Your personas were written 3 years ago. Re-run the skill with fresh interview snapshots to refresh them.

Onboard new team members

A new PM, designer, or marketer can read the persona doc and immediately understand who the customer is.

Get the full skill file

Everything above is 80% of the skill file. Download the complete version with full implementation details, agent prompts, and ready-to-run scripts.

Common questions

Pragmatic Marketing uses behavioural personas centred on use scenarios (Persona + Goal + Problem + Frequency) rather than demographic personas. It's more actionable for product decisions because each scenario maps to a feature or workflow.
For real personas, yes — interview snapshots, survey results, or customer behaviour data are the input. You can generate "starter" personas from internal hypotheses, but they should be validated with research before product decisions get made on them.
For most B2B products: 2–4 personas (1–2 buyers, 1–2 users). More than 4 usually means you haven't found the meaningful groupings.
Personas describe WHO the user is and how they behave. JTBD describes WHAT they're trying to accomplish. They're complementary — the persona doc usually includes JTBD statements per persona.
Names yes (easier to reference in conversation). Stock photos no — they signal "this is invented." Behavioural descriptions are more useful than visual archetypes.

Ready to automate?

SoloStack gives you every skill pre-installed — scraping, marketing, sales, CRM, and more. One repo. Every department.

Book a Call →