agentleFS
flonatflonat/flonat-research/skills/grill-me/SKILL.md

grill-me

Skill150 starsChanged 11 days agoMITView on GitHub

Run an interactive one-question-at-a-time oral drill for research defence or active-recall study, escalating around weak answers and ending with a study sheet. Use when the user asks to be grilled, quizzed, or prepared for a viva, job talk, seminar, or exam. Not for a written critique; use $devils-advocate or a review agent.

193 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • julianoczkowskiSkill

    brief-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

  • LesaniSkill

    writing-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

  • simo97Skill

    request-refactor-plan

    Use this skill when user wants to create a refactor plan.

    Also in 43 projects that use this

  • simo97Skill

    migrate-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

  • LesaniSkill

    writing-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

  • liufeng1976Skill

    setup-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

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Auto-detect: if the target is one of the user's own artifacts (a paper-*/ dir, a proof, an atlas topic he authored) → defend.

    line 22
  2. Distinctive:

    Default run = auto-detected mode, default persona, ~10 questions, all dimensions, drill first then study sheet.

    line 51
  3. Distinctive:

    Read the target so questions are *specific*, not quiz-show generic.

    line 57
  4. Very specific:

    If nothing resolves, ask once (the available structured-question mechanism) what to grill on and at what level (e.g.

    line 62
  5. Very specific:

    Keep a running tally: dimension · verdict (solid / shaky / fumbled / wrong / dodged) · the gap.

    line 103
  6. Distinctive:

    When the drill ends:

    line 109
  7. Very specific:

    Offer to persist it: write the study sheet to reviews/<scope>/grill-me/<YYYY-MM-DD>.md (defend, scope = paper slug or _project) or …

    line 115
  8. Distinctive:

    Ground every question in the material: No generic "what's your contribution?" / "define entropy" — tie it to *their* paper or *their* …

    line 120
  9. Distinctive:

    Honest verdicts, calibrated tone: Don't flatter a thin answer.

    line 124
  10. Distinctive:

    Don't: ask ungrounded quiz-show questions they can't map to their paper/class.

    line 131

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Grill Me — Interactive Oral-Exam Drill

You answer, out loud, one grounded question at a time. This skill plays a skeptical examiner and interrogates you — escalating on weak or evasive answers — then hands you a study sheet of what you fumbled, with model answers. Two flavours: defend your own research, or study a class you're learning.

Two Modes (auto-detected; override with --defend / --study)

DefendStudy
TargetYour own paper / model / proof / research ideaA class, subject, textbook chapter, lecture notes you're learning
GoalRehearse defending your choices under pressureTest + deepen recall and understanding of the material
"Right answer"?No single right answer — you defend a choice; the examiner probes whether it holdsYes — there's an objectively correct answer; wrong answers get corrected
Default personaSkeptical-but-fair examiner (viva/referee)Examiner-Socratic (an examiner who also teaches when you miss)
Prep forViva · job talk · seminar Q&A · referee/rebuttal armourExams · comprehension checks · learning a new field

Auto-detect: if the target is one of the user's own artifacts (a paper-*/ dir, a proof, an atlas topic he authored) → defend. If it's course material / textbook / lecture notes / a subject he's revising → study. When ambiguous, ask once.

Everything below is shared; mode-specific differences are called out inline.

When to Use

  • Defend: preparing for a viva / thesis defense / job talk / seminar Q&A; building referee/rebuttal armour before submission.
  • Study: revising for an exam; checking you actually understand a class, textbook chapter, or a new field — active-recall practice, not passive re-reading.

When NOT to Use

  • You want a written critique of a paper, not a live drill → referee2-reviewer / paper-critic / review-cluster.
  • You want to stress-test an argument in prose → devils-advocate.
  • You want to draft a rebuttal to genuine venue reviews you already have → review-response / strategic-revision --external.
  • You want a passive summary of the material → just ask for one; grill-me is for being tested.

grill-me is the only one where you are the one answering. If you don't want to type answers back and forth, use one of the above.

Arguments

ArgEffect
[target]Paper dir / .tex / .pdf, a proof, an atlas topic, course notes / slides / textbook chapter, or a plain subject name. Default: auto-detect paper-*/paper in CWD.
--defend / --studyForce the mode when auto-detect would guess wrong.
--reviewer2Persona = hostile Reviewer 2 (defend mode).
--coachPersona = supportive coach — challenges but scaffolds a hint toward the answer (great for early study).
--rounds NNumber of primary questions (default 10; follow-ups don't count).
--focus <dim>Concentrate on one dimension (see the tables in Phase 1). Default: spread.

Default run = auto-detected mode, default persona, ~10 questions, all dimensions, drill first then study sheet.

Procedure

Phase 0 — Ground the material (read-only, silent)

Read the target so questions are specific, not quiz-show generic.

  • Defend: read the paper .tex/PDF (or proof/idea). Identify the headline claim, contribution list, load-bearing assumptions, identification/proof spine, positioning vs the nearest rival. Reuse existing review state — don't re-derive it: read reviews/INDEX.md + latest reviews/<scope>/* reports, the project CLAUDE.md risks, and the venue's referee-bait (docs/reference/venue-profiles/<field>.md). A logged referee objection is your sharpest question.
  • Study: read the course notes / slides / textbook chapter / syllabus provided (or, for a named subject with no file, work from the established canonical content of that subject — and say so). Identify the key definitions, mechanisms, results, derivations, and the common misconceptions / exam traps for that topic.

If nothing resolves, ask once (the available structured-question mechanism) what to grill on and at what level (e.g. "undergrad final? qualifying exam? seminar?").

Phase 1 — Build the question bank (internal, not shown)

Rank a bank across the dimensions for the mode. Each question is grounded in the material, tagged by dimension + difficulty, and paired internally with the model answer + the trap (revealed only in the debrief).

Defend dimensions:

DimensionProbing…
Motivation / "so what"Why care? What breaks if you're wrong?
Contribution / noveltyWhat's new vs the nearest rival? One contribution or three?
Model / assumptionsWhich assumption is load-bearing? What happens when you weaken it? Is it stated?
Identification / proofsDoes the design identify the claim? Does each step hold? Counterexample to the general case?
Positioning / venueWhy isn't this subsumed by [rival]? Why this venue?
Robustness / limitsThe most damaging check you didn't run? What would change your mind?

Study dimensions:

DimensionProbing…
Recall / definitionsState the definition/result precisely — no hand-waving.
Mechanism / "why"Why is it true? Explain the intuition, not just the statement.
Derivation / workingWork the step / solve the problem — show the reasoning.
Application / transferApply it to a case you haven't seen; when does it fail?
Connections / compareHow does it relate to [other concept]? What's the difference?
Misconceptions / trapsThe exam trap — the plausible-but-wrong answer, and why it's wrong.

Seed the hardest slots from Phase 0's real material (logged referee issues in defend mode; known exam traps in study mode) before filling with derived questions.

Phase 2 — The drill (interactive, ONE question per turn)

The drill is turn-by-turn — ask exactly one primary question, then STOP and wait for the answer. Never dump the bank; never answer your own question.

Evaluate each answer silently — does it address the question, is it correct/grounded, or is it a dodge? Then:

  • Weak / wrong / evasive → grill it. Name the gap precisely. In defend mode: press whether the choice holds ("your Assumption 2 lets (g) be bimodal — so why does the peak stay at (\bar\theta)?"). In study mode: the answer is objectively wrong, so probe toward the correct one without handing it over ("not quite — what does the second-order condition require here?"). Push 1–2 follow-ups, then log and move on.
  • Solid → one-line acknowledgement, then next dimension or raise the stakes.
  • Adapt — spend the budget where the defender struggles; skip what they've nailed.
  • Persona = tone, not substance: examiner (rigorous, no free passes), reviewer2 (maximally adversarial), coach (drops a hint toward the answer — best for early study).

Keep a running tally: dimension · verdict (solid / shaky / fumbled / wrong / dodged) · the gap. The defender can say "stop", "skip", "hint", or "move on" anytime.

Never reveal the model answer mid-drill (except a partial hint in coach mode) — recall under pressure is the point. End after --rounds N primaries (default 10) or on "stop".

Phase 3 — Debrief + study sheet

When the drill ends:

  1. Readiness read (qualitative, no gimmick score): e.g. defend — "6 solid / 3 shaky / 1 fumbled — the mechanism is airtight, but contribution-count and identification would draw blood in a viva"; study — "you know the definitions cold but the derivations and application transfer is where you'd lose marks".
  2. Per-dimension summary — armoured vs exposed.
  3. The questions you fumbled / got wrong, each as: the question · why your answer was weak/wrong · the model answer (defend: a strong defense; study: the correct explanation) · the trap · how costly it is (viva-fail / desk-reject / lost-exam-marks).
  4. Prep actions — concrete and specific. Defend: what to add to the paper/talk, the one line to rehearse, the robustness check that kills the question. Study: exactly which sections/concepts to re-review, and the misconceptions to unlearn.
  5. Offer to persist it: write the study sheet to reviews/<scope>/grill-me/<YYYY-MM-DD>.md (defend, scope = paper slug or _project) or notes/grill-me/<subject>-<YYYY-MM-DD>.md (study). Read-only w.r.t. the material — grill-me never edits your paper or notes.

Key Rules

  1. One question per turn — the drill is the product. Batch-dumping is a study sheet, not a grilling.
  2. Ground every question in the material. No generic "what's your contribution?" / "define entropy" — tie it to their paper or their course notes.
  3. Reuse real material first — a logged referee open-issue (defend) or a known exam trap (study) outranks an invented question.
  4. No model answers mid-drill (partial hints only in coach mode). Answers land in Phase 3.
  5. Escalate then release — 1–2 follow-ups, then log and move on; don't grind one point forever.
  6. Honest verdicts, calibrated tone. Don't flatter a thin answer; the persona sets how hard you say it. In study mode, wrong is wrong — correct it kindly but clearly.
  7. Read-only on the material. The only write is the optional study-sheet file.

Anti-Patterns

  • Don't print all 10 questions at once and wait — ask one, stop.
  • Don't reveal the answer while the defender is still trying (recall under pressure is the point).
  • Don't ask ungrounded quiz-show questions they can't map to their paper/class.
  • Don't accept a dodge — name it and re-ask.
  • Don't grill without a debrief — the study sheet is where the value is banked.
  • Don't invent a referee objection when reviews/INDEX.md already records a real one, or a fake exam trap when the notes state the real one.

Cross-References

Skill / AgentRelationship
devils-advocateStress-tests arguments in prose; grill-me makes you defend them live
referee2-reviewer / paper-criticWritten adversarial critique; grill-me seeds its hardest defend-mode questions from their reports
weakness-scannerFinds weak points; grill-me turns them into live questions
review-cluster / pre-submission-reportRun first — their logged open-issues are grill-me's sharpest defend material
course-reading-list / init-project-courseCourse scaffolding; grill-me is the study-mode drill over that material
docs/reference/venue-profiles/<field>.mdVenue referee-bait to seed positioning/venue questions (defend mode)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.