grilling
mattpocock/skills · Agent Skill
Relentlessly questions the user about their ideas, plans, or decisions to stress-test their thinking and achieve a deeper understanding.
Jump to install ↓Overview
| Publisher |  mattpocockCommunity |
|---|---|
| Repository | mattpocock/skills ↗ |
| Skill folder | grilling |
| Stars | 256,360 |
| Bundled files | 1 |
| License | MIT |
| Last updated | August 19, 2026 |
| Links | Skill source ↗ · Repository ↗ |
Mozgi check
What we found in the skill files. Details come with a subscription.
Installation
A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.
Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.
Install the “grilling” skill from mozgi.io (https://mozgi.io/skills/grilling/) for me. 1. Download the archive: https://mozgi.io/skills/grilling/download If it fails, take the skill folder from the source: https://github.com/mattpocock/skills/tree/main/skills/productivity/grilling 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “grilling” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/grilling/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills mkdir -p .claude/skills cp -r /tmp/skills/skills/productivity/grilling .claude/skills/grilling
Restart Claude Code — the skill appears in the list; call it manually with /grilling. For all projects use ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills mkdir -p .agents/skills cp -r /tmp/skills/skills/productivity/grilling .agents/skills/grilling
Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $grilling. For all projects use ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills mkdir -p .cursor/skills cp -r /tmp/skills/skills/productivity/grilling .cursor/skills/grilling
Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills mkdir -p .gemini/skills cp -r /tmp/skills/skills/productivity/grilling .gemini/skills/grilling
Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.
Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.
SKILL.md contents
Original author text · read-onlyInterview 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>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.
Frequently asked questions
What does the grilling skill do?
Relentlessly questions the user about their ideas, plans, or decisions to stress-test their thinking and achieve a deeper understanding.
How do I install grilling?
Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.
Which AI models work with grilling?
Skills are plain Markdown instructions (the Agent Skills format), so grilling works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.
Is grilling free?
The skill is published openly by mattpocock under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.
Is it safe to install skills?
A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.
How is a skill different from an MCP server or a plugin?
An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.
Related skills
All skills →teach
Teaches the user new skills and concepts within the workspace, saving progress.
mattpocock256k
ask-matt
Helps select the appropriate skill or flow for your task, acting as a router for available tools.
mattpocock256k
browser-automation
Automates web page control, including complex scenarios, login checks, tab management, and error handling.
openclaw390k
skill-creator
Creates, edits, and validates SKILL.md files for AI agents, structuring them and preparing them for use.
openclaw389k
subagent-driven-development
A development methodology where an agent delegates tasks to specialized sub-agents with isolated context, ensuring high code quality, automated result verification, and continuous plan execution without human intervention.
obra303k
using-superpowers
This skill helps the agent find and use other skills, requiring their invocation before any response or action.
obra283k