Individual skill
research-interview-synthesis
Synthesize multiple user interviews into evidence-backed themes, insights, limitations, and next research actions. Use for: interview synthesis, customer research findings, usability study themes, discovery interview analysis.
.grok/skills/research-interview-synthesis/SKILL.md
Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 14
- Repository last updated
- Oct 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- grok Repository topic
- prompt-engineering Repository topic
- workflow-automation Repository topic
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Research Interview Synthesis
## Purpose
Turn multiple user-research conversations into a traceable synthesis that distinguishes what participants said from the team’s interpretation and recommendations.
## Workflow
1. Confirm the research question, participant count, recruitment context, and available materials.
2. Remove or replace direct identifiers unless they are essential and authorized for the requested audience.
3. Code observations by topic while preserving participant IDs and source references.
4. Identify recurring patterns, notable exceptions, and areas of disagreement; do not treat frequency as proof of importance.
5. Draft insights that state the evidence, interpretation, confidence, and limitations separately.
6. Propose research or product actions that tie back to specific findings.