Agent skill · Documentation

interview-me

Interview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.

Neeeophyteegithub.com/NeeeophyteeGitHub ↗
claude-codecodexcursorNOASSERTION
Install
npx skills add Neeeophytee/finding-unknowns-skills --skill interview-me --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Path: skills/interview-me/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 298

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Interview me Brainstorming is over and there are still gaps between the user's map and the territory. Close them by asking, one question at a time, starting with the questions whose answers would change the most. ## Steps 1. Read everything already established: the request, any spec, any prototypes, relevant code. Do not ask about things that are already answered. 2. Build a private list of open ambiguities and sort by blast radius: - **First: architecture-changers** — answers that would alter the data model, the interfaces, or the overall approach. - **Then: behavior definers** — edge cases, failure modes, defaults, permissions. - **Last: polish** — naming, copy, cosmetics. Often not worth asking; propose and move on. 3. Ask exactly one question per turn. For each: give the context that makes it matter, offer 2-3 concrete options with your recommendation, and accept "you decide" as an answer you then own. 4. Every few questions, checkpoint: restate what has been decided so far in one tight list, so drift dies early. 5. Stop when the remaining unknowns are cheaper to discover during implementation than to ask about now, and say that out loud. End with the final decision list, rea

What's inside
Steps it walks through
  1. Steps
  2. Guardrails
More from finding-unknowns-skills
All skills →
About this skill
What does the interview-me skill do?

Interview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.

How do I install it?

Run `npx skills add Neeeophytee/finding-unknowns-skills --skill interview-me --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Neeeophytee/finding-unknowns-skills, a repository with 298 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going