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.
npx agentmods add skills/kazdenc/builder-skills/interviewnpx skills add kazdenc/builder-skills --skill interviewgit clone --depth 1 https://github.com/kazdenc/builder-skillsWrote 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.
[](https://agentmods.dev/skills/kazdenc/builder-skills/interview)<a href="https://agentmods.dev/skills/kazdenc/builder-skills/interview"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/interview.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00055 | $0.01071 |
| Opus 5 | $0.00028 | $0.00535 |
| Sonnet 5 | $0.00011 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Interviews
This skill operates in two modes. Pick the one that matches what you have.
- GENERATE — You have a topic or feature area. You need an interview script.
- ANALYZE — You have a transcript (or notes). You need structured insights.
GENERATE Mode — Build an Interview Script
Structure every interview in three acts:
┌─────────────────────────────────────────┐
│ 1. WARM-UP (5 min) │ Build rapport, set context
│ 2. CORE QUESTIONS (30–40 min) │ Explore the job, past behavior
│ 3. WRAP-UP (5 min) │ Open floor, next steps
└─────────────────────────────────────────┘
Warm-Up
Set the participant at ease. Explain there are no wrong answers, you're learning from them, and they can skip anything. Ask one or two easy background questions to get them talking.
Core Questions
Use these question types, in roughly this order:
| Type | Purpose | Starter |
|---|---|---|
| Context | Understand their world | "Walk me through a typical day when you..." |
| Behavioral | Surface real past actions | "Tell me about the last time you..." |
| JTBD | Uncover the job and switching triggers | "What were you trying to accomplish when you decided to..." |
| Process | Map their current workflow | "What happened next? And after that?" |
| Emotional | Find pain and delight | "How did that make you feel? What was the hardest part?" |
| Magnitude | Gauge importance | "How big a deal is that for you? What's at stake?" |
Follow every answer with "Why?" or "Can you tell me more about that?" until you reach concrete specifics.
Wrap-Up
Ask "Is there anything I should have asked but didn't?" — this regularly surfaces the most valuable insight of the session. Thank them and explain what happens next.
Good vs Bad Questions
| Bad (avoid) | Why it fails | Good (use instead) |
|---|---|---|
| "Would you use a feature that does X?" | Hypothetical — people can't predict future behavior | "Tell me about the last time you needed to do X." |
| "Don't you think this is frustrating?" | Leading — suggests the answer | "How do you feel about that part of the process?" |
| "Do you like A or B better?" | Binary — closes exploration | "What matters most to you when you're doing this?" |
| "How often would you use this?" | Speculative frequency | "How often did you do this in the past month?" |
| "Users like you typically want..." | Primes agreement | "What do you wish were different?" |
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.
- 4d ago First seen · 102 lines · 55 tokens per session scan A d53c9593d75f
interview is a skill published in the GitHub repository kazdenc/builder-skills (44 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 1,071 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…
rebase-themes
Rebase all theme- branches onto main, resolving conflicts while preserving each theme's visual identity. Force-pushes directly to theme branches with backup tags. Run as a scheduled task or one-off.