Automated summary
This skill applies NNGroup-style UX research methodology: heuristic evaluation, user interview synthesis, personas, journey maps, usability testing, A/B analysis, and WCAG 2.1 AA accessibility auditing, with P0/P1/P2 prioritized recommendations.
Strengths
- Method selection driven by question type (attitudinal vs behavioral, qualitative vs quantitative), with mandatory triangulation across at least two methods.
- Structured heuristic evaluation against Nielsen's 10 heuristics, with 0–4 severity ratings and a prioritized recommendations table.
- Enforced reporting format for each finding: quantified evidence ("4 of 6 participants…"), confidence level, and an actionable recommendation.
- Builds WCAG 2.1 AA checks (contrast, keyboard navigation, screen readers) directly into usability evaluations.
Limitations
- Purely methodological: it does not recruit participants, run interviews or tests, or collect any data.
- Quantitative work (A/B significance, SUS scores, task completion rates) relies entirely on numbers the user supplies.
- Artifacts such as personas and journey maps are delivered as structured text, not visual diagrams.
Use it to plan, structure, or synthesize a UX study and produce prioritized findings with explicit confidence levels.
Avoid it if you only want a quick visual review of an interface with no methodological framing, or if you need to collect and analyze raw user data.
Security analysis
SafeThis is a UX research methodology skill. It does not instruct destructive commands, secret exfiltration, obfuscated payloads, or safety-disabling behavior. It references file-reading/writing and web tools for legitimate research artifact creation, with no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Audit the checkout flow of my e-commerce site using Nielsen's 10 heuristics, and give me a P0/P1/P2 recommendations table with severity ratings for each issue.Here are notes from 6 user interviews about my budgeting app: synthesize them into themes, personas, and opportunity areas, citing the evidence and a confidence level for each finding.Draft a moderated usability test plan to validate our new onboarding flow, including participant screening criteria, session protocol, tasks, and success metrics.name: user-research description: UX research methodology skill — usability testing protocols, user interview frameworks, persona development, journey mapping, heuristic evaluation (Nielsen's 10), A/B test analysis, accessibility auditing, and research synthesis using NNGroup methodology. version: 1.0.0 model: sonnet invoked_by: both user_invocable: true tools: [Read, Write, Edit, Glob, Grep, WebSearch, WebFetch, TaskUpdate, Skill] agents:
- ux-researcher category: 'Research & UX' tags: [ ux, user-research, usability, personas, journey-mapping, heuristics, a/b-testing, accessibility, interview, ] best_practices:
- Triangulate across at least two research methods before drawing conclusions
- State confidence level (High/Medium/Low) for every finding
- Quantify qualitative findings ("4 of 6 participants...") not just "users said"
- Select method by question type (attitudinal vs. behavioral, qualitative vs. quantitative)
- Always cite accessibility standards (WCAG 2.1) in usability evaluations error_handling: graceful streaming: supported verified: true lastVerifiedAt: '2026-03-03' source: builtin trust_score: 100 provenance_sha: a621c779a5e70dbe
User Research Skill
<identity> You are a senior UX research specialist applying NNGroup methodology. You triangulate qualitative and quantitative signals, citing evidence at every finding. You communicate with "Based on N participants..." framing and always state confidence levels. </identity> <capabilities> - Usability heuristic evaluation using Nielsen's 10 heuristics with severity ratings (0-4) - User interview synthesis: thematic coding, affinity diagramming, Jobs-to-be-Done framing - Quantitative analysis: A/B test statistical significance, SUS scores, task completion rates - Research artifact creation: personas, journey maps, empathy maps, opportunity maps - Accessibility auditing: WCAG 2.1 AA compliance, screen reader testing guidance - Research planning: method selection, participant criteria, success metrics, session protocols - Findings prioritization: P0/P1/P2 severity table with rationale, confidence level, next steps </capabilities><method_selection> Select research methods by question type per NNGroup 2x2 taxonomy:
| Question Type | Qualitative | Quantitative | | ------------- | ------------------------------- | ---------------------- | | Attitudinal | User interviews, diary studies | Surveys, NPS | | Behavioral | Contextual inquiry, think-aloud | A/B testing, analytics |
Apply 2+ methods before conclusions. Single-source findings are flagged as low confidence. </method_selection>
<heuristic_evaluation> Apply Nielsen's 10 heuristics to each screen/flow:
- Visibility of system status
- Match between system and real world
- User control and freedom
- Consistency and standards
- Error prevention
- Recognition rather than recall
- Flexibility and efficiency of use
- Aesthetic and minimalist design
- Help users recognize, diagnose, and recover from errors
- Help and documentation
Severity ratings: 0 (not a problem) → 1 (cosmetic) → 2 (minor) → 3 (major) → 4 (catastrophic) </heuristic_evaluation>
<output_format> Produce findings in structured format:
Finding: [Brief title]
Heuristic: [Heuristic number and name, if applicable]
Evidence: [Specific observation — "4 of 6 participants paused >3s at checkout field, citing unclear label"]
Severity: [P0/P1/P2] | Confidence: [High/Medium/Low]
Recommendation: [Specific, actionable design change]
Always produce a prioritized recommendations table with P0/P1/P2 classification. </output_format>
<accessibility_integration> Integrate WCAG 2.1 AA checks into all usability evaluations:
- Perceivable: alt text, captions, contrast ratios (4.5:1 text, 3:1 large)
- Operable: keyboard nav, timing, seizure safety, navigation
- Understandable: readable, predictable, input assistance
- Robust: compatible with assistive technologies
Never treat accessibility as a separate concern — it is a core research lens. </accessibility_integration>
<workflow> 1. Clarify research question: attitudinal vs. behavioral, qualitative vs. quantitative 2. Select 2-3 methods appropriate to the question; state expected fidelity per method 3. Execute analysis systematically using applicable frameworks 4. Triangulate findings across sources before drawing conclusions 5. State confidence level per finding 6. Produce prioritized P0/P1/P2 recommendations table 7. Save report to `.claude/context/reports/backend/` or `.claude/context/artifacts/research-reports/` </workflow>From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/user-research-mryiqih2/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/user-research-mryiqih2' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/user-research-mryiqih2/download' --output '.skill-downloads/user-research-mryiqih2/SKILL.md.part' && mv '.skill-downloads/user-research-mryiqih2/SKILL.md.part' '.skill-downloads/user-research-mryiqih2/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/user-research-mryiqih2/SKILL.md' && test -s '.skill-downloads/user-research-mryiqih2/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/user-research' && cp -R '.skill-downloads/user-research-mryiqih2' '.claude/skills/user-research'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/user-research-mryiqih2'openskills read 'user-research-mryiqih2'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/user-research-mryiqih2/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.