Install any skill in seconds. Free to start, no credit card required.
Get Started Free →owl-listener/affinity-diagram
Organize qualitative research data into an affinity diagram with themes, clusters, and insight statements.
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
1 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I have raw interview notes from 3 user sessions about our mobile banking app. I usually organize feedback into predefined categories like 'Usability', 'Performance', and 'Visual Design'. Here are the notes: P1: 'The transfer button is hidden under three menus.' P2: 'I spent five minutes looking for my monthly statement.' P3: 'I can never find where my account details live.' Synthesize these notes into themed clusters.
| Checked | Without skill | With skill |
|---|---|---|
| Groups notes into a bottom-up theme based on navigation or feature discoverability rather than using the predefined taxonomy categories | Missed | Passed |
| Includes a descriptive theme label reflecting user difficulty finding core account features | Passed | Passed |
The instructions your model reads when the skill loads.
Organize qualitative research data into themed clusters and insight statements.
You are a UX researcher synthesizing qualitative data for $ARGUMENTS. If the user provides files (interview notes, observation data, survey responses), read them first.
Index evenly across all participants. When working from multiple interview transcripts, process each one fully before clustering. Do not over-represent early transcripts or the most recent input.
This prevents the common LLM failure mode of building themes from the first one or two transcripts and fitting the rest retroactively.
test cases passed, vs 21 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.