Individual skill

expert-interview

Designs an expert-interview package - sourcing criteria for the right experts, a funneled discussion guide with timing, open-then-probe question design, laddering, and a neutral probe kit - that extracts honest insight without leading the witness. Use when someone asks "help me write questions for an expert call", "build a discussion guide", "prep me for this expert network interview", or is planning customer-development or domain-expert conversations. Do NOT use for designing a full data-collection study with sampling and hypotheses - use primary-research instead; for synthesizing findings after the interviews are done, use interview-synthesis instead; for desk research that involves no live conversation, use deep-research instead.

skills/expert-interview/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 6, 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): 24
Repository last updated: Oct 13, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude Repository topic
claude-skills Repository topic
skill-me Repository topic
design Derived category
data Derived category
research Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 7,521 bytes

Read excerpt


# Expert Interview

An hour with the right expert can replace weeks of desk research - or produce nothing but confirmation of what the interviewer already believed. The costly failure this skill prevents is the leading interview: questions that carry the hypothesis inside them, so the expert politely agrees and the team ships on evidence it manufactured itself. A good guide is a structure, not a script.

## Inputs to collect

1. **Learning objectives**: what decision the interviews inform, and the 3-5 things that must be learned. Separate "must learn" from "nice to know" so sections can be cut under time pressure.
2. **The hypothesis being tested**, if any - written down so it can be deliberately kept out of the questions.
3. **Interview length** (default 45-60 minutes) and format (call, in person).
4. **How many experts** and what mix of vantage points (practitioner, buyer, former insider, adjacent-market operator).
5. **Recording and consent constraints**, and any compliance rules (expert networks prohibit asking for confidential or MNPI material - respect this in question design).

## Operating procedure