User Research Cookiy
cookiy-ai/user-research-skill
End-to-end user research assistant — qualitative and quantitative.
Run high-signal customer discovery interviews using a scripted question hierarchy, behavior-over-opinion probes, and rapport techniques drawn from Portigal, Torres, Fitzpatrick (Mom Test), and Lewis…
Install Customer Interview Script
$ npx skills add borghei/Claude-Skills --skill customer-interview-script -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills customer-interview-script --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/discovery/customer-interview-script .claude/skills/customer-interview-script && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "customer-interview-script" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/customer-interview-script into .claude/skills/customer-interview-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-interview-script", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/customer-interview-scriptType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill customer-interview-script -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills customer-interview-script --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/project-management/discovery/customer-interview-script .agents/skills/customer-interview-script && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "customer-interview-script" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/customer-interview-script into .agents/skills/customer-interview-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-interview-script", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill customer-interview-script -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills customer-interview-script --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/project-management/discovery/customer-interview-script .cursor/skills/customer-interview-script && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "customer-interview-script" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/customer-interview-script into .cursor/skills/customer-interview-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-interview-script", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path project-management/discovery/customer-interview-script--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill customer-interview-script -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills customer-interview-script --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/project-management/discovery/customer-interview-script .gemini/skills/customer-interview-script && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "customer-interview-script" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/customer-interview-script into .gemini/skills/customer-interview-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-interview-script", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills customer-interview-scriptInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill customer-interview-script -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/project-management/discovery/customer-interview-script .github/skills/customer-interview-script && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "customer-interview-script" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/customer-interview-script into .github/skills/customer-interview-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-interview-script", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill customer-interview-script -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills customer-interview-script --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/project-management/discovery/customer-interview-script .opencode/skills/customer-interview-script && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "customer-interview-script" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/discovery/customer-interview-script into .opencode/skills/customer-interview-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-interview-script", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
customer-interview-script- GitHub stars
- 874
- Token cost
- ~1.7k tokens
- SKILL.md length
- 711 words
- Files
- 7 (incl. references, assets)
- Skills in repo
- 364
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run high-signal customer discovery interviews using a scripted question hierarchy, behavior-over-opinion probes, and rapport techniques drawn from Portigal, Torres, Fitzpatrick (Mom Test), and Lewis…
- Works in 3 steps: Pull top assumptions from… → Customize… → Run the 5-phase script (rapport first,…
- Tasks that involve User research
- SKILL.md covers Overview, Core Capabilities, When to Use and Clarify First, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Customer Interview Script is an agent skill from borghei/Claude-Skills. Run high-signal customer discovery interviews using a scripted question hierarchy, behavior-over-opinion probes, and rapport techniques drawn from Portigal, Torres, Fitzpatrick (Mom Test), and Lewis Lin.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files and assets (for example `assets/interview_script_template.md`, `assets/question_bank.md` and `examples/churn-investigation-filled-script.md`).
It sits in Product & Project Management, covering User research. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Tasks that involve User research
Example prompts
- “/customer-interview-script”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Pull top assumptions from discovery/identify-assumptions/; write 2-3 must-answer questions and pick the interview type.
- Customize assets/interview_script_template.md and pull type-specific prompts from assets/question_bank.md.
- Run the 5-phase script (rapport first, stories in the middle, contradictions at the end); debrief within 30 minutes; hand the transcript…
What it can do on your machine
Read from SKILL.md and the folder at commit c9a1487. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Customer Interview Script loads about 1.7k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 711 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 711 words, ~1,671 tokens.
Download SKILL.mdSave it as
.claude/skills/customer-interview-script/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- customer-interview-script
- description
- Run high-signal customer discovery interviews using a scripted question hierarchy, behavior-over-opinion probes, and rapport techniques drawn from Portigal, Torres, Fitzpatrick (Mom Test), and Lewis Lin.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.1
- metadata.author
- borghei
- metadata.category
- project-management
- metadata.domain
- pm-discovery
- metadata.updated
- 2026-06-15
- metadata.tech-stack
- customer-interviews, discovery, jobs-to-be-done, mom-test
Customer Interview Script Expert
Overview
Running a customer interview is harder than it looks. The difference between a 60-minute conversation that produces three actionable insights and one that produces zero is almost entirely method: what you ask, when you ask it, and what you do not ask. This skill is the live-interview companion to discovery/interview-synthesis/ (post-interview analysis) and discovery/identify-assumptions/ (which produces the questions you go in to test).
The script structure draws from four canonical sources: Steve Portigal's Interviewing Users (rapport, listening, "tell me about the last time"), Teresa Torres' Continuous Discovery Habits (story-based probing, weekly cadence), Rob Fitzpatrick's The Mom Test (avoiding compliments, opinions, and futures), and Lewis Lin's behavioral interviewing patterns (concrete-recent-relevant). The goal is to leave each interview with at least one story, one contradiction, and one surprise.
Core Capabilities
- 5-phase script -- opening/consent, context, story collection (the meat), probing/synthesis, closing -- timed for 45/60/90-minute slots.
- Story-based probing -- the story funnel and 5-Whys turn opinions into concrete-recent-relevant evidence.
- Mom Test discipline -- bad-question to good-question conversions that strip out compliments, fluff, and feature pitches.
- Question banks by type -- problem discovery, solution validation, journey mapping, churn/win-loss.
- Interview craft -- rapport rules, silence handling, pacing, pair-interviewing roles, recording/consent/storage.
When to Use
- Problem discovery -- test whether a customer pain is real, who has it, and how acute it is.
- Solution validation -- get feedback on a wireframe/prototype grounded in past behavior, not hypotheticals.
- Journey research -- understand the end-to-end flow of how a customer does a job today (tools, workarounds, handoffs).
- Churn or win/loss -- understand why customers left, stayed, or chose a competitor.
- Continuous discovery cadence -- weekly customer touchpoints to keep the team grounded in evidence.
Clarify First
Before building the interview script, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Interview type — problem discovery / solution validation / journey / churn-win-loss (selects the question bank and phase emphasis)
- Must-answer questions — the 2-3 assumptions you go in to test (drives the custom story-collection prompts)
- Time slot — 45 / 60 / 90 minutes (sets the per-phase timing)
- Participant recency — how recently they did the job (story-based probing degrades past ~90 days, which weakens the script's core)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Quick Start
- Pull top assumptions from
discovery/identify-assumptions/; write 2-3 must-answer questions and pick the interview type. - Customize
assets/interview_script_template.mdand pull type-specific prompts fromassets/question_bank.md. - Run the 5-phase script (rapport first, stories in the middle, contradictions at the end); debrief within 30 minutes; hand the transcript to
discovery/interview-synthesis/.
See references/interview-execution-playbook.md for the full method, scripts, question banks, pacing, and troubleshooting.
Show full SKILL.md (271 more words)Show less
References
references/interview-execution-playbook.md-- read this before running an interview: the four-source frameworks, the verbatim 5-phase script, question banks by type, what-not-to-ask table, pacing, pair-interviewing roles, recording/consent, silence handling, workflow, troubleshooting, and success criteria.references/interviewing-methodology-guide.md-- read this for the deep method with worked examples (Portigal, Torres, Fitzpatrick, Lin).references/red-flags.md-- read this when auditing a transcript or technique for biasing anti-patterns before trusting the findings.assets/interview_script_template.md-- ready-to-customize 5-phase interview script.assets/question_bank.md-- question bank organized by interview type (problem / solution / journey / churn).
Scope & Limitations
In scope: live discovery interview script structure and pacing; question banks (problem / solution / journey / churn); rapport, listening, and silence techniques; recording consent and retention policy; pair-interviewing role definitions.
Out of scope: interview synthesis and theme clustering (discovery/interview-synthesis/); assumption mapping before interviews (discovery/identify-assumptions/); survey design and quantitative research; usability testing protocols (task-based, not story-based); recruiting operations (panel sourcing, screening, incentives).
Caveats: this skill produces interview technique, not research operations. Story-based interviewing is bounded by participant memory -- events older than 90 days are reconstructions. B2B enterprise interviews often need procurement-style approval; build 2-4 weeks into recruiting. Continuous discovery assumes weekly touchpoints; one-off rounds produce shallower evidence -- weight findings accordingly.
Integration Points
| Integration | Direction | What Flows |
|---|---|---|
discovery/identify-assumptions/ | Receives from | Top assumptions become the must-answer questions for each interview |
discovery/interview-synthesis/ | Feeds into | Transcripts and debrief notes are the input for theme clustering |
discovery/brainstorm-ideas/ | Bidirectional | Pre-interview hypotheses; post-interview ideas seeded by themes |
discovery/brainstorm-experiments/ | Feeds into | Validated pains become experiment hypotheses |
discovery/jtbd-workshop/ | Complementary | Switch interviews use this script structure as their foundation |
discovery/value-proposition-canvas/ | Feeds into | Jobs, pains, and gains captured in stories populate the Customer Profile |
execution/create-prd/ | Feeds into | Direct quotes strengthen PRD Background and Market Segments |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (references, assets) in project-management/discovery/customer-interview-script of borghei/Claude-Skills.
- SKILL.md
- assets/interview_script_template.md
- assets/question_bank.md
- examples/churn-investigation-filled-script.md
- references/interview-execution-playbook.md
- references/interviewing-methodology-guide.md
- references/red-flags.md
Open the folder on GitHubat commit c9a1487
Compare with similar skills
Customer Interview Script next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Customer Interview Script this skillborghei/Claude-Skills | 874 | — | ~1.7k | Automated safety check: Pass | MIT | |
| User Research Cookiycookiy-ai/user-research-skill | 1.6k | — | ~954 | Automated safety check: Pass | MIT | |
| Fable DomainSahir619/fable-method | 2.3k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Produck Feedback To Buildtryproduck/produck-skills | 511 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| MITRE Problem Framing Canvasdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~4.5k | Automated safety check: Pass | Custom licence | |
| Customer InterviewsRefoundAI/lenny-skills | 1.4k | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Fable Domain
Sahir619/fable-method
Discuss a domain with the user, research it from real sources, then generate a trusted skill bundle for it - a step-by-step workflow with a flowchart, a domain adapter, a trap fixture, and a smoke…
Produck Feedback To Build
tryproduck/produck-skills
Pulls full in-context user feedback tickets through the Produck MCP server and turns them into an aligned product change instead of a guess.
MITRE Problem Framing Canvas
deanpeters/Product-Manager-Skills
Guides a three-phase canvas, looking inward, looking outward, then reframing, to produce an equity-aware problem statement.
Customer Interviews
RefoundAI/lenny-skills
Help users conduct high-impact customer interviews that move beyond surface-level feature requests to identify root emotional frustrations and specific causal triggers.
Product Discovery Brief Builder
open-mercato/skills
Guides a product discovery conversation and writes product-brief.md with the problem, evidence, scope, decisions and the next open question, for existing, client or own ideas.
More from borghei/Claude-Skills
All 364 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Customer Interview Script
What does Customer Interview Script do?
Run high-signal customer discovery interviews using a scripted question hierarchy, behavior-over-opinion probes, and rapport techniques drawn from Portigal, Torres, Fitzpatrick (Mom Test), and Lewis…. Customer Interview Script is an agent skill from borghei/Claude-Skills. Run high-signal customer discovery interviews using a scripted question hierarchy, behavior-over-opinion probes, and rapport techniques drawn from Portigal, Torres, Fitzpatrick (Mom Test), and Lewis Lin.
When should I use Customer Interview Script?
Customer Interview Script fits situations like: tasks that involve User research.
How do I install Customer Interview Script in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill customer-interview-script -a claude-code`. Or copy the skill folder (project-management/discovery/customer-interview-script in borghei/Claude-Skills) into .claude/skills/customer-interview-script in your project. Claude Code loads it when a task matches its description.
How do I install Customer Interview Script in Codex?
Run `npx skills add borghei/Claude-Skills --skill customer-interview-script -a codex`. Or copy the skill folder (project-management/discovery/customer-interview-script in borghei/Claude-Skills) into .agents/skills/customer-interview-script in your project. Codex loads it when a task matches its description.
Can I use Customer Interview Script in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill customer-interview-script -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/customer-interview-script, .gemini/skills/customer-interview-script, .github/skills/customer-interview-script and .opencode/skills/customer-interview-script in your project.
What does Customer Interview Script need to run?
SKILL.md names no scripts, command-line tools or credentials: Customer Interview Script is instructions for the agent only.
Does Customer Interview Script access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Customer Interview Script safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Customer Interview Script use?
Customer Interview Script is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Customer Interview Script use?
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.
What are the alternatives to Customer Interview Script?
Skills that share tags, products or a category with Customer Interview Script: User Research Cookiy (cookiy-ai/user-research-skill, 1.6k stars), Fable Domain (Sahir619/fable-method, 2.3k stars), Produck Feedback To Build (tryproduck/produck-skills, 511 stars) and MITRE Problem Framing Canvas (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Customer Interview Script?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.