grilling
Skill0 starsChanged 5 days agoMITView on GitHub
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
195 other projects use a version of this, 141 of them edited.
Adopted by
Most recently taken up by
- bamlab/flashlightedited, first seen Nov 16, 2026
- bmcszk/agent-skillsedited, first seen Nov 16, 2026
- devdeepjs/kobayashi-maruedited, first seen Nov 16, 2026
- gaoyuan98/dameng-skillstheir own version, first seen Nov 16, 2026
- lhotwll217/owner-operatoredited, first seen Nov 16, 2026
- Lixiuxiu559/AgentForgetheir own version, first seen Nov 16, 2026
Used with
Projects with it also use capture-learning-tools, design-frontend-dev and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
The-Vibe-CompanySkillcapture-learning-tools
Turn technical conversations, bugs, CI failures, review comments,
Also in 5 projects that use this
The-Vibe-CompanySkilldesign-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to
Also in 5 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 58 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 42 projects that use this
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 8 projects that use this
AWSSkillwizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
Also in 136 projects that use this
- +3 more from The-Vibe-Company
Other versions195 projects use a version of this.
Word for word · 1
- lutzseverino/repo-canon★ 1100% same
Edited · 141
- mattpocock/skills★ 325k74% same
- The-Vibe-Company/quivr★ 40k26% same
- QuivrHQ/quivr★ 40k26% same
- windmill-labs/windmill★ 19k75% same
- formbricks/formbricks★ 13k76% same
- ArcReel/ArcReel★ 6.6k76% same
- pollinations/pollinations★ 5.3k76% same
- withcoral/coral★ 5k74% same
- bestofjs/bestofjs★ 3.1k75% same
- The-Vibe-Company/claude-code-controller★ 2.4k26% same
131 more not listed
Wrote their own version · 53
- GreyDGL/PentestGPT★ 16ksame name
- PX4/PX4-Autopilot★ 13ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- AUTO-MAS-Project/AUTO-MAS★ 774same name
- devcxl/mattpocock-skills-zh★ 543same name
- Tiberriver256/mcp-server-azure-devops★ 401same name
- ninehills/skills★ 280same name
- heyongjun666/AICU-Graph★ 200same name
- opencrvs/opencrvs-core★ 122same name
- GulajavaMinistudio/awesome-copilot-id★ 92same name
43 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- babysitSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- factorySkill
- grill-with-docsSkill
- implementSkill
- improve-codebase-architectureSkill
- prototypeSkill
- prSkill
- repository-standardsSkill
- researchSkill
- reviewSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wayfinderSkill
- writing-for-agentsSkill
- adopt-repository-standardsSkill
- author-standardsSkill
- repository-standardsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 72 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the contribution guide's Triage inference test and owner-question route before adding a question to the frontier.
- Distinctive: line 42
Only when the guide is missing, use this inference boundary: cite the owner's approved goal, a recorded decision or wish, or the owner's …
“Common” is measured: kept by at least 6 in 10 of the 72 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
A prompt or brief naming this skill is its invocation.
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.
Read the contribution guide's Triage inference test and owner-question route before adding a question to the frontier. Reuse recorded answers with their dated sources, record qualifying inferences in the guide's named list, and investigate missing facts. When the guide is missing, use the fallback below.
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 frontier in rounds: number each question and give your recommended answer. Keep each round short: when the frontier holds more questions than the user can weigh at once, ask the ones that unblock the most and leave the rest for the next round. 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. Put the decisions the inference test leaves open to the user and wait for their answers.
The interview is done when the frontier is empty: each decision is recorded or listed as a qualifying inference, with no required owner answer missing under the guide's Triage rules. Reuse recorded approval. A composite skill can then continue to its publication step.
Without a contribution guide
Only when the guide is missing, use this inference boundary: cite the owner's approved goal, a recorded decision or wish, or the owner's quoted words, each with its date. Keep an inference reversible within the approved goal and scope; it adds no public name or breaking policy and chooses no persistent default, limit, timeout or fallback. List qualifying answers under Inferred, listed for the owner, with dated sources and owner veto. Ask the user directly about one-way doors and unchosen values, including every choice failing that test. Retain the owner's grill answers and plan approval as gates.
Reads
CONTRIBUTING.md, relative to the repository root: the Triage inference test and owner-question route. If missing, use Without a contribution guide.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

