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 skills add assimovt/productskills --skill user-interviewgit clone --depth 1 https://github.com/assimovt/productskillsWrote 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/assimovt/productskills/user-interview)<a href="https://agentmods.dev/skills/assimovt/productskills/user-interview"><img src="https://agentmods.dev/badge/skills/assimovt/productskills/user-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.
<a href="https://agentmods.dev/skills/assimovt/productskills/user-interview"><img src="https://agentmods.dev/badge/skills/assimovt/productskills/user-interview.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00055 | $0.00822 |
| Opus 5 | $0.00028 | $0.00411 |
| Sonnet 5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
user-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 10d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run user interviews that surface real problems, not polite lies. Most interviews fail because the interviewer pitches their idea and asks "would you use this?" The Mom Test (Rob Fitzpatrick) fixes this: talk about their life, not your idea.
The Five Questions (Eric Migicovsky, YC)
Use these as the backbone of every interview. They work in order — each question digs deeper.
-
What's the hardest part about [doing the thing you're exploring]? Opens with their pain, not your solution.
-
Tell me about the last time you encountered that problem. Forces specifics. Past behavior > hypothetical opinions.
-
Why was that hard? Uncovers root cause. Their first answer is usually surface-level.
-
What, if anything, have you done to try to solve this? Existing workarounds = real pain. No workarounds = not painful enough.
-
What don't you love about the solutions you've tried? Reveals gaps in existing alternatives. This is your opportunity space.
Mom Test Rules
These rules override all default interviewing instincts:
- NEVER ask "Would you use this?" or "What would you pay?" — hypothetical questions get hypothetical answers.
- NEVER pitch your solution during the interview. The moment you pitch, you stop learning.
- ALWAYS ask about past behavior. "Tell me about the last time..." not "Would you ever..."
- Deflect compliments immediately. "That sounds great!" → "Thanks — but tell me more about how you currently handle this."
- Anchor fluff to specifics. "I always struggle with..." → "When was the last time? Walk me through it."
Follow-up Framework (Gustaf Alstromer, YC)
After the Five Questions, probe for signal strength:
- Frequency: "How often does this come up?" (Daily = strong signal)
- Workarounds: "Show me how you do it today." (Screenshots, spreadsheets, hacks = gold)
- Willingness to pay: "Have you looked for or paid for a solution?" (Spending = strongest signal)
- Emotional weight: Watch for energy shifts — frustration, sighing, storytelling. That's where the real pain lives.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 68 lines · 55 tokens per session scan A 7b5bbf151147
user-interview is a skill published in the GitHub repository assimovt/productskills (68 stars, last pushed 6mo ago), licensed MIT. It adds 55 tokens to every session and 822 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
handoff
Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a…
prd-taskmaster
Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes…
generate
Phase 2 of the prd-taskmaster pipeline: spec generation and task parsing. Loads a template (comprehensive|minimal), fills it with DISCOVER-phase constraints and answers, validates the spec (placeholdersfound, grade thresholds), parses the PRD into tasks via task-master, runs TaskMaster's native complexity analysis…
customise-workflow
Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default…
discover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the…
execute-fleet
Phase execution skill for licensed Atlas Fleet runs. Use when HANDOFF has selected Atlas Fleet and the project should be executed across isolated launcher worktrees with inbox-based result collection, verified CDD cards, sequential integration merges, and one final PR.