Grill Me

Community

ericgandrade

grill-me

Relentless Socratic interview that walks down every branch of a plan or design, resolving decisions one-by-one. Trigger ONLY when the user explicitly says "grill me" or the PT equivalent "me grille". Do NOT trigger for stress-test, poke holes, devil's advocate, challenge, review, or feedback requests.

Overview

Publisher	ericgandrade
Repository	`claude-superskills`
Skill name	`grill-me`
Stars	86
Forks	16
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by ericgandrade on GitHub. Read the source before you install it.

Installation

Install the Grill Me AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ericgandrade/claude-superskills/tree/main/skills/grill-me
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/ericgandrade/claude-superskills.git /tmp/claude-superskills
mkdir -p .claude/skills
cp -r /tmp/claude-superskills/skills/grill-me .claude/skills/grill-me

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Grill Me in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Grill Me on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Grill Me is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Grill Me

Purpose

Stress-test a plan, design, or idea through relentless Socratic questioning. Walk down every branch of the decision tree, resolve dependencies between decisions one-by-one, and reach a shared understanding where no assumption is left unchallenged.

When to Use

Trigger ONLY when the user explicitly uses the word "grill" — e.g.:

"grill me on this"
"grill me on my plan / architecture / design"
"I want you to grill me before I present"
PT: "me grille sobre esse plano"

Do NOT trigger for synonyms or near-misses, even when the intent seems similar:

"stress-test this" → not grill-me
"poke holes in my plan" → not grill-me
"play devil's advocate" → not grill-me
"challenge my assumptions" → not grill-me
"pressure-test this" → not grill-me
"review this and tell me what's wrong" → not grill-me
"give me feedback" → not grill-me

Workflow

Step 0 — Understand the Subject

Read the plan, design, or idea the user has provided. If working in a codebase, explore relevant files before asking questions that can be answered by reading the code.

Step 1 — Build the Decision Tree (silent)

Before asking the first question, mentally map:

Core decisions already made (what's locked in)
Branches that are open or unresolved
Dependencies between decisions
Unstated assumptions worth surfacing

Step 2 — Interview Relentlessly

Ask one question at a time. For each question:

Ask the question
Provide your recommended answer with brief reasoning
Wait for the user's response before moving on

Work through branches systematically — exhaust one thread before opening another. When an answer reveals a new sub-question, follow it immediately.

Question types to cycle through:

Scope: What's in? What's explicitly out?
Dependencies: What does this depend on that isn't defined yet?
Failure modes: What breaks first under load / edge cases / bad inputs?
Alternatives rejected: Why this approach and not X?
Success criteria: How will you know this worked?
Reversibility: What's hard to undo? What's the rollback plan?
Ownership: Who owns each part when something goes wrong?

Step 3 — Resolve and Close

When all branches of the decision tree are resolved, summarize:

Decisions confirmed
Decisions changed or refined
Open questions that remain (if any)
Risks surfaced that need a mitigation plan

Critical Rules

NEVER ask more than one question per turn
ALWAYS provide your recommended answer alongside the question
If a question can be answered by exploring the codebase, explore it instead of asking
Follow threads to completion before opening new ones
Push back on weak reasoning — don't accept "it should be fine" as an answer
Surface assumptions the user didn't state but is implicitly relying on

Example Usage

"Grill me on my microservices migration plan"
"I want to stress-test this database schema before we build on it — grill me"
"We're about to kick off this project. Grill me on the architecture."
"I have a go-to-market plan. Pick it apart."
"Grill me on this carve-out strategy before I write the plan"

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

evals/trigger-eval.json2 KB

Frequently asked questions

What does the Grill Me AI skill do?

Why use Grill Me on TypingMind?

Because you install it once and use it with any model. Grill Me is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Grill Me in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ericgandrade/claude-superskills/tree/main/skills/grill-me. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Grill Me?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Grill Me?

As many as you like. As long as a model supports skills, you can use Grill Me with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Grill Me AI skill free?

Yes. It is published on GitHub by ericgandrade under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Pokemon Player

NousResearch

OrganizationPopular

Play Pokemon via headless emulator + RAM reads.

Docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document',…

Openclaw Docker E2e Authoring

openclaw

OrganizationPopular

Author OpenClaw Docker E2E and live provider Docker lanes.

Openclaw Parallels Smoke

openclaw

OrganizationPopular

Prepare, snapshot, run, rerun, debug, or interpret OpenClaw Parallels guest install, onboarding, gateway smoke, and upgrade checks across macOS, Windows, and Linux.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Grill Me

Purpose

When to Use

Workflow

Step 0 — Understand the Subject

Step 1 — Build the Decision Tree (silent)

Step 2 — Interview Relentlessly

Step 3 — Resolve and Close

Critical Rules

Example Usage

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now