New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Interviews

by davepoon in davepoon/buildwithclaude

Manages the founder's customer discovery interview lifecycle — drafting scripts tailored to a target segment, refining existing ones, managing script status, and analyzing interview transcripts to…

MITAuto-check passedProduct & Project Management

Install Interviews

skills CLI
$ npx skills add davepoon/buildwithclaude --skill interviews -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davepoon/buildwithclaude interviews --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/startup-superpowers/skills/interviews .claude/skills/interviews && rm -rf skills-src

Use ~/.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/

Facts

Skill name
interviews
GitHub stars
3.6k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
691 words
Files
3 (incl. references)
Skills in repo
245
Repo updated
First seen
Licence
MIT

At a glance

Manages the founder's customer discovery interview lifecycle — drafting scripts tailored to a target segment, refining existing ones, managing script status, and analyzing interview transcripts to…

  • Works in 2 steps: Script management — drafting, refining,… → Transcript analysis — after an interview…
  • The founder wants to prep for interviews
  • SKILL.md covers Before you start, When scripts already exist, When no scripts exist and When a transcript arrives
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Interviews is an agent skill from davepoon/buildwithclaude. Manages the founder's customer discovery interview lifecycle — drafting scripts tailored to a target segment, refining existing ones, managing script status, and analyzing interview transcripts to extract insights, review technique, and update hypothesis state. Use when the founder wants to prep for interviews, draft a discovery script, refine questions, change a script's status, analyze a completed interview (transcript, paste, or recollection), extract insights, or review how an interview went.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/initial-interview-script.md` and `references/transcript-analysis.md`).

It sits in Product & Project Management, covering User research. The repository describes itself as: A single hub to find Claude Skills, Agents, Commands, Hooks, Plugins, and Marketplace collections to extend Claude Code, Claude Desktop, Agent SDK and OpenClaw. The licence is MIT.

When your agent uses it

  • The founder wants to prep for interviews
  • Draft a discovery script
  • Refine questions
  • Change a scripts status

Example prompts

  • “Use the interviews skill to manage the founder's customer discovery interview lifecycle — drafting scripts tailored to a target segment, refining…”
  • “/interviews”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Script management — drafting, refining, and managing the lifecycle of reusable interview scripts.
  2. Transcript analysis — after an interview has happened, extracting statements, linking them to hypotheses, reviewing the founder's…

What it can do on your machine

Read from SKILL.md and the folder at commit 10bfc43. 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 (its code samples are bash).

    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

Interviews loads about 1.4k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 128 tokens; SKILL.md has 691 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.4k

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 davepoon/buildwithclaude at commit 10bfc43, republished under its MIT licence (© davepoon). 691 words, ~1,445 tokens.

Download SKILL.mdSave it as .claude/skills/interviews/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
interviews
description
Manages the founder's customer discovery interview lifecycle — drafting scripts tailored to a target segment, refining existing ones, managing script status, and analyzing interview transcripts to extract insights, review technique, and update hypothesis state. Use when the founder wants to prep for interviews, draft a discovery script, refine questions, change a script's status, analyze a completed interview (transcript, paste, or recollection), extract insights, or review how an interview went.

Interviews

Help the founder run the full customer discovery interview loop — from preparing a script to analyzing what was said afterward.

This skill covers two phases:

  1. Script management — drafting, refining, and managing the lifecycle of reusable interview scripts.
  2. Transcript analysis — after an interview has happened, extracting statements, linking them to hypotheses, reviewing the founder's interviewing technique, and recommending hypothesis state changes.

An interview script is a reusable guide, not a teleprompter: it anchors the conversation around the assumptions being tested while leaving room for the founder to follow threads that open up. Most founders need one script for their primary segment; occasionally a second script for an adjacent segment.

Before you start

Read startup/core.md to load project context (name, seed description, and all fields under ## Core — especially Audience).

Check if startup/interview-scripts/ contains any .md files.

Scaffold the folders if they don't exist yet:

bash
mkdir -p startup/interview-scripts
mkdir -p startup/interviews/transcripts

When scripts already exist

Load and understand them for context. Infer intent from the conversation — don't mechanically ask "what do you want to do?" If the founder is:

  • Referring to a specific script — load that file, discuss, help edit the relevant section
  • Iterating after running interviews — help revise questions that didn't land, add follow-ups that proved useful, tighten or expand as needed
  • Drafting a script for a different segment — start a new script (route to the reference file below if they want a guided draft, or draft directly if they know what they want)
  • Changing status — read the file, propose the change, write it back
    • draft — still being shaped, not yet used
    • ready — actively in use for interviews
    • retired — superseded or no longer in rotation

When adding or updating scripts, follow the file conventions:

  • YAML frontmatter with status (draft, ready, retired), length_minutes (number — 15/30/45/60), and target_persona (one-line segment descriptor)
  • H1 heading: script title — segment + focus, e.g. "Freelance designers — invoice chasing"
  • ## Target Persona — 2–4 sentences describing who this script is for and why
  • ## Opening — what the founder says at the start: purpose, consent to record, framing
  • ## Core Questions — numbered questions with optional indented probes
  • ## Closing — wrap-up, referrals ask, thank-you
  • Optional ## Notes — facilitation tips for the founder

Slug convention: lowercase the title, replace spaces and non-alphanumeric characters with hyphens, collapse multiple hyphens. "Freelance designers — invoice chasing" → freelance-designers-invoice-chasing.

Read before writing, propose before saving, get confirmation.

Show full SKILL.md (313 more words)Show less

When no scripts exist

Check prerequisites:

  • core.md is missing or has no Audience or similar information that provides this information under ## Core: Mention that a defined target audience sharpens the script considerably — suggest filling that in first (via the whats-next skill or directly in core.md). Do not block: if the founder wants to proceed with a rough persona, proceed.

  • startup/hypotheses/ is empty or has fewer than 3 hypotheses: Mention that scripts work best when they're built around specific hypotheses to test — suggest invoking the hypotheses skill first. Do not block: if the founder insists on drafting a script now, proceed.

  • Prerequisites met (or founder insists): Load the reference file for the guided script-creation conversation:

.claude/skills/interviews/references/initial-interview-script.md

The reference file's instructions take over from this point.

When a transcript arrives

After the founder runs an interview, they may bring back a transcript, paste text into chat, or simply recount a conversation from memory. In any of these cases, the workflow is the same: save the source material, dispatch the interview-analyst subagent, then dispatch the hypotheses-manager subagent, surface recommendations to the founder, and route confirmed hypothesis changes through the hypotheses skill.

Recognize this intent when the founder:

  • Points at a transcript file under startup/interviews/transcripts/ (or similar)
  • Pastes transcript-shaped text (dialogue, Q&A, long monologue) into chat
  • Describes a conversation from memory ("I talked to someone at a coffee shop…", "I had a call with a designer and she said…")
  • Asks to analyze, review, or extract insights from a completed interview

Load the Layer 2 reference file that owns this workflow end-to-end:

.claude/skills/interviews/references/transcript-analysis.md

The reference file's instructions take over from this point, including the three input branches (file / pasted / recollection), dispatching both subagents, summarizing to the founder, and routing confirmed edits through the hypotheses skill.

Do not extract statements, evaluate hypothesis state, or edit hypothesis files yourself — the reference file describes how to delegate that work to the two subagents.

© davepoon, 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 2 other files (references) in plugins/startup-superpowers/skills/interviews of davepoon/buildwithclaude.

  • SKILL.md
  • references/initial-interview-script.md
  • references/transcript-analysis.md

Open the folder on GitHubat commit 10bfc43

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in davepoon/buildwithclaude, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Interviews 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.

Interviews compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Interviews this skilldavepoon/buildwithclaude3.6k1 repos~1.4kAutomated safety check: PassMIT
User Research Cookiycookiy-ai/user-research-skill1.6k—~954Automated safety check: PassMIT
Fable DomainSahir619/fable-method2.3k—~2.6kAutomated safety check: PassMIT
Produck Feedback To Buildtryproduck/produck-skills510—~1kAutomated safety check: PassApache-2.0
MITRE Problem Framing Canvasdeanpeters/Product-Manager-Skills7.2k2 repos~4.5kAutomated safety check: PassCustom licence
Customer InterviewsRefoundAI/lenny-skills1.4k—~1.7kAutomated safety check: PassMIT

Similar skills

  • User Research Cookiy

    cookiy-ai/user-research-skill

    End-to-end user research assistant — qualitative and quantitative.

    1.6k GitHub stars~954 tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • 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…

    2.3k GitHub stars~2.6k tokensUpdated 5 days ago
    Product & Project ManagementAuto-check passed

  • 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.

    510 GitHub stars~1k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • 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.

    7.2k GitHub starsUsed in 2 repos~4.5k tokens
    Product & Project ManagementAuto-check passed

  • 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.

    1.4k GitHub stars~1.7k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed

  • 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.

    227 GitHub stars~3k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

More from davepoon/buildwithclaude

All 245 skills in this repo

  • Qwen Vision

    davepoon/buildwithclaude

    A skill your agent uses when the user asks to "analyze video", "watch this video", "what happens in this video", "describe this clip", "review this footage", "classify these videos", "compare…

    3.6k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed

  • Hard Predict Future

    davepoon/buildwithclaude

    Activate this agent for any future-oriented question that requires deep quantitative analysis, historical precedents, and structured scenario planning.

    3.6k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed

  • iOS Hig Design Guide

    davepoon/buildwithclaude

    Build, update, and apply iOS design specifications using Apple Human Interface Guidelines (HIG) source data.

    3.6k GitHub stars~735 tokensUpdated yesterday
    Auto-check passed

  • Video Downloader

    davepoon/buildwithclaude

    Download YouTube videos with customizable quality and format options.

    3.6k GitHub starsUsed in 1 repo~871 tokens
    Auto-check passed

  • Atlas Cloud Media

    davepoon/buildwithclaude

    Discover Atlas Cloud image and video models, inspect their live schemas, and submit one confirmed media generation request with bounded GET polling.

    3.6k GitHub stars~852 tokensUpdated yesterday
    Auto-check passed

  • Slack Gif Creator

    davepoon/buildwithclaude

    Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives.

    3.6k GitHub starsUsed in 12 repos~4.3k tokens
    Auto-check passed

Categories

Questions about Interviews

What does Interviews do?

Manages the founder's customer discovery interview lifecycle — drafting scripts tailored to a target segment, refining existing ones, managing script status, and analyzing interview transcripts to…. Interviews is an agent skill from davepoon/buildwithclaude. Manages the founder's customer discovery interview lifecycle — drafting scripts tailored to a target segment, refining existing ones, managing script status, and analyzing interview transcripts to extract insights, review technique, and update hypothesis state.

When should I use Interviews?

Interviews fits situations like: the founder wants to prep for interviews; draft a discovery script; refine questions; change a scripts status.

How do I install Interviews in Claude Code?

Run `npx skills add davepoon/buildwithclaude --skill interviews -a claude-code`. Or copy the skill folder (plugins/startup-superpowers/skills/interviews in davepoon/buildwithclaude) into .claude/skills/interviews in your project. Claude Code loads it when a task matches its description.

How do I install Interviews in Codex?

Run `npx skills add davepoon/buildwithclaude --skill interviews -a codex`. Or copy the skill folder (plugins/startup-superpowers/skills/interviews in davepoon/buildwithclaude) into .agents/skills/interviews in your project. Codex loads it when a task matches its description.

Can I use Interviews 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 davepoon/buildwithclaude --skill interviews -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/interviews, .gemini/skills/interviews, .github/skills/interviews and .opencode/skills/interviews in your project.

What does Interviews need to run?

SKILL.md names no scripts, command-line tools or credentials: Interviews is instructions for the agent only.

Does Interviews 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 Interviews 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 Interviews use?

Interviews is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Interviews use?

About 1.4k tokens (SKILL.md is roughly 5.8k 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 5k tokens, read only when the agent opens those files.

What are the alternatives to Interviews?

Skills that share tags, products or a category with Interviews: 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, 510 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 Interviews?

davepoon (a GitHub user) maintains it in davepoon/buildwithclaude, which has 3,604 GitHub stars. The repository holds 245 skills in this directory. The repository was last updated on October 6, 2026.

Source: davepoon/buildwithclaude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.