Grilling
pietheinstrengholt/rssmonster
Grill the user relentlessly about a plan, decision, or idea.
Clarify a standalone idea or check assumptions before feature or fix planning.
Install Interview Me
$ npx skills add kdlbs/kandev --skill interview-me -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kdlbs/kandev interview-me --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kdlbs/kandev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/interview-me .claude/skills/interview-me && rm -rf skills-srcUse ~/.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/
Install the "interview-me" agent skill from https://github.com/kdlbs/kandev/tree/main/.agents/skills/interview-me into .claude/skills/interview-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interview-me", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kdlbs/kandev/tree/main/.agents/skills/interview-meType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kdlbs/kandev --skill interview-me -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kdlbs/kandev interview-me --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kdlbs/kandev.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/interview-me .agents/skills/interview-me && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "interview-me" agent skill from https://github.com/kdlbs/kandev/tree/main/.agents/skills/interview-me into .agents/skills/interview-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interview-me", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kdlbs/kandev --skill interview-me -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kdlbs/kandev interview-me --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kdlbs/kandev.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/interview-me .cursor/skills/interview-me && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "interview-me" agent skill from https://github.com/kdlbs/kandev/tree/main/.agents/skills/interview-me into .cursor/skills/interview-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interview-me", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kdlbs/kandev.git --path .agents/skills/interview-me--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kdlbs/kandev --skill interview-me -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kdlbs/kandev interview-me --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kdlbs/kandev.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/interview-me .gemini/skills/interview-me && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "interview-me" agent skill from https://github.com/kdlbs/kandev/tree/main/.agents/skills/interview-me into .gemini/skills/interview-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interview-me", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kdlbs/kandev interview-meInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kdlbs/kandev --skill interview-me -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kdlbs/kandev.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/interview-me .github/skills/interview-me && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "interview-me" agent skill from https://github.com/kdlbs/kandev/tree/main/.agents/skills/interview-me into .github/skills/interview-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interview-me", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kdlbs/kandev --skill interview-me -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kdlbs/kandev interview-me --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kdlbs/kandev.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/interview-me .opencode/skills/interview-me && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "interview-me" agent skill from https://github.com/kdlbs/kandev/tree/main/.agents/skills/interview-me into .opencode/skills/interview-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interview-me", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
interview-me- GitHub stars
- 909
- Token cost
- ~1.4k tokens
- SKILL.md length
- 788 words
- Files
- 2 (incl. references)
- Skills in repo
- 45
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Clarify a standalone idea or check assumptions before feature or fix planning.
- Works in 4 steps: Check assumptions → Ask questions in dependency order → Stress-test the answers → …
- Tasks that involve Requirements gathering
- SKILL.md covers 1. Check assumptions, 2. Ask questions in dependency…, 3. Stress-test the answers and 4. Capture decisions and…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Interview Me is an agent skill from kdlbs/kandev. Clarify a standalone idea or check assumptions before feature or fix planning. Use focused questions, stress-test intent, and map unresolved decisions for large uncertain initiatives.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/decision-mapping.md`).
It sits in Agent Workflows, covering Requirements gathering and Load testing. The repository describes itself as: AI Kanban & Development Environment. Orchestrate multiple agents, review changes, open PRs. Multi-provider, self-hostable, no telemetry. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve Requirements gathering
- Tasks that involve Load testing
Example prompts
- “/interview-me”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b734113. 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.4k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 49 tokens; SKILL.md has 788 words of instructions outside code blocks.
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 kdlbs/kandev at commit b734113, republished under its AGPL-3.0 licence (© kdlbs). 788 words, ~1,431 tokens.
Download SKILL.mdSave it as
.claude/skills/interview-me/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- interview-me
- description
- Clarify a standalone idea or check assumptions before feature or fix planning. Use focused questions, stress-test intent, and map unresolved decisions for large uncertain initiatives.
Interview Me
Run the assumption check before requirements, system designs, or implementation plans. Reuse settled answers throughout the design package. An assumption check does not require an interview when the material choices are already clear.
For a standalone interview or stress test, clarify intent without automatically creating a design package. Skip this workflow for mechanical edits and pure information requests.
1. Check assumptions
Read the request, relevant specifications, source, and tests. Separate:
- Confirmed: the user explicitly requested or previously settled it.
- Verified: source, tests, or documentation establish a fact. Keep its source reference and distinguish current behavior from intended behavior.
- Unresolved: a choice or missing fact can change behavior, scope, ownership, permissions, persistence, compatibility, or acceptance criteria.
State the intended outcome and material unresolved assumptions briefly. Do not invent confidence percentages. Investigate facts that available tools can resolve before asking the user. Evidence of current behavior is not user agreement to preserve it.
Ask about consequential choices that evidence cannot settle. Choose routine, reversible implementation details within the agreed scope. A request for speed reduces questions; it does not make an unanswered material choice confirmed.
For a clear regression, use the active acceptance criterion without asking the user to define the behavior again.
2. Ask questions in dependency order
Identify which decisions depend on other answers. Ask only questions whose prerequisites are settled. Use the active harness's user-question tool and obey its limits and waiting rules. Ask one to four independent questions per round, within those limits. Without a question tool, ask one question at a time in chat during a normal interactive session.
If this is an autopilot root or another non-interactive session with no question tool, record each unresolved material choice as an assumption. Continue only when the caller permits autonomous planning for that choice and use the most conservative reversible option. Otherwise return the assumption as a blocker to the caller. Never present an assumption as confirmed, and preserve the normal chat fallback for interactive sessions.
Give each question concrete options, a recommended answer, and a short reason. Align the question with the recommendation so agreement has one clear meaning. Do not ask the user to locate code or supply facts you can investigate.
For example, first settle what "preserve task context" includes. Ask about retention duration only after the user chooses persistent context.
Wait for answers before resolving dependent choices. After each round, update the remaining questions. If an answer changes an earlier assumption, revisit the affected choices and artifacts. Do not repeat settled questions without new evidence or changed scope.
If the initiative has too many dependent unknowns to specify reliable work orders, use decision mapping. Ordinary features and clear fixes do not need a map.
Show full SKILL.md (337 more words)Show less
3. Stress-test the answers
Use concrete scenarios to expose material gaps in success, failure, recovery, and scope. Select scenarios relevant to the request; do not invent adjacent features or an exhaustive questionnaire.
Challenge vague terms such as "robust" with an observable outcome. Compare domain terms with the owning specifications and any existing glossary. If a term or claimed behavior conflicts with those sources, name the conflict and resolve it.
Distinguish uncertainty that needs evidence from a choice that needs the user. If a design question needs an experiment, define the question and observable result first. Keep prototypes temporary and separate from production changes. Record what the experiment proves and what remains undecided.
4. Capture decisions and continue
After each answer, preserve the choice and its reason in the current task notes. Use the Kandev task plan when available, preserving user edits. Do not create a separate intent document unless requested.
During authorized specification or planning work, put settled behavior in the
owning requirement and technical contracts in its system design. Use /record
for significant decisions that meet its ADR criteria. Preserve meaningful
alternatives and rationale there. Update an existing glossary when terminology
changes; do not introduce a parallel glossary by default.
Keep unresolved choices visibly unresolved. A recommendation, silence, or timeout is not confirmation. If the user explicitly delegates a choice, record the selected option as an agent decision made under that delegation.
When intent is clear and no material choice blocks the next design phase, finish the interview. This includes success criteria, constraints, and scope. Explicit answers and prior instructions count as confirmation; do not require a second approval of their restatement. If broad intent remains ambiguous, ask about the specific remaining gap before continuing.
Summarize the settled intent and exclusions. If another skill called this check,
return to its current phase without restarting specification or planning.
For a direct planning request, continue through /spec and /plan to the
existing design-package handoff. For a standalone interview, return the clarified
intent. Neither path authorizes implementation or delegation.
© kdlbs, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .agents/skills/interview-me of kdlbs/kandev.
- SKILL.md
- references/decision-mapping.md
Open the folder on GitHubat commit b734113
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Interview Me this skillkdlbs/kandev | 909 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Grillingpietheinstrengholt/rssmonster | 564 | 32 repos | ~510 | Automated safety check: Pass | MIT | |
| Deep Divebyungjunjang/jangpm-meta-skills | 121 | — | ~2.5k | Automated safety check: Pass | None | |
| Grillingopencrvs/opencrvs-core | 120 | 2 repos | ~205 | Automated safety check: Pass | Custom licence | |
| Deep Divebyungjunjang/jangpm-meta-skills | 121 | — | ~2.7k | Automated safety check: Pass | None | |
| Grillingfossasia/eventyay-interpretation | 1.6k | 6 repos | ~167 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Deep Dive
byungjunjang/jangpm-meta-skills
Socratic interview skill to deepen a spec or refine an existing agent blueprint.
Grilling
opencrvs/opencrvs-core
Grill the user relentlessly about a plan or design. An agent skill from opencrvs/opencrvs-core.
Deep Dive
byungjunjang/jangpm-meta-skills
A Codex skill for Socratic interviews that deepen a spec or refine an existing agent blueprint.
Grilling
fossasia/eventyay-interpretation
Interview the user relentlessly about a plan or design. An agent skill from fossasia/eventyay-interpretation.
Grill
koolamusic/claudefiles
Adversarial questioning and collaborative shaping in one skill.
More from kdlbs/kandev
All 45 skills in this repoPR Walkthrough
kdlbs/kandev
Generate a single-file HTML walkthrough that explains a PR's purpose, user impact, interface changes, compatibility risks, and implementation.
Debug
kdlbs/kandev
Diagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior.
Harness Improvement
kdlbs/kandev
Improve Kandev's AI harness from session learnings or explicit requests.
Diagram Design
kdlbs/kandev
Create branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel…
TDD
kdlbs/kandev
Implement changes using Test-Driven Development (Red-Green-Refactor).
Verify
kdlbs/kandev
Run a broad local verification audit only when the user explicitly requests it or PR/CI remediation requires it.
Related
Categories
Questions about Interview Me
What does Interview Me do?
Clarify a standalone idea or check assumptions before feature or fix planning. Interview Me is an agent skill from kdlbs/kandev. Clarify a standalone idea or check assumptions before feature or fix planning.
When should I use Interview Me?
Interview Me fits situations like: tasks that involve Requirements gathering; tasks that involve Load testing.
How do I install Interview Me in Claude Code?
Run `npx skills add kdlbs/kandev --skill interview-me -a claude-code`. Or copy the skill folder (.agents/skills/interview-me in kdlbs/kandev) 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 kdlbs/kandev --skill interview-me -a codex`. Or copy the skill folder (.agents/skills/interview-me in kdlbs/kandev) 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 kdlbs/kandev --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 AGPL-3.0 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.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 782 tokens, read only when the agent opens those files.
What are the alternatives to Interview Me?
Skills that share tags, products or a category with Interview Me: Grilling (pietheinstrengholt/rssmonster, 564 stars), Deep Dive (byungjunjang/jangpm-meta-skills, 121 stars), Grilling (opencrvs/opencrvs-core, 120 stars) and Deep Dive (byungjunjang/jangpm-meta-skills, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Interview Me?
kdlbs (a GitHub organization) maintains it in kdlbs/kandev, which has 909 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on October 8, 2026.
Source: kdlbs/kandev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.