Agent skill

Interview Me

by mohitagw15856 in mohitagw15856/pm-claude-skills

Elicit the real requirements by interviewing the requester BEFORE building or writing anything — one question at a time, until the brief is buildable.

MITAuto-check passedAgent Workflows

Install Interview Me

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill interview-me -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills interview-me --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/interview-me .claude/skills/interview-me && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
interview-me
GitHub stars
1.4k
Token cost
~1.2k tokens
SKILL.md length
612 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Elicit the real requirements by interviewing the requester BEFORE building or writing anything — one question at a time, until the brief is buildable.

  • Works in 6 steps: One question at a time. A wall of seven… → Sequence by decision-weight. The order… → Interrogate the difference, not the… → …
  • A request is vague (make me a dashboard
  • SKILL.md covers What This Skill Produces, When to Trigger (and when not), Interview Method and Output Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Interview Me is an agent skill from mohitagw15856/pm-claude-skills. Elicit the real requirements by interviewing the requester BEFORE building or writing anything — one question at a time, until the brief is buildable. Use when a request is vague ('make me a dashboard', 'write something for the board'), when past deliverables missed the mark, or when the user says 'interview me' / 'ask me questions first'. Produces a validated brief: goal, audience, constraints, success criteria, and explicit non-goals — then, and only then, the work.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Requirements gathering. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • A request is vague (make me a dashboard
  • Write something for the board)
  • Past deliverables missed the mark
  • The user says interview me / ask me questions first

Example prompts

  • “make me a dashboard”
  • “write something for the board”
  • “interview me”
  • “/interview-me”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. One question at a time. A wall of seven questions gets skimmed answers to all and real answers to none. Ask, absorb, let the answer shape…
  2. Sequence by decision-weight. The order that converges fastest
  3. Interrogate the difference, not the topic. Weak: "tell me more about the dashboard." Strong: "if this dashboard existed today, what…
  4. Offer forks, not open fields, when the requester is fuzzy. "Is this closer to (a) a live monitor the team glances at, or (b) a monthly…
  5. Know when to stop. 3-6 questions settles most briefs. Stop when a new answer wouldn't change what you'd build. Then play the brief back in…
  6. Ledger what's still open. Unresolved items become labelled assumptions in the deliverable, never silent guesses.

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Interview Me loads about 1.2k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 612 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~121
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 612 words, ~1,182 tokens.

Download SKILL.mdSave it as .claude/skills/interview-me/SKILL.md (or your agent's skills folder).
name
interview-me
description
Elicit the real requirements by interviewing the requester BEFORE building or writing anything — one question at a time, until the brief is buildable. Use when a request is vague ('make me a dashboard', 'write something for the board'), when past deliverables missed the mark, or when the user says 'interview me' / 'ask me questions first'. Produces a validated brief: goal, audience, constraints, success criteria, and explicit non-goals — then, and only then, the work.

Interview Me Skill

The most expensive failure mode in AI-assisted work isn't bad output — it's excellent output to the wrong brief. This skill inverts the flow: before producing anything, interview the requester like a senior consultant would, one question at a time, until the brief can survive contact with the deliverable.

What This Skill Produces

  • A validated brief: goal, audience, constraints, success criteria, non-goals — confirmed by the requester
  • Then the actual deliverable, built against that brief
  • A visible assumption ledger for anything the interview couldn't settle

When to Trigger (and when not)

Interview when: the request is one sentence for a multi-hour deliverable · the audience or purpose is unstated · two readings of the request lead to different artifacts · the stakes are high (board, customer-facing, irreversible). Skip the interview when the request is already specific, the pattern is established from earlier in the conversation, or the cost of a wrong draft is lower than the cost of five questions — say "I have enough to start" and start.

Interview Method

  1. One question at a time. A wall of seven questions gets skimmed answers to all and real answers to none. Ask, absorb, let the answer shape the next question.
  2. Sequence by decision-weight. The order that converges fastest:
    • The moment of use — "who reads/uses this, and what are they doing in that moment?" (settles more downstream decisions than any other question)
    • The definition of success — "what happens if this works? what would make you send it back?"
    • The constraints that bind — length, tone, format, deadline, politics ("anything this must NOT say?")
    • The prior art — "has something like this been tried/shown before? what happened?"
    • The non-goals — "what's adjacent that we're deliberately not doing?"
  3. Interrogate the difference, not the topic. Weak: "tell me more about the dashboard." Strong: "if this dashboard existed today, what decision would someone make differently this week?"
  4. Offer forks, not open fields, when the requester is fuzzy. "Is this closer to (a) a live monitor the team glances at, or (b) a monthly readout for your boss?" — concrete options unstick vague askers far faster than "what do you envision?"
  5. Know when to stop. 3-6 questions settles most briefs. Stop when a new answer wouldn't change what you'd build. Then play the brief back in ≤5 lines and get an explicit "yes, build that."
  6. Ledger what's still open. Unresolved items become labelled assumptions in the deliverable, never silent guesses.
Show full SKILL.md (209 more words)Show less

Output Format

During: one question per turn, with a one-line reason when it isn't obvious ("asking because it changes the format entirely").

The brief playback:

Building: [artifact] for [audience in their moment] so that [the decision/outcome]. Success: … · Constraints: … · Not doing: … Assumed (unconfirmed): … Confirm and I'll build it.

Quality Checks

  • Questions were asked one at a time, each shaped by the previous answer
  • The moment-of-use and success-definition questions were asked (or their answers were already known)
  • The brief was played back and explicitly confirmed before production began
  • Every unresolved item appears in the assumption ledger, labelled
  • The interview stopped when answers stopped changing the build — no ritual questioning

Anti-Patterns

  • Do not fire a questionnaire — seven questions at once produces skim-answers and resentment
  • Do not interview when the brief is already clear — process applied without judgment is friction
  • Do not ask questions whose answers wouldn't change the deliverable — every question spends the requester's patience
  • Do not start building mid-interview "to save time" — half-brief work anchors the requester to the wrong draft
  • Do not skip the playback — the interview's value is captured only when the requester says "yes, that"

Example Trigger Phrases

  • "Interview me before you build anything."
  • "Ask me questions first."
  • "Make me a dashboard."
  • "Work out what I actually need."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/interview-me of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Interview Me next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Interview Me compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Interview Me this skillmohitagw15856/pm-claude-skills1.4k—~1.2kAutomated safety check: PassMIT
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Interview Meaddyosmani/agent-skills103k6 repos~3.8kAutomated safety check: PassMIT
Grillingpietheinstrengholt/rssmonster56431 repos~510Automated safety check: PassMIT
Agentic Workflow Designerdotnet/Open-XML-SDK4.6k2 repos~3.5kAutomated safety check: PassMIT
Ask User QuestionMemTensor/MemOS12k—~1kAutomated safety check: PassApache-2.0

Similar skills

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Interview Me

    addyosmani/agent-skills

    Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.

    103k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • Grilling

    pietheinstrengholt/rssmonster

    Grill the user relentlessly about a plan, decision, or idea.

    564 GitHub starsUsed in 31 repos~510 tokens
    Agent WorkflowsAuto-check passed
  • Agentic Workflow Designer

    dotnet/Open-XML-SDK

    Official

    Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.

    4.6k GitHub starsUsed in 2 repos~3.5k tokens
    Agent WorkflowsAuto-check passed
  • Ask User Question

    MemTensor/MemOS

    Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.

    12k GitHub stars~1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Brainstorming Before Building

    jnMetaCode/superpowers-zh

    Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.

    8.3k GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Interview Me

What does Interview Me do?

Elicit the real requirements by interviewing the requester BEFORE building or writing anything — one question at a time, until the brief is buildable. Interview Me is an agent skill from mohitagw15856/pm-claude-skills. Elicit the real requirements by interviewing the requester BEFORE building or writing anything — one question at a time, until the brief is buildable.

When should I use Interview Me?

Interview Me fits situations like: A request is vague (make me a dashboard; write something for the board); past deliverables missed the mark; the user says interview me / ask me questions first.

How do I install Interview Me in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill interview-me -a claude-code`. Or copy the skill folder (skills/interview-me in mohitagw15856/pm-claude-skills) into .claude/skills/interview-me in your project. Claude Code loads it when a task matches its description.

How do I install Interview Me in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill interview-me -a codex`. Or copy the skill folder (skills/interview-me in mohitagw15856/pm-claude-skills) into .agents/skills/interview-me in your project. Codex loads it when a task matches its description.

Can I use Interview Me in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill interview-me -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/interview-me, .gemini/skills/interview-me, .github/skills/interview-me and .opencode/skills/interview-me in your project.

What does Interview Me need to run?

SKILL.md names no scripts, command-line tools or credentials: Interview Me is instructions for the agent only.

Does Interview Me access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Interview Me safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Interview Me use?

Interview Me is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Interview Me use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Interview Me?

Skills that share tags, products or a category with Interview Me: Using Superpowers (farm-fe/farm, 5.6k stars), Interview Me (addyosmani/agent-skills, 103k stars), Grilling (pietheinstrengholt/rssmonster, 564 stars) and Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Interview Me?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.