interrogatoire
Skill2 starsChanged 26 days agoMITView on GitHub
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, uses any 'grill' trigger phrases, or French ones such as 'cuisine-moi', 'interroge-moi', 'challenge mon idée'.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Darius-Tokam/superSkillword for word, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- Darius-Tokam/superSkill★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- anti-blablaSkill
- cuisine-moiSkill
- souffleurSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Before the first round, call the Skill tool with "anti-blabla".
- Distinctive: line 14
Ask each round through your harness's question tool: the built-in tool that puts multiple-choice questions in front of the user and returns …
- Distinctive: line 30
Cap: ask as many frontier questions as the tool accepts per call, 4 when its limit is unknown or uncapped.
- Distinctive: line 39
When the harness has no question tool, or the tool refuses the call (Codex outside Plan mode, a non-interactive run), ask the whole …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interview the user relentlessly until you reach a shared understanding. Map this as a design tree: every decision branches into the decisions that hang off it.
Work the tree in rounds. The frontier is every decision whose prerequisites are already settled: the questions you can ask now without guessing at answers you haven't heard yet. Each round puts the frontier to the user, every question carrying your recommended answer. Then wait for the user's answers before the next round.
Before the first round, call the Skill tool with "anti-blabla". Write every question, option, and description by its rules.
Asking a round
Ask each round through your harness's question tool: the built-in tool that puts multiple-choice questions in front of the user and returns their picks. Known names, verified 2026-10-20:
| Harness | Question tool | Questions per call | Options per question |
| Claude Code, Claude Agent SDK | AskUserQuestion | 4 | 2-4 |
| Gemini CLI | ask_user | 4 | 2-4 |
| Codex CLI (Plan mode) | request_user_input | 3 | 2-3 |
| OpenCode | question | uncapped | uncapped |
| VS Code Copilot | vscode_askQuestions | uncapped | uncapped |
| Copilot CLI | ask_user | unknown | unknown |
| Cursor | AskQuestion | unknown | unknown |
Any other tool with the same job counts as your question tool.
One round is one call:
- Cap: ask as many frontier questions as the tool accepts per call, 4 when its limit is unknown or uncapped. When the frontier is wider, ask first the questions whose answers unblock the most of the tree; the rest wait for the next round.
- Recommendation: your recommended answer is the first option, its label ending in "(Recommended)", its description saying why.
- Options: mutually exclusive, within the tool's option limit. The user reaches any other answer through the tool's free-text choice. Turn on multi-select only for choices that combine.
- Header: 12 characters at most.
Some free-text answers are a question back or a doubt. Answer it, then put the question again in the next round.
Without a question tool
When the harness has no question tool, or the tool refuses the call (Codex outside Plan mode, a non-interactive run), ask the whole frontier as text. Number each question and give your recommended answer:
❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>
---
❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>Word each question so "yes" accepts your recommended answer.
Between rounds
Each round the user answers reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a later round, not this one.
Finding facts is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent with a fresh context window to find it; don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report; ask the rest of the frontier now. The decisions are the user's: put each to them and wait.
The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.