interview-me
An agent skill by addyosmani, from addyosmani/agent-skills. Tags: design, documents.
What it does
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add addyosmani/agent-skills --skill interview-meOr copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/addyosmani/agent-skills
cp -r agent-skills/skills/interview-me ~/.claude/skills/interview-meSafety box score
Grade A, minimal risk: 4 of 100 risk points, rated 2026-09-20. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
Source
- Repository
- addyosmani/agent-skills (all skills from this repository)
- Path
- skills/interview-me/SKILL.md
- Branch
- main
- Updated
- 2026-09-19
Related skills
- design-md — Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
- stitch::extract-static-html — Extract self-contained static HTML from a built web application or React components by inlining CSS and images.
- stitch::manage-design-system — Manage design systems in Stitch using MCP tools. Includes retrieval of assets, creating/updating design systems in Stitch, and applying them to screens.
- api-and-interface-design — Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface.
- idea-refine — Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking.
- spec-driven-development — Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet.