grill-me
Skill0 starsChanged 16 days agoApache-2.0View on GitHub
Design-tree interview. Triggers: grill me, interview my plan, stress-test this design. NOT for implementation or one-question-at-a-time interviews.
193 other projects use a version of this, 7 of them edited.
Adopted by
Most recently taken up by
- xiaoxiaosrm/dsh-mattpocock-skillstheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- microsoft/frontier-agentic-modernization-rvastheir own version, first seen Nov 8, 2026
- The-Vibe-Company/quivrtheir own version, first seen Nov 8, 2026
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- codedb-io/codedb-lenstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use brief-to-tasks, writing-beats 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.
julianoczkowskiSkillbrief-to-tasks
Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".
Also in 7 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 66 projects that use this
simo97Skillrequest-refactor-plan
Use this skill when user wants to create a refactor plan.
Also in 43 projects that use this
simo97Skillmigrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Also in 71 projects that use this
LesaniSkillwriting-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
Also in 65 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
- +2 more from simo97
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 7
- nrwl/nx★ 29k11% same
- rtadewald/skills★ 27231% same
- sammcj/agentic-coding★ 16922% same
- MiladJoodi/skills★ 2429% same
- emiliosheinz/agent-skills★ 2016% same
- Yassimba/loom★ 919% same
- IxTechCrypto/kicad-skills★ 820% same
Wrote their own version · 186
- mattpocock/skills★ 309ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- langfuse/langfuse★ 37ksame name
- windmill-labs/windmill★ 18ksame name
- GreyDGL/PentestGPT★ 16ksame name
- humanlayer/humanlayer★ 13ksame name
- jaredpalmer/kev★ 9.8ksame name
- openstatusHQ/openstatus★ 9.3ksame name
- webiny/webiny-js★ 8ksame name
176 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 repository64 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- verify-lead-waitSkill
- verify-merge-receiptsSkill
- branded-docSkill
- explanatory-docSkill
- 1passwordSkill
- agada-benchSkill
- agent-browserSkill
- agent-routingSkill
- architectural-conformance-auditSkill
- audio-dashboardSkill
- brain-store-fallbackSkill
- claude-desktop-researchSkill
- cmux-agentsSkill
- cmuxSkill
- coachSkill
- coderabbitSkill
- codex-workflowsSkill
- collab-monitorSkill
- content-demo-creationSkill
- convention-auditSkill
- cursor-workflowsSkill
- cyberSkill
- deploy-verifySkill
- drive-filingSkill
- eas-prebuild-checkSkill
- ecosystem-healthSkill
- eli5Skill
- false-green-gateSkill
- figma-loopSkill
- fleet-wrap-gateSkill
- fleet-wrapSkill
- frustration-captureSkill
- gemini-researchSkill
- git-guardianSkill
- github-researchSkill
- golem-installSkill
- heredoc-guardSkill
- html-dashboardSkill
- human-confirm-gateSkill
- i-have-adhdSkill
- install-runbook-linterSkill
- large-planSkill
- m1-window-gateSkill
- model-pin-gateSkill
- never-fabricateSkill
- orcSkill
- plan-councilSkill
- pr-loopSkill
- qa-verdict-gateSkill
- qa-videoSkill
- repogolemSkill
- research-lifecycleSkill
- reviewer-order-gateSkill
- session-handoffSkill
- skill-creatorSkill
- stitch-designSkill
- t3-visualsSkill
- tmp-blockSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 177 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
design tree: every decision branches into the decisions that hang off it.
- Distinctive: line 29
Ask the whole frontier in one round.
- Distinctive: line 43
Do not block the whole round on that exploration.
- Distinctive: line 51
Keep labels short enough to answer by voice in one breath:
- Very specific: line 73
Read shorthand such as 1A 2C as the user's decisions.
- Distinctive: line 83
Do not act on the plan until the user explicitly confirms shared understanding.
“Common” is measured: kept by at least 6 in 10 of the 177 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
/grill-me
Ported and adapted from Matt Pocock's
skills/productivity/grilling/SKILL.mdandskills/productivity/grill-me/SKILL.mdat upstream commitc55ee46073ed923f86ce59a5eb3b6d895095d1b7. Upstream is Copyright (c) 2026 Matt Pocock and MIT licensed; see LICENSE.upstream.Local shape: the upstream
grillingbody is folded into this user-invoked skill so a one-line wrapper does not add a second always-on description to the skill roster.Deliberate local divergence from upstream: retain Etan's voice-friendly lettered options,
1A 2Cshorthand, exactly oneRecommendedlabel per question, and the final <=6 frozen bullets. A recommendation is never a default.
Interview the user relentlessly until you reach a shared understanding. Map the subject as a design tree: every decision branches into the decisions that hang off it.
Work the whole frontier
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 have not heard yet.
Ask the whole frontier in one round. Do not impose a fixed question-count cap. Number every question, give it short lettered options, and mark exactly one option Recommended with a one-line reason. Then wait for the user's answers before the next round.
Each round reshapes the tree. Fold in the user's decisions, recompute the frontier, and ask the next round. A question whose answer depends on another open question belongs to a later round, not the current one.
Find facts without blocking the round
Finding facts is your job, never the user's. Read the plan and codebase first. When a frontier question needs a fact from the filesystem, tools, or another available source, dispatch a sub-agent to find it instead of asking the user.
Do not block the whole round on that exploration. Treat the running exploration as an unsettled prerequisite: hold only its downstream questions and ask the rest of the frontier now. Fold the fact into the tree when the sub-agent reports.
Facts belong to the agent. Decisions belong to the user: put every decision to them and wait.
Round format
Keep labels short enough to answer by voice in one breath:
## Round N
1. <question title>: <question body>
A. <option>
B. <option> (Recommended: <one-line reason>)
C. <option>
---
2. <question title>: <question body>
A. <option> (Recommended: <one-line reason>)
B. <option>
C. <option>
Answer like: 1B 2A, or 1B 2: <answer outside the options>Separate every pair of questions in a round with a horizontal rule.
Read shorthand such as 1A 2C as the user's decisions. If an answer is outside the options,
take it verbatim. Never answer for him. Recommended is advice, not a default. Never treat
silence as a choice; unanswered questions remain open.
Stop only at shared understanding
The session is ready to close only when the frontier is empty: every branch of the design tree was visited and nothing remains silently assumed. Emit <=6 frozen bullets summarizing the settled decisions and the round that settled each one. Then wait.
Do not act on the plan until the user explicitly confirms shared understanding. If the user names something still open, put it back into the tree and continue.
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.

