skillZs
LIVE SKILL TAGS
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
REAL INSTALL DATA
← back to all skills
chris-jimdo/skills-test1 installs

research-analysis

Guide for analyzing qualitative user research data at Jimdo — covering data preparation, GDPR anonymization, coding and tagging, and synthesizing findings into insights. Use this skill whenever someone wants to analyze research data, make sense of interview notes or test results, tag or code qualitative data, identify themes across participants, or turn observations into insights. Also use when someone asks how to use AI tools for analysis or how to structure their analysis work.

How do I install this agent skill?

npx skills add https://github.com/chris-jimdo/skills-test --skill research-analysis
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides a comprehensive framework and templates for qualitative user research analysis. It is entirely informational, contains no executable code or automated tools, and prioritizes data security through mandatory anonymization protocols.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

⚠️ Always ask for explicit confirmation before publishing or posting anything to Confluence, Slack, or any other external tool — even if the person has already approved the content.

Research Analysis

This skill covers how to go from raw research data to meaningful insights — ready to be reported and shared.


Step 1: Data preparation

Before you start analyzing, get your data in order.

Organize and clean your data Gather all session notes, recordings, and transcripts in one place. Remove irrelevant content and make sure the data is readable and searchable.

Add a research context statement At the top of your analysis document, briefly describe:

  • What you were trying to learn (research questions)
  • What method you used
  • Who you spoke to (number and type of participants, without PII)
  • When the research took place

Create a mini-glossary (if needed) If your research touches on domain-specific terms or internal product names, add a short glossary so anyone reading the analysis understands the context.


GDPR — mandatory before using AI tools

Always anonymize your data before using any AI tool for analysis.

This is not optional. Replace all personally identifiable information before pasting anything into an AI tool:

  • Use participant codes: P1, P2, P3, etc. — never real names or identifying details
  • Remove company names, locations, job titles, or anything that could identify a person
  • This applies to direct quotes, notes, and transcripts

If you're unsure whether something is PII, remove it.


Step 2: Coding and tagging

Participant-level analysis

For each participant, create a summary of what you heard. Capture:

  • Key themes or topics they brought up
  • Direct quotes (labeled with participant code, e.g. P1)
  • Observations about behavior, emotions, or decision-making
  • Anything surprising or contradicting your expectations

Theme identification across participants

Once you have participant-level notes, look across them for patterns:

  • What did multiple participants say or experience?
  • Where do their experiences differ, and why might that be?
  • What topics came up most frequently?
  • What are the strongest, most consistent signals?

Group your notes by theme, not by participant. This is where cross-participant patterns emerge.


Step 3: From findings to insights

There's a critical difference between a finding and an insight:

FindingInsight
What you observed or heardWhat it means
"5 out of 7 participants couldn't find the export button""The export function is invisible to users because it's buried in a secondary menu, which breaks a key workflow"
DescriptiveInterpretive

Synthesize findings into insights Don't just report what happened — explain what it means for the product or user experience.

Identify opportunities Based on your insights, what could be improved, explored, or addressed? Frame these as opportunities, not solutions.

Keep layers visible in your documentation:

  • What participants said or did (direct data)
  • Your interpretation of what it means (analysis)
  • Recommendations or next steps (your professional judgment)

Using AI tools for analysis (CRAFTe framework)

When using AI to help with analysis, structure your prompt using the CRAFTe framework:

ElementWhat it means
C — ContextWhat is the research about? What are you trying to learn?
R — RoleWhat role should the AI take? (e.g., "act as a UX researcher")
A — ActionWhat specifically do you want the AI to do?
F — FormatHow should the output be structured?
T — TemplateIs there a specific template or structure to follow?
e — ExamplesCan you provide an example of the expected output?

This framework helps you get more consistent, useful output — especially when working with large amounts of qualitative data.

Always review AI-generated analysis critically. AI can help identify patterns and draft summaries, but the interpretation and judgment are yours.

Read references/example-ai-analysis-prompt.md for a real example of a CRAFTe-structured prompt used at Jimdo.


Reference examples

When helping someone with analysis, read the relevant reference file and use it as a format template for your output:

What you're helping withReference file
Writing a participant summaryreferences/example-participant-summary.md
Doing cross-interview thematic analysisreferences/example-cross-interview-analysis.md
Writing recommendationsreferences/example-recommendations.md
Building an AI analysis promptreferences/example-ai-analysis-prompt.md

These are real Jimdo examples — follow their structure, level of detail, and way of presenting quotes and themes closely.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/chris-jimdo/skills-test/research-analysis">View research-analysis on skillZs</a>