Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-persona-jtbd-analysis
Structured persona creation and JTBD analysis methodology - persona templates, ODI job step tables, pain point mapping, success metric quantification, and multi-persona segmentation
Passed 17 of 22 test cases with the skill, and 13 of 22 without it.
and 4 more in the full report
5 fixed12 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to clarify who we are building our automated data analysis assistant for before writing user stories. Please help us build formal user personas for a novice business analyst and an experienced data scientist. Ensure each persona profile outlines their core role, demographic attributes, a job step table formatted with action verbs and desired outcomes minimizing negative states, pain points aligned to specific job steps, and concrete quantified thresholds for success.
| Checked | Without skill | With skill |
|---|---|---|
| Uses Job Step, Goal, and Desired Outcome as table column headers. | Missed | Passed |
| Expresses success metrics using quantified numeric thresholds. | Passed | Passed |
| Includes a one-sentence Who description of product relationship. | Missed | Passed |
The instructions your model reads when the skill loads.
Use during Phase 1 (GATHER) when the user lacks clear personas or the "Who" section needs rigorous definition. Provides structured alternative to ad-hoc persona descriptions.
For each user type, build a complete persona:
## Persona: {Name}
**Who**: {Role description -- one sentence capturing relationship to product}
**Demographics**:
- {Characteristic 1: e.g., technical proficiency level}
- {Characteristic 2: e.g., frequency of interaction}
- {Characteristic 3: e.g., environment/context of use}
- {Characteristic 4: e.g., primary motivation}
**Jobs-to-be-Done**: (see Job Step Table below)
**Pain Points**:
- {Pain 1} -- maps to Job Step: {step name}
- {Pain 2} -- maps to Job Step: {step name}
**Success Metrics**:
- {Quantified outcome 1: e.g., "Task completed in < 2 minutes"}
- {Quantified outcome 2: e.g., "Zero manual configuration steps"}
Each persona has job steps describing what they accomplish. Steps follow ODI format.
| Job Step | Goal | Desired Outcome |
|---|---|---|
| {Verb} | {What the user wants to achieve} | Minimize {metric} of {undesirable state} |
test cases passed, vs 13 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.