How do I install the Grim:ep:grill Me skill?

Run npx skillmds@latest add mindgoblinstudios/grim-ep-grill-me in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Grim:ep:grill Me safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Grim:ep:grill Me?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Grim:ep:grill Me free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Grim:ep:grill Me?

MindGoblinStudios (@mindgoblinstudios) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Grim:ep:grill Me by mindgoblinstudios

Name: Grim:ep:grill Me
Author: MindGoblinStudios

Grim:ep:grill Me

Grill the user relentlessly about a plan, decision, or idea through open-ended frontier rounds with recommended answers. Use for exhaustive stress-testing; for requests that say "grill me 10" or "10 pack", use grim:ep:mx:grill-me instead.

MindGoblinStudios 2ec0eb3 5 files · 1.6 MB Updated Sep 17, 2026

File contents

Original skill: grilling (upstream renamed grill-me to grilling; the upstream grill-me is now an alias stub)

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>

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.

---name: grim-ep-grill-medescription: Grill the user relentlessly about a plan, decision, or idea through open-ended frontier rounds with recommended answers. Use for exhaustive stress-testing; for requests that say "grill me 10" or "10 pack", use grim:ep:mx:grill-me instead.---Original skill: [grilling](https://github.com/mattpocock/skills/blob/main/skills/productivity/grilling/SKILL.md) (upstream renamed `grill-me` to `grilling`; the upstream `grill-me` is now an alias stub)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>```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