skills/research-interviewer/SKILL.md
Three-phase research interview system based on Anthropic Interviewer methodology. Conducts structured qualitative interviews with explicit planning, adaptive interviewing, and synthesis. Supports single interviews and multi-interview series with thematic analysis. Use when you need Claude to interview you (or guide an interview with someone else) to extract insights, stories, and knowledge on any topic.
npx skillsauth add szoloth/skills research-interviewerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Three-phase interview system based on Anthropic Interviewer methodology and academic research on AI-conducted qualitative interviews.
The three phases:
Works across contexts: expert/SME interviews, stakeholder research, exploratory discovery, and editorial content gathering. Supports both single interviews and multi-interview series with cumulative thematic analysis.
Say things like:
When a user requests an interview, ALWAYS start with planning.
Before generating questions, ask the user:
Generate an interview plan with:
Opening script (consent, framing, duration):
"Thank you for taking time to speak with me. We're exploring [topic] to understand [goal]. There are no right or wrong answers – I'm genuinely interested in your unique experiences. This should take about 10 minutes."
Anchor questions (5-9, following Anthropic's structure):
| # | Type | Template | |---|------|----------| | 1 | Integration/context | "Could you tell me about how [X] fits into your typical [context]?" | | 2 | Specific instance | "Can you walk me through what a specific instance of [X] looks like?" | | 3 | Preferences/choices | "Are there certain [tasks] you prefer to handle yourself? What makes those different?" | | 4 | Interaction patterns | "When you [do X], do you tend to [approach A] or [approach B]?" | | 5 | Environmental influences | "How have [colleagues/environment/context] influenced the way you [do X]?" | | 6 | Critical incident | "Can you share a time when [X] made you feel particularly satisfied or frustrated?" | | 7 | Skill/capability | "How do you think about [developing/maintaining] your [skills] in this area?" | | 8 | Future vision | "Looking ahead, how do you envision [X] evolving?" | | 9 | Open closure | "Is there anything else about [topic] that you think would be valuable for me to know?" |
Follow-up branches for each anchor (anticipated probes based on likely responses)
Time allocation (~10 min default, adjustable)
Success criteria (what would make this interview successful?)
Present the rubric to the user and get approval before starting:
"Thank you for taking time to speak with me today. We're exploring [topic] to understand [research goal]. During our conversation, I'll ask questions about [focus areas]. There are no right or wrong answers – I'm genuinely interested in your unique experiences. This should take about 10 minutes."
Based on AI Conversational Interviewing research:
| Behavior | Description | |----------|-------------| | One question at a time | Never stack multiple questions. Wait for response before asking next. | | Active listening | Briefly restate key points in their words before moving on. Shows you heard them. | | Casual, conversational, neutral, professional tone | Not interrogation. Not therapy. Professional curiosity. | | Connect to previous answers | "Earlier you mentioned X. How does that relate to...?" | | Move forward gracefully | If they can't answer, don't pressure. Acknowledge and continue. |
When to probe:
Timing is critical (from AI Follow-up Questions research):
How to probe:
| Strategy | Description | Example | |----------|-------------|---------| | Connector/Springboard | Link previous response to next step | "That connects to something I wanted to ask..." | | Push Deeper | Move from broad to specific | "Can you give me a specific example of that?" | | Request Examples | Concrete over abstract | "What did that look like in practice?" | | Clarify Emotion | Understand the feeling | "What made that particularly [frustrating/satisfying]?" |
Follow-up phrasing:
Avoid these (from research showing 88% of interview violations came from AI):
| Failure Mode | Description | Instead | |--------------|-------------|---------| | Probing too early | Asking follow-ups before rapport established | Wait until mid-interview | | Over-probing | Too many follow-ups, feels like interrogation | 1-2 follow-ups max per anchor | | Poor timing | Interrupting flow with tangent questions | Let natural pauses emerge | | Suggesting answers | Leading questions with implied answers | Keep questions open and neutral | | Stacking questions | Multiple questions in one turn | One question per turn only |
If interviewee is rambling: Gently redirect with specific question. "That's interesting—can you give me a specific example of when that happened?"
If answers are too short: Use silence first (let them think), then: "Tell me more about that" or "What made you think that?"
If hitting surface-level answers: Push for specifics: "What exactly did they say?" or "Walk me through that moment."
If interviewee seems uncomfortable: Acknowledge it, offer to skip, or reframe more gently. "We can come back to that if you'd like."
If energy/passion detected: Follow it. "You seem really energized about this—tell me more."
For analysis, invoke the interview-synthesizer subagent via Task tool.
This separates the heavy synthesis work from the main conversation and enables parallel analysis of multiple interviews.
Task tool invocation:
- subagent_type: "interview-synthesizer"
- prompt: Include the interview transcript and research question
- For series: Launch multiple synthesizers in parallel, one per interview
The synthesizer agent will generate:
1. Key Insights (3-5) Each insight includes:
2. Theme Tags Emergent topics that appeared (for tracking across interviews)
3. Research Question Answers How this interview informed the original research question
4. Emotional Intensity Map What topics generated the most energy (positive or negative)?
5. Follow-up Questions What would you ask in a follow-up interview?
For interview series, track cumulatively:
| Analysis | Description | |----------|-------------| | Theme Prevalence | "X of Y participants mentioned this" | | Pattern Clusters | Group similar responses together | | Theme Hierarchy | Broad themes → specific sub-themes | | Outliers | Unique perspectives worth noting | | Evolution | How insights develop across interviews | | Contradictions | Where participants disagree |
Interview Plan (pre-interview):
## Research Question
[What we're trying to learn]
## Anchor Questions
1. [Question] → Follow-up branches: [a, b, c]
2. [Question] → Follow-up branches: [a, b, c]
...
## Time Allocation
[X] minutes
## Success Criteria
[What would make this interview successful]
Session Notes (post-interview):
## Key Insights
1. [Insight] - "[Verbatim quote]"
2. [Insight] - "[Verbatim quote]"
...
## Theme Tags
[tag1] [tag2] [tag3]
## Research Question Progress
[How this interview informed the question]
## Emotional Highlights
[Topics with energy]
## Follow-up Questions
[For next interview]
Series Synthesis (multi-interview):
## Cross-Interview Themes
| Theme | Prevalence | Key Quotes |
|-------|------------|------------|
| [Theme] | X of Y | "[quote1]", "[quote2]" |
## Pattern Clusters
[Grouped findings]
## Outliers
[Unique perspectives]
## Recommendations/Implications
[What to do with these findings]
Goal: Extract specialized knowledge and hard-won insights.
Mode-specific anchor questions:
Focus on: Domain knowledge, mental models, decision heuristics, non-obvious insights, contrarian takes
Goal: Understand organizational dynamics and priorities.
Mode-specific anchor questions:
Focus on: Organizational dynamics, priorities, hidden constraints, sacred cows, what's unsaid
Goal: Learn about an unfamiliar domain with open curiosity.
Mode-specific anchor questions:
Focus on: Landscape understanding, key players, terminology, surprising connections, foundational concepts
Goal: Gather compelling material for articles and content.
Mode-specific anchor questions:
Focus on: Quotable insights, vivid stories, contrarian perspectives, headline moments, voice and personality
Interview is going well when:
Interview needs adjustment when:
This skill incorporates methodology from:
content-media
Fetch transcripts from YouTube videos for summarization and analysis.
documentation
This skill should be used when reviewing or editing written drafts to ensure they match Sam's personal style guide. It prioritizes voice preservation and anti-beige detection while catching structural gaps. Triggers on requests to review, edit, or improve written content.
tools
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
development
Web search and content extraction using Brave Search. Use when researching topics, finding documentation, extracting article content, or gathering information from the web. No browser required - works headlessly.