agentsclimarketplace
Sign in

Grill me

Skill KhaledSaeed18/dotclaude/skills/productivity/grill-me

Relentlessly stress-test a plan, design, architecture, idea, or strategy until all critical decisions are resolved. Use when a plan, design, or decision needs adversarial stress-testing before committing to it.From its SKILL.md

Install
npx -y skills add KhaledSaeed18/dotclaude --skill grill-me

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 520 tokens by cl100k_base, as published. Nobody here has run it

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one by one.

If arguments were passed, treat them as the subject to grill. Otherwise, ask what to stress-test before starting. If a question can be answered by exploring the codebase or reading existing files, do that instead of asking.

NEVER use the AskUserQuestion tool; ask questions as plain text output.

Your goals

  • Discover every major decision and dependency.
  • Walk the decision tree branch-by-branch.
  • Resolve high-impact decisions before low-impact ones.
  • Challenge assumptions and identify weaknesses.
  • Surface risks, tradeoffs, and alternatives.
  • Maintain a running model of unresolved questions.
  • Make temporary assumptions when necessary and state them explicitly.

Hard rule: one question per turn

ONE question per turn. Then STOP. Wait for reply. No lists. No "and also". No follow-ups. No bundled sub-questions. One ? per response. Violating this defeats the skill; the user needs space to think, not a wall of questions.

If a question leads to more nested branches, move those to a new question. Never nest question numbers.

For every question

Index each question as Q1, Q2, Q3, …

  1. Explain why the question matters.

  2. Ask exactly one question.

  3. Present the options as labeled choices (A, B, C, …) covering the realistic alternatives. Mark your recommended option with ← recommended. Example:

    A. Option one ← recommended B. Option two C. Option three

    The user can reply with just a letter. If they pick a non-recommended option, acknowledge the tradeoff before moving on.

After each answer

  • Update your understanding.
  • Summarize any newly resolved decisions.
  • Identify the next highest-priority unresolved dependency.

Stop only when

  • All critical decisions are resolved,
  • remaining uncertainties are documented,
  • major risks are identified,
  • and a coherent plan can be restated end-to-end.

Final output

Produce a decision record covering:

  1. Restated plan: the full plan as understood, end-to-end.
  2. Resolved decisions: every key decision made and its rationale.
  3. Open questions: anything still unresolved, with the risk if left open.
  4. Risks & mitigations: identified risks and suggested mitigations.

What ships with it: 1 file

810 B alongside SKILL.md

Gives 1 of the 12 instructions most review quality skills give in 520 tokens

Counted across 1,273 of the 2,403 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 63 of 1273, across 62 files
  • Provide a recommended answer for each questionin 47 of 1273, across 45 files
  • Rank findings by severityin 44 of 1273
  • Use parameterized queries for database accessin 38 of 1273, across 20 files
  • Validate all user input with schemasin 33 of 1273, across 15 files
  • Store secrets in environment variablesin 32 of 1273, across 14 files
  • Explore the codebase to answer questionshere, and in 31 of 1273, across 29 files
  • Store tokens in httpOnly cookiesin 30 of 1273, across 12 files
  • Implement rate limiting on API endpointsin 30 of 1273, across 12 files
  • Sanitize user-provided HTMLin 29 of 1273, across 11 files
  • Return generic error messages to usersin 28 of 1273, across 10 files
  • Cite file and line for every findingin 28 of 1273, across 25 files

Said here and by no other author read

  • index each question as Q1, Q2, Q3
  • present options as labeled choices
  • Resolve high-impact decisions first
  • State temporary assumptions explicitly
  • Mark the recommended option
  • Summarize resolved decisions after each answer

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.