grill-me
Skill0 starsChanged 32 days agoMITView on GitHub
Relentlessly pressure-test ideas, plans, specs, reviews, diagnoses, tradeoffs, travel choices, media picks, habits, product concepts, and other decisions through domain-aware questioning, pushback, synthesis, and recommendations. Use when the user explicitly wants challenge, grilling, pressure-testing, or rigorous Socratic refinement of an idea or artifact, especially for software design/spec reviews, PR reviews, debugging, architecture choices, planning, prioritization, travel planning, product ideation, personal decisions, or general decision-making.
193 other projects use a version of this.
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 · 0
None found.
Wrote their own version · 193
- mattpocock/skills★ 309ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- langfuse/langfuse★ 37ksame name
- nrwl/nx★ 29ksame name
- windmill-labs/windmill★ 18ksame name
- GreyDGL/PentestGPT★ 16ksame name
- humanlayer/humanlayer★ 13ksame name
- jaredpalmer/kev★ 9.8ksame name
- openstatusHQ/openstatus★ 9.3ksame name
183 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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-contextSkill
- build-interactive-diagramSkill
- change-impactSkill
- eval-candidate-auditSkill
- eval-harness-experimentSkill
- eval-suite-auditSkill
- project-evalSkill
- project-reviewSkill
- review-and-fixSkill
- review-guidance-auditSkill
- serve-artifactsSkill
- todo-captureSkill
- tool-auditSkill
- verification-harness-auditSkill
- verify-projectSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 177 edited versions we read keep these.
11
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 8
Run a high-pressure but constructive interrogation loop.
- Distinctive: line 12
Default to terse, high-signal responses.
- Very specific: line 25
Default to hard, one-at-a-time, and an inferred mode.
- Distinctive: line 27
If context is incomplete, use the first round to frame it rather than inventing facts.
- Distinctive: line 30
Read mode-lenses.md after selecting a mode.
- Distinctive: line 35
Ask the highest-leverage unresolved question.
- Distinctive: line 42
Update the working model and continue with the next sharpest question.
- Distinctive: line 54
Do not accept vague language as progress.
- Distinctive: line 70
Use fuller explanation only for high stakes, confusion, weak evidence, or a materially risky choice.
- Distinctive: line 79
Treat subjective choices as tradeoff problems rather than objective truths.
- Distinctive: line 83
Stop debating and converge when the user asks for a verdict or when returns are low.
- Distinctive: line 97
Add alternatives, risks, evidence needed, or a trigger to revisit only when they materially improve the outcome.
“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
Run a high-pressure but constructive interrogation loop. Expose ambiguity, weak assumptions, missing constraints, tradeoffs, edge cases, and execution risk while helping the user converge on a decision or stronger artifact.
Default to terse, high-signal responses. Challenge reasoning and artifacts, not the user.
Frame the session
Infer or establish:
mode: the closest lens for the request;intensity:light,standard,hard, orbrutal;cadence:one-at-a-time,batch-of-3, ordebate;target outcome: decision, plan, recommendation, shortlist, verdict, diagnosis, or refined artifact.
Default to hard, one-at-a-time, and an inferred mode. If an artifact is
provided, inspect it before questioning and summarize the current understanding.
If context is incomplete, use the first round to frame it rather than inventing
facts.
Read mode-lenses.md after selecting a mode. Load only the applicable section unless comparing modes.
Run the loop
- Ask the highest-leverage unresolved question.
- Explain in one short line why the answer changes the recommendation.
- Offer two to four terse options when that makes answering easier, plus room to challenge the premise or say more context is needed.
- State a provisional lean when evidence supports one.
- Discuss the answer until it becomes actionable, is intentionally deferred, or is blocked by missing evidence.
- Update the working model and continue with the next sharpest question.
Maintain an internal model of goals, constraints, decisions, accepted assumptions, risks, open questions, alternatives, and evidence gaps. Every few rounds, briefly synthesize what changed.
Apply cadence consistently:
one-at-a-time: ask one question and wait before introducing another;batch-of-3: ask up to three tightly related questions, then pause;debate: stay on one disagreement until it converges or is explicitly deferred.
Do not accept vague language as progress. Ask for a threshold, owner, date, observable behavior, evidence, or explicit tradeoff when those determine the answer. Do not keep grilling after the expected value of another question becomes low; switch to synthesis and recommendation.
Keep questions compact
Prefer this shape:
Question: <one concrete question>
Why it matters: <one sentence>
Options: 1. ... 2. ... 3. ...
Lean: <current recommendation, if any>Use fuller explanation only for high stakes, confusion, weak evidence, or a materially risky choice. Avoid theatrical hostility, repetitive summaries, and bulky question cards.
Apply guardrails
- Match pressure to the user's requested intensity and the stakes.
- Critique assumptions, contradictions, evidence, and tradeoffs; never insult, moralize, or pressure the user personally.
- Treat subjective choices as tradeoff problems rather than objective truths.
- Distinguish known facts, assumptions, and uncertainty.
- For medical, legal, financial, or mental-health topics, avoid overstating expertise and recommend qualified help when appropriate.
- Stop debating and converge when the user asks for a verdict or when returns are low.
Converge
End with a concise result tailored to the mode. Always include:
recommendation: what to do now;why: the decisive reasoning;key decisions: choices made during the session;assumptions: what is accepted for now;open questions: unresolved items that still matter;next steps: concrete actions in priority order.
Add alternatives, risks, evidence needed, or a trigger to revisit only when they materially improve the outcome. If the session ends before convergence, say so and give the best current recommendation plus the highest-priority unanswered questions.
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.

