Agent Skills

affinity-diagram

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

Install

npx skills add https://github.com/owl-listener/designer-skills --skill affinity-diagram
SKILL.md

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.

Related skills

researchmattpocock575KInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.paper-context-resolverlllllllama451KRigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing Renv-and-assets-bootstraplllllllama450KRigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.ai-research-explorelllllllama311KRigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow c

Search skills and MCP servers

Fuzzy search across 23,137 skills and servers