agentsclimarketplace
Sign in

Grill me

Skill sinhoneyy/master-skills/skills/grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".From its SKILL.md

Install
npx -y skills add sinhoneyy/master-skills --skill grill-me

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 10 stars10 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.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, 484 tokens by cl100k_base, as published. Nobody here has run it

Grill Me

Derived from Matt Pocock's grill-me (MIT). Matt's interview discipline preserved verbatim. Additions: extraction + question + session tools + references + cs-* wrapper (see references/companion_tooling.md).

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time.

If a question can be answered by exploring the codebase, explore the codebase instead.

Rules (preserved + amplified)

  1. One question per turn. Never bundle.
  2. Provide a recommended answer with each question. Defaulting to "what do you think?" is lazy.
  3. Explore the codebase before asking. If grep / Read resolves it, do that first. Saves a turn.
  4. Walk the tree depth-first. Finish a branch before opening another.
  5. Track dependencies. If decision B depends on decision A, ask A first.

Workflow

  1. User provides a plan or design (or path to one).
  2. Run scripts/decision_tree_extractor.py to extract branches.
  3. Run scripts/question_generator.py to produce the question list with recommendations.
  4. Start a session: scripts/grill_session_tracker.py --action start.
  5. Walk the tree, one question at a time, recording answers in the session.
  6. When all branches resolved: report "shared understanding reached" + the locked-in decisions.

Output Pattern

Per question turn:

Q[i]/[total]: [question]
Recommended answer: [your call + 1-sentence rationale]

(Or: I explored the codebase and found [evidence]. Confirm?)

Tooling

See references/companion_tooling.md. Tools: extractor + generator + tracker. Agent: cs-grill-master. Command: /cs:grill-me.

Version: 1.0.0 Derived: Matt Pocock (MIT) + this repo's wrapper

What ships with it: 6 files

34.6 KB alongside SKILL.md, 3 of them executable

references/

scripts/

Keep looking

Skills are one crate of 326,696. 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.