interview-me

interview-me is a skill for Claude Code, Codex from BlackBeltTechnology/pi-agent-dashboard. It costs 90 tokens per session (3,212 once invoked), scanned A, a copy of interview-me, MIT.

A guided interview that asks one question at a time to clarify an underspecified request before planning or writing a specification. It focuses on the user, reason, success criteria, and constraints.

In plain words
What is it for?
Use it when someone asks for a feature without clearly stating who it is for, why it matters, how success is measured, or what limits apply.
Why use it?
It helps distinguish the requested solution from the underlying problem before work begins. Finding that mismatch early avoids building the wrong thing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when someone asks for a feature without clearly stating who it is for, why it matters, how success is measured, or what limits apply.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/blackbelttechnology/pi-agent-dashboard/interview-me
Install

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.

Any agent
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill interview-me
Clone the repo
git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for interview-me

README.md
[![agentmods](https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/interview-me/github.svg)](https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/interview-me)
Your own site
<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/interview-me"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/interview-me/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.

agentmods 80×15 button for interview-me

Your own site · 80×15
<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/interview-me"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/interview-me.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,212 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00090 $0.03212
Opus 5 $0.00045 $0.01606
Sonnet 5 $0.00018 $0.00642
Haiku 4.5 $0.00009 $0.00321

Measured 9d ago against content hash c98f91f4c1ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

interview-me 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 9d 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.

Origin

This is a copy

94% identical to interview-me — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

packages/eng-disciplines/.pi/skills/interview-me/SKILL.md · 226 lines

How it starts

The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Interview Me

Overview

What people ask for and what they actually want are different things. They ask for "a dashboard" because that's what one asks for, not because a dashboard solves their problem. They say "make it faster" without a number to hit.

The cheapest moment to find this gap is before any plan, spec, or code exists. Once you've started building, switching costs are real, and the user will rationalize the wrong thing into a "good enough" thing. The misfit gets locked in.

This skill closes the gap before it costs anything. The other Define-phase skills assume you already know roughly what you want: idea-refine generates variations from an idea, spec-driven-development writes the requirements down, doubt-driven-development stress-tests a plan after you've drafted one. Interview-me is the part before all of those, where you ask one question at a time, with your best guess attached, until you can predict what the user is going to say before they say it.

When to Use

Apply this skill when:

  • The ask is missing at least one of: who the user is, why they want it, what success looks like, what the binding constraint is
  • The request is conventional rather than specific ("build me X", "make it faster") and you can't unpack the convention without guessing
  • You're tempted to start with assumptions you haven't surfaced
  • The user hasn't said which value they're optimizing for when two reasonable ones are in tension (simplicity vs. flexibility, cost vs. speed)
  • The user explicitly invokes: "interview me", "grill me", "before we start, are we sure?", "stress-test my thinking"

When NOT to use:

  • The ask is unambiguous and self-contained ("rename this variable", "fix this typo")
  • The user has explicitly asked for speed over verification
  • Pure information requests ("how does X work?", "what does this code do?")
  • Mechanical operations (renames, formats, file moves)
  • You already have ≥95% confidence; re-read the stop condition below before assuming you don't

Read the full file on GitHub · 226 lines

Changes

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.

  1. 9d ago First seen · 226 lines · 90 tokens per session scan A c98f91f4c1ca

Subscribe to this mod's changes

interview-me is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (278 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 3,212 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to interview-me, differing in 2 lines, and is treated as a copy.