discovery-interview

discovery-interview is a skill for Claude Code, Codex from event4u-app/agent-config. It costs 41 tokens per session (1,553 once invoked), scanned A, original, MIT.

A method for planning and improving customer-discovery interviews, including interview questions, bias checks, and structured analysis of transcripts.

In plain words
What is it for?
It is for auditing interview guides, checking whether hypotheses can be disproved, and extracting organized insights from interview transcripts.
Why use it?
It helps teams avoid leading questions and confusing vivid individual comments with reliable patterns across interviews.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for auditing interview guides, checking whether hypotheses can be disproved, and extracting organized insights from interview transcripts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/event4u-app/agent-config/discovery-interview
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add event4u-app/agent-config --skill discovery-interview
Clone the repo
git clone --depth 1 https://github.com/event4u-app/agent-config

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for discovery-interview

README.md
[![agentmods](https://agentmods.dev/badge/skills/event4u-app/agent-config/discovery-interview/github.svg)](https://agentmods.dev/skills/event4u-app/agent-config/discovery-interview)
Your own site
<a href="https://agentmods.dev/skills/event4u-app/agent-config/discovery-interview"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/discovery-interview/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for discovery-interview

Your own site · 80×15
<a href="https://agentmods.dev/skills/event4u-app/agent-config/discovery-interview"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/discovery-interview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,553 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.01553
Opus 5 $0.00020 $0.00776
Sonnet 5 $0.00008 $0.00311
Haiku 4.5 $0.00004 $0.00155

Measured 7d ago against content hash a3ce7d32368d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

discovery-interview scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/skills/discovery-interview/SKILL.md · 163 lines

How it starts

The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.

discovery-interview

When to use

  • A discovery slice has been framed (customer-research ran), but the interview guide is still rough or untested.
  • A transcript exists and the team needs structured insight extraction, not narrative summary.
  • An interview round produced surprising findings; a bias audit is needed before the team acts on them.

Do NOT use for the upstream framing of the discovery slice (frame sentence, recruit criteria, JTBD focal job) — that is customer-research. Do NOT use for quantitative survey design or scale-bound research.

Cognition cluster

  • Mental model 22 — Data-informed, not data-driven. Interview data is signal at low N; treat it as evidence to reason with, not a vote count. See docs/contracts/mental-models.md § 22.
  • Mental model 15 — Signal vs noise. A vivid quote from one articulate user can swamp three muted but consistent signals; frequency-rank by distinct people, never by quote count. See mental-models.md § 15.
  • Mental model 28 — Eisenhower matrix. Sort post-interview insights into urgent / important quadrants so the team acts on high-importance signals, not the loudest ones. See mental-models.md § 28.
  • Product context-spine slot. Read product for the focal job
    • competitor names; do not re-derive these inside this skill. See context-spine.

Procedure

1. Build the question bank

  1. Anchor on the switch event from customer-research. The first question is always "Walk me through the day you decided to ..." — never "would you ...".
  2. Three layers:
    • Past behaviour (what did you do? when? alternative considered?)
    • Anxiety / habit (what feared in switching? what habit died?)
    • Outcome (what changed for you? expected? unexpected?)
  3. Cap at 8 open questions per 45-min slot. Beyond that, the interview becomes a survey delivered in person.

Read the full file on GitHub · 163 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 163 lines · 41 tokens per session scan A a3ce7d32368d

Subscribe to this mod's changes

discovery-interview is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,553 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

save-progress

Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…

KimYx0207/Meta_Kim · 65 tokens

same-set-reusable-flow-for-project-file-inventor

Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.

KimYx0207/Meta_Kim · 45 tokens

meta-theory

MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.

KimYx0207/Meta_Kim · 57 tokens

starreel-drama-production

Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…

waydaxp/starreel-mcp · 102 tokens

seedance-20

Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…

Kingdaddy007/my-os · 96 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens