affinity-diagram

affinity-diagram is a skill for Claude Code from Owl-Listener/designer-skills. It costs 50 tokens per session (415 once invoked), scanned A, original, MIT.

A qualitative research method for grouping many observations, interview notes, or survey responses into themes. It helps turn separate comments into shared patterns and conclusions.

In plain words
What is it for?
Extract observations, cluster related points, name and organize themes, write insight statements, identify patterns, and prioritize findings.
Why use it?
It reduces the effort of finding repeated ideas across several research sessions or sources. It also connects each theme to an insight that can guide design decisions.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the design-research plugin — 12 skills, 4 commands shipped together

Good fit Extract observations, cluster related points, name and organize themes, write insight statements, identify patterns, and prioritize findings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/designer-skills/affinity-diagram
About the project

Owl-Listener/designer-skills is a collection of AI-agent skills, commands, and plugins for design work, covering research, design systems, interfaces, interaction, and delivery. Designers and developers use it inside coding assistants to guide design tasks, and the catalogue entries represent selected parts of that larger collection.

Owl-Listener/designer-skills · 2,609 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Owl-Listener/designer-skills --skill affinity-diagram
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designer-skills

Made for: Claude Code.

Or install design-research, the plugin that ships this one along with the rest of its 12 skills, 4 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for affinity-diagram

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/designer-skills/affinity-diagram/github.svg)](https://agentmods.dev/skills/owl-listener/designer-skills/affinity-diagram)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/designer-skills/affinity-diagram"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/affinity-diagram/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for affinity-diagram

Your own site · 80×15
<a href="https://agentmods.dev/skills/owl-listener/designer-skills/affinity-diagram"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/affinity-diagram.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 415 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 16 Mar 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00415
Opus 5 $0.00025 $0.00208
Sonnet 5 $0.00010 $0.00083
Haiku 4.5 $0.00005 $0.00042

Measured 11d ago against content hash 607026b92553, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

affinity-diagram scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

design-research/skills/affinity-diagram/SKILL.md · 35 lines

What it actually says

Affinity Diagram

Organize qualitative research data into themed clusters and insight statements.

Context

You are a UX researcher synthesizing qualitative data for $ARGUMENTS. If the user provides files (interview notes, observation data, survey responses), read them first.

Instructions

  1. Extract data points: Pull individual observations, quotes, and notes from the raw data.
  2. Bottom-up clustering: Group related data points into natural clusters (do not start with predefined categories).
  3. Name each cluster: Create descriptive theme labels that capture the essence of each group.
  4. Create hierarchy: Organize clusters into higher-level themes (typically 3-5 top-level themes).
  5. Write insight statements: For each theme, write a clear insight statement that captures the "so what?"
  6. Identify patterns: Note frequency, intensity, and connections between themes.
  7. Prioritize: Rank insights by impact on design decisions.
  8. Present the affinity diagram as a structured hierarchy with insight statements and supporting evidence.

Cross-Interview Sampling Principle

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.

  • Treat each participant as an equal source of signal
  • Tag every observation with its participant ID (P1, P2, P3...) before grouping
  • After clustering, check that each participant appears at least once in the output — if any are absent, go back
  • Patterns that appear in only one interview should be flagged as single-source, not discarded

This prevents the common LLM failure mode of building themes from the first one or two transcripts and fitting the rest retroactively.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 35 lines · 50 tokens per session scan A 607026b92553

Subscribe to this mod's changes

affinity-diagram is a skill published in the GitHub repository Owl-Listener/designer-skills (2,609 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 415 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

ui-review

Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.

LiHongwei-cn/lihongwei-cn · 26 tokens

design-system

Use this skill BEFORE writing or restyling ANY user-facing interface in WrongStack. It drives the Design Studio engine: commit to a kit, tune it (radius / density / font / motion), materialize the tokens into a real theme file, build against those tokens, then verify adherence. Trigger it whenever the user asks to…

WrongStack/WrongStack · 248 tokens

accessibility-a11y

Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.

BlackBeltTechnology/pi-agent-dashboard · 44 tokens

tailwind-shadcn

Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.

BlackBeltTechnology/pi-agent-dashboard · 50 tokens

anti-slop-frontend

A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…

BlackBeltTechnology/pi-agent-dashboard · 147 tokens

frontend-mockup-loop-dashboard

Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when designing/redesigning any pi-agent-dashboard client surface. Triggers: "design a dashboard screen", "mockup a dashboard…

BlackBeltTechnology/pi-agent-dashboard · 83 tokens