customer-interviews

customer-interviews is a skill for Claude Code, Codex from uthumany/uthy-legacy-os. It costs 30 tokens per session (1,102 once invoked), scanned A, original, MIT.

A structured method for interviewing potential customers to learn about their real problems and past behavior. Customer discovery means researching whether a problem matters before designing a solution.

In plain words
What is it for?
Use it to set learning goals, write interview questions, recruit participants, and conduct early product research.
Why use it?
It helps replace guesses and leading questions with evidence from conversations with people who may use the product.

Skill for Claude CodeCodex

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

Good fit Use it to set learning goals, write interview questions, recruit participants, and conduct early product research.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/uthumany/uthy-legacy-os/customer-interviews
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 uthumany/uthy-legacy-os --skill customer-interviews
Clone the repo
git clone --depth 1 https://github.com/uthumany/uthy-legacy-os

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 customer-interviews

README.md
[![agentmods](https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/customer-interviews/github.svg)](https://agentmods.dev/skills/uthumany/uthy-legacy-os/customer-interviews)
Your own site
<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/customer-interviews"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/customer-interviews/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 customer-interviews

Your own site · 80×15
<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/customer-interviews"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/customer-interviews.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,102 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.00030 $0.01102
Opus 5.5 $0.00012 $0.00441
Sonnet 5.5 $0.00006 $0.00220
Haiku 4.5 $0.00003 $0.00110

Measured 2mo ago against content hash 60f05101cc91, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

customer-interviews 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 2mo 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.

skills/discovery/customer-interviews/SKILL.md · 104 lines

How it starts

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

Customer Discovery Interviews

Overview

Customer discovery interviews are the bedrock of evidence-based product management. This skill turns casual user conversations into structured discovery — helping you uncover real problems, avoid solution bias, and build products people actually need. Rooted in The Mom Test by Rob Fitzpatrick and Continuous Discovery Habits by Teresa Torres.

When to Use

  • You're entering a new problem space with unvalidated assumptions
  • You need to understand why users behave a certain way
  • You want to test an opportunity before exploring solutions
  • You're preparing for a product discovery sprint
  • Don't use for: usability testing (use validation-interview instead), market research surveys (too structured), or customer satisfaction calls

Instructions

Phase 1: Plan the Interviews

  1. Define your learning goals — What 3-5 things do you want to learn? Frame as open-ended questions about past behavior, not future intent.
  2. Write the interview guide — Start with broad context, narrow to specifics. Never ask "Would you use X?" — ask "Tell me about the last time you dealt with Y."
  3. Recruit participants — Aim for 5-8 per segment. Use customer discovery criteria: they should have the problem, not necessarily use your product.
  4. Avoid bias — Do not mention your solution idea. Do not pitch. Do not lead.

Phase 2: Conduct the Interview

  1. Build rapport — Thank them, explain the goal is to learn, not sell. Ask permission to record.
  2. Ask about specific moments — "Walk me through the last time you..." beats "How often do you..."
  3. Listen for emotion — Strong frustration, workarounds, and surprising effort signal real problems.
  4. Use the Mom Test principles:
    • Talk about their life, not your idea
    • Ask about specifics from the past, not hypotheticals about the future
    • Listen for commitments (time, introductions, money) — compliments are cheap
  5. Dig deeper — When they mention something interesting: "Tell me more about that." "Why did you do it that way?" "What happened next?"

Read the full file on GitHub · 104 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. 2mo ago First seen · 104 lines · 30 tokens per session scan A 60f05101cc91

Subscribe to this mod's changes

customer-interviews is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 1,102 once invoked, about $0.0001 per session on Opus 5.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-08-31.

Related

customer-interviews compared with skills from other repositories

customer-interviews next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
customer-interviewsuthumany/uthy-legacy-osSkill55mo agoMITA30Claude Code, Codex
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex