interview-guide
Skill1 starsChanged 36 days agoMITView on GitHub
Write a semi structured interview guide with behaviour based questions and follow up probes that do not lead the participant. Use when someone is preparing user interviews, customer conversations, discovery calls or switch interviews, or wants their questions reviewed for bias.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- ql-link/drawoffer-skillstheir own version, first seen Nov 1, 2026
- Pearl1531/Archetype-talktheir own version, first seen Oct 13, 2026
- prestarius/jet-skills-stacktheir own version, first seen Oct 11, 2026
- denchik2245/Skillstheir own version, first seen Oct 9, 2026
- talgacapri/pm-ostheir own version, first seen May 23, 2026
- nbirkner/digital-braintheir own version, first seen Apr 12, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Pearl1531/Archetype-talk★ 2same name
- denchik2245/Skills★ 1same name
- prestarius/jet-skills-stack★ 1same name
- nbirkner/digital-brain★ 0same name
- ql-link/drawoffer-skills★ 0same name
- talgacapri/pm-os★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- accessibility-researchSkill
- ai-browser-walkthroughSkill
- analytics-insightsSkill
- card-sort-tree-testSkill
- competitive-analysisSkill
- diary-studySkill
- jobs-to-be-doneSkill
- journey-mapSkill
- research-planSkill
- research-readoutSkill
- screener-surveySkill
- stakeholder-interviewsSkill
- survey-designSkill
- synthetic-usersSkill
- usability-test-analysisSkill
- usability-test-planSkill
- user-personasSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
No leading ("Wouldn't it be easier if..."), no yes or no, no hypotheticals ("Would you use...").
- Distinctive: line 22
After each core question, a probe: "What happened next?", "Why was that?", "How did you decide?", "Can you show me?"
- Distinctive: line 30
Don't pitch. Don't fill silences.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interview guide
Good interviews ask about the past, not the future. People are bad at predicting what they'll do and good at telling you what they did.
Structure for a 30 to 45 minute session
- Intro (3 min). Who you are, the purpose in plain words, consent to record, "there are no wrong answers, we're testing ideas, not you".
- Warm up (5 min). Their context and role, not your product.
- The core (20 to 30 min). Walk through the last time they actually did the task: "Tell me about the last time you..." then let the story run. Questions follow the order things happened.
- Workarounds and costs (5 min). What they tried instead, what it cost in time, money or stress.
- Close (3 min). "What should I have asked?", thanks, next steps for the incentive.
Rules for every question
- Open ended, about real past behaviour, one idea at a time.
- No leading ("Wouldn't it be easier if..."), no yes or no, no hypotheticals ("Would you use...").
- After each core question, a probe: "What happened next?", "Why was that?", "How did you decide?", "Can you show me?"
Output
The guide with timings, each question followed by its probe, and the three questions to keep if time runs short. Then a short list of what to listen for, tied to the research questions.
Don't
- Don't pitch. Don't fill silences. Don't correct the participant.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

