Grilling
pietheinstrengholt/rssmonster
Grill the user relentlessly about a plan, decision, or idea.
Calibrated grilling session for stress-testing a plan, design, idea, or decision.
Install Grill Me
$ npx skills add JuliusBrussee/skills --skill grill-me -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JuliusBrussee/skills grill-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/JuliusBrussee/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/grill-me .claude/skills/grill-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 "grill-me" agent skill from https://github.com/JuliusBrussee/skills/tree/main/skills/grill-me into .claude/skills/grill-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grill-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/JuliusBrussee/skills/tree/main/skills/grill-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 JuliusBrussee/skills --skill grill-me -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JuliusBrussee/skills grill-me --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JuliusBrussee/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/grill-me .agents/skills/grill-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 "grill-me" agent skill from https://github.com/JuliusBrussee/skills/tree/main/skills/grill-me into .agents/skills/grill-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grill-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 JuliusBrussee/skills --skill grill-me -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JuliusBrussee/skills grill-me --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JuliusBrussee/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/grill-me .cursor/skills/grill-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 "grill-me" agent skill from https://github.com/JuliusBrussee/skills/tree/main/skills/grill-me into .cursor/skills/grill-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grill-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/JuliusBrussee/skills.git --path skills/grill-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 JuliusBrussee/skills --skill grill-me -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JuliusBrussee/skills grill-me --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JuliusBrussee/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/grill-me .gemini/skills/grill-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 "grill-me" agent skill from https://github.com/JuliusBrussee/skills/tree/main/skills/grill-me into .gemini/skills/grill-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grill-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 JuliusBrussee/skills grill-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 JuliusBrussee/skills --skill grill-me -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JuliusBrussee/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/grill-me .github/skills/grill-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 "grill-me" agent skill from https://github.com/JuliusBrussee/skills/tree/main/skills/grill-me into .github/skills/grill-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grill-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 JuliusBrussee/skills --skill grill-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 JuliusBrussee/skills grill-me --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JuliusBrussee/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/grill-me .opencode/skills/grill-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 "grill-me" agent skill from https://github.com/JuliusBrussee/skills/tree/main/skills/grill-me into .opencode/skills/grill-me/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grill-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
grill-me- GitHub stars
- 162
- Token cost
- ~1.6k tokens
- SKILL.md length
- 873 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Calibrated grilling session for stress-testing a plan, design, idea, or decision.
- Works in 4 steps: Frame The Target → Calibration → Build The Decision Map → …
- User says grill me
- SKILL.md covers Core Rules, Phase 1: Frame The Target, Phase 2: Calibration and Phase 3: Build The Decision Map, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Grill Me is an agent skill from JuliusBrussee/skills. Calibrated grilling session for stress-testing a plan, design, idea, or decision. First assesses the user's topic knowledge, confidence, and desired pressure level, then asks one question at a time with recommended answers. Use when user says "grill me", "stress-test this", "challenge my plan", "interview me", or wants a plan probed without being overwhelmed.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Requirements gathering and Load testing. The licence is MIT.
When your agent uses it
- User says grill me
- Stress-test this
- Challenge my plan
- Wants a plan probed without being overwhelmed
Example prompts
- “grill me”
- “stress-test this”
- “challenge my plan”
- “/grill-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 8470b26. 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
Grill Me loads about 1.6k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 873 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 JuliusBrussee/skills at commit 8470b26, republished under its MIT licence (© JuliusBrussee). 873 words, ~1,620 tokens.
Download SKILL.mdSave it as
.claude/skills/grill-me/SKILL.md (or your agent's skills folder).- name
- grill-me
- description
- Calibrated grilling session for stress-testing a plan, design, idea, or decision. First assesses the user's topic knowledge, confidence, and desired pressure level, then asks one question at a time with recommended answers. Use when user says "grill me", "stress-test this", "challenge my plan", "interview me", or wants a plan probed without being overwhelmed.
Grill Me
Interview the user until the plan is clear, defensible, and ready for action.
This is not hostile debate. It is calibrated pressure. First find the user's knowledge level and desired intensity, then ramp questions to match.
Core Rules
- Ask one question at a time.
- Give a recommended answer for every question.
- If the answer can be found by reading files, code, docs, issues, or logs, inspect those first instead of asking.
- Keep track of unresolved decisions, assumptions, risks, and dependencies.
- Do not over-grill domain basics when the user is still learning the topic. Teach the missing frame briefly, then ask the next useful question.
- Do not under-grill confident experts. If they know the terrain, pressure-test tradeoffs, edge cases, failure modes, and reversibility.
- Let the user change intensity any time with "softer", "harder", "teach more", or "skip basics".
Phase 1: Frame The Target
Identify what should be grilled before asking about comfort. If the topic is not clear, ask:
What plan, design, or decision should I grill?
Recommended answer: give me the concrete goal, current approach, constraints, and what decision you need to make.
If context already contains the plan, summarize it in 3-6 bullets and ask for correction:
I think target is: [...]
Recommended answer: "Yes, grill that" or "Adjust: ..."
Phase 2: Calibration
Before grilling the topic, ask a short calibration question unless the user's level is already obvious from context.
Ask:
Before I grill the plan: what is your current comfort with this topic, and how hard do you want the pressure?
Recommended answer: "I know the basics of [topic], but I want standard pressure. Explain missing concepts briefly, then keep pushing."
Use the user's answer to set two dials:
Knowledge Level
- New - user lacks core vocabulary or model of the domain.
- Working - user understands basics and can discuss tradeoffs.
- Expert - user knows domain deeply and wants sharper critique.
Pressure Level
- Light - clarify goals, constraints, and missing context.
- Standard - challenge assumptions, tradeoffs, and execution path.
- Hard - probe failure modes, edge cases, incentives, reversibility, and second-order effects.
If the user does not answer calibration, default to:
- Knowledge: Working
- Pressure: Standard
Phase 3: Build The Decision Map
Create a private decision map while asking questions one at a time:
- Goal - what success means.
- User or customer - who this affects.
- Constraints - time, money, stack, team, policy, risk.
- Options - obvious alternatives and why current option wins.
- Dependencies - what must be true first.
- Risks - what breaks, gets expensive, or becomes irreversible.
- Validation - how user will know it worked.
- Rollback - how to undo or recover.
Do not dump the full map unless user asks. Use it to choose the next question.
Phase 4: Question Ladder
Move through this ladder. Stop early if the plan becomes clear enough or user asks to stop.
1. Goal Fit
Questions:
- What outcome matters most?
- What would make this not worth doing?
- What problem are we solving, and for whom?
2. Constraint Reality
Questions:
- What hard constraint cannot move?
- What resource bottleneck decides the plan?
- What assumption would kill the plan if false?
3. Option Pressure
Questions:
- What are the top two alternatives?
- Why this approach over the boring one?
- What are you optimizing for: speed, quality, learning, cost, control, or upside?
Show full SKILL.md (340 more words)Show less
4. Execution Path
Questions:
- What is the smallest useful version?
- What has to happen first?
- What can be deferred without harming the goal?
5. Failure Modes
Questions:
- How does this fail in production or real use?
- What edge case would embarrass the plan?
- What part is hardest to observe once it breaks?
6. Validation
Questions:
- What test, metric, screenshot, demo, or user behavior proves this works?
- What would you check before trusting it?
- What does done mean in observable terms?
7. Reversibility
Questions:
- What decision here is hardest to undo?
- What backup, migration, rollback, or escape hatch exists?
- What should be logged as an ADR or explicit tradeoff?
Pressure Adaptation
If Knowledge Is New
- Define one missing concept in 2-4 sentences before asking.
- Avoid jargon unless you define it.
- Ask fewer branching questions.
- Focus on goals, constraints, and first principles.
- Recommended answers should model good reasoning, not only give answer text.
If Knowledge Is Working
- Ask normal tradeoff questions.
- Surface alternatives.
- Push for validation and smallest useful version.
- Challenge vague words like "simple", "scalable", "good", "clean", or "fast".
If Knowledge Is Expert
- Skip basics.
- Ask sharper counterfactuals.
- Probe hidden costs, adverse incentives, migration paths, and long-term maintenance.
- Ask what evidence would change their mind.
If Pressure Is Light
- Keep questions clarifying.
- Use supportive framing.
- Stop after top ambiguities are resolved.
If Pressure Is Standard
- Challenge assumptions and tradeoffs.
- Keep moving until implementation path is concrete.
If Pressure Is Hard
- Be direct.
- Name weak reasoning.
- Ask about unpleasant edge cases.
- Demand observable validation.
- Still ask one question at a time.
Recommended Answer Format
Every question includes:
Question: ...
Recommended answer: ...
Why it matters: ...Keep "Why it matters" to one sentence.
When To Stop
Stop grilling when one of these is true:
- User says stop.
- Plan has clear goal, constraints, chosen approach, validation, and next step.
- Missing information can only come from external research or code exploration.
- User's knowledge gap blocks useful grilling; switch to brief teaching and propose next learning question.
End with:
- Final decision or current best plan.
- Remaining open questions.
- Next concrete action.
- Risks to watch.
© JuliusBrussee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/grill-me of JuliusBrussee/skills.
Open the folder on GitHubat commit 8470b26
Compare with similar skills
Grill 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 |
|---|---|---|---|---|---|---|
| Grill Me this skillJuliusBrussee/skills | 162 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Grillingpietheinstrengholt/rssmonster | 564 | 31 repos | ~510 | Automated safety check: Pass | MIT | |
| Grill Menateherkai/AIS-OS | 1.6k | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Grill MeEffect-TS/effect-smol | 782 | 1 repos | ~504 | Automated safety check: Pass | MIT | |
| Grill Mesanity-io/sanity | 6.4k | 39 repos | ~151 | Automated safety check: Pass | MIT | |
| Deep Divebyungjunjang/jangpm-meta-skills | 120 | — | ~2.5k | Automated safety check: Pass | None |
Similar skills
Grill Me
nateherkai/AIS-OS
Interview the user relentlessly about a plan, design, or topic, checkpointing every answer to a brainstorm file so nothing is lost.
Grill Me
Effect-TS/effect-smol
Interview the user about a plan or design until reaching shared understanding, resolving each branch of the decision tree.
- Official
Grill Me
sanity-io/sanity
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree.
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.
More from JuliusBrussee/skills
Context Canary
JuliusBrussee/skills
Install a per-turn canary signal (e.g. An agent skill from JuliusBrussee/skills.
Junior To Senior
JuliusBrussee/skills
Adversarial senior-engineer review for agent-generated plans, designs, and architectures.
Interface Kit
JuliusBrussee/skills
Authoritative guide for implementing stunning, accessible, performant UI.
Loop Factory
JuliusBrussee/skills
Run a spec-driven agent loop where coding tasks live as markdown specs that move through inbox → active → archive, get implemented by Claude Code or Codex, and pass a review gate before they count…
Deslopify
JuliusBrussee/skills
De-slop pass for any text. An agent skill from JuliusBrussee/skills.
Related
Categories
Questions about Grill Me
What does Grill Me do?
Calibrated grilling session for stress-testing a plan, design, idea, or decision. Grill Me is an agent skill from JuliusBrussee/skills. Calibrated grilling session for stress-testing a plan, design, idea, or decision.
When should I use Grill Me?
Grill Me fits situations like: user says grill me; stress-test this; challenge my plan; wants a plan probed without being overwhelmed.
How do I install Grill Me in Claude Code?
Run `npx skills add JuliusBrussee/skills --skill grill-me -a claude-code`. Or copy the skill folder (skills/grill-me in JuliusBrussee/skills) into .claude/skills/grill-me in your project. Claude Code loads it when a task matches its description.
How do I install Grill Me in Codex?
Run `npx skills add JuliusBrussee/skills --skill grill-me -a codex`. Or copy the skill folder (skills/grill-me in JuliusBrussee/skills) into .agents/skills/grill-me in your project. Codex loads it when a task matches its description.
Can I use Grill 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 JuliusBrussee/skills --skill grill-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/grill-me, .gemini/skills/grill-me, .github/skills/grill-me and .opencode/skills/grill-me in your project.
What does Grill Me need to run?
SKILL.md names no scripts, command-line tools or credentials: Grill Me is instructions for the agent only.
Does Grill 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 Grill 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 Grill Me use?
Grill Me is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Grill Me use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Grill Me?
Skills that share tags, products or a category with Grill Me: Grilling (pietheinstrengholt/rssmonster, 564 stars), Grill Me (nateherkai/AIS-OS, 1.6k stars), Grill Me (Effect-TS/effect-smol, 782 stars) and Grill Me (sanity-io/sanity, 6.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Grill Me?
JuliusBrussee (a GitHub user) maintains it in JuliusBrussee/skills, which has 162 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on August 7, 2026.
Source: JuliusBrussee/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.