Borrowing it
Nothing to install: this file belongs to ertra/pm-brain-for-cursor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ertra/pm-brain-for-cursor/main/.cursor/skills/interview-frameworks/SKILL.mdgit clone --depth 1 https://github.com/ertra/pm-brain-for-cursorWrote 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/ertra/pm-brain-for-cursor/interview-frameworks)<a href="https://agentmods.dev/skills/ertra/pm-brain-for-cursor/interview-frameworks"><img src="https://agentmods.dev/badge/skills/ertra/pm-brain-for-cursor/interview-frameworks/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/ertra/pm-brain-for-cursor/interview-frameworks"><img src="https://agentmods.dev/badge/skills/ertra/pm-brain-for-cursor/interview-frameworks.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.00069 | $0.03265 |
| Opus 5.5 | $0.00028 | $0.01306 |
| Sonnet 5.5 | $0.00014 | $0.00653 |
| Haiku 4.5 | $0.00007 | $0.00327 |
Grade A, and why
interview-frameworks 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 1mo 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 — 505 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Frameworks
Overview
Frameworks for conducting effective user interviews including question design, interviewing techniques, and extracting actionable insights.
Core Principle: Good interviews come from great questions. Focus on past behavior and specific examples, not hypotheticals or opinions. Listen more than you talk.
Origin: Synthesized from Teresa Torres ("Continuous Discovery Habits"), Erika Hall ("Just Enough Research"), and Rob Fitzpatrick ("The Mom Test").
Key Insight: User interviews are the foundation of customer discovery. Good interviews uncover unmet needs, validate assumptions, and reveal the "why" behind user behavior that quantitative data cannot.
When to Use This Skill
Use when you need:
- Customer discovery research
- Problem validation
- Solution validation
- Usability testing
- Feature prioritization research
- Understanding user workflows
- Jobs-to-be-Done research
Four Types of User Interviews
Discovery Interviews (Problem Exploration)
Purpose: Understand problems, needs, contexts, pain points
When: Early product development, new market, problem validation
Focus:
- Current workflows
- Pain points and workarounds
- Unmet needs
- Context and constraints
Example question: "Walk me through how you currently manage projects for your team"
Complete script: assets/interview-script-templates.md (Discovery section)
Validation Interviews (Solution Testing)
Purpose: Test solutions, get feedback on concepts
When: After problem validation, before building
Focus:
- Solution fit with workflow
- Feature prioritization
- Willingness to pay
- Alternatives considered
Example question: "If we built [solution], how would that fit into your workflow?"
Complete script: assets/interview-script-templates.md (Validation section)
Usability Interviews (Product Testing)
Purpose: Test actual product, identify friction
When: During or after building
What ships with it
6 files 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.
- 1mo ago First seen · 505 lines · 69 tokens per session scan A 7ed509e37664
interview-frameworks is a skill published in the GitHub repository ertra/pm-brain-for-cursor (22 stars, last pushed 5mo ago), licensed MIT. It adds 69 tokens to every session and 3,265 once invoked, about $0.0003 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-30.
Other skills, from other repositories
replit-deck
For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query "pm-feature-business-case-deck", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident…
hps-true-blueprint
OpenDesign's engineering blueprint: how the sandbox, sidecar, and daemon fit — the system diagram and the invariants. Built as a decision-grade product management deck for engineering org.
design-critique
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
analytics-product
Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.
deck-open-slide-canvas
OpenDesign's architecture review: the local daemon + agent-runtime design, the tradeoffs, and the decision to lock. Built as a decision-grade product management deck for staff eng, tech leads, security.
mockup-device-3d
Static iPhone and MacBook 3D-style showcase with real HTML embedded on screens, glass-lens refraction, and 360-degree turntable composition.