Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mattpocock/grilling
Grill the user relentlessly about a plan, decision, or idea.
Passed 18 of 22 test cases with the skill, and 18 of 22 without it.
and 1 more in the full report
4 fixed14 passed either way0 still failing4 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to design a new CLI tool for internal database backups. Please run an intensive Q&A session with me to map out all requirements and choices. Group active questions by logical rounds, include a recommended option for each, and gather any codebase details yourself instead of asking me for structural facts.
| Checked | Without skill | With skill |
|---|---|---|
| The response limits active questions to the initial unblocked round. | Passed | Passed |
| Every question is phrased so that a 'yes' answer confirms the recommended option. | Missed | Passed |
| The response provides a concrete recommended choice for every question presented. | Passed | Passed |
The instructions your model reads when the skill loads.
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. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round.
Format a round like so:
❓ **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.
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 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.
test cases passed, vs 18 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.