Grill me

Skill bjg4/bgskillz/bakeoff/live/v4/grill-me-clone/grill-me

Build high-quality, portable Claude skills that trigger reliably and deliver real value.

Install

npx -y skills add bjg4/bgskillz --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

1 stars1 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 author says it does

Copied from the file, not written here

Helps users stress-test plans and designs through detailed questioning. Use when discussing architecture, project plans, or design documents. Supports Socratic dialogue and recommended answers.

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

1.7 KB, as published. Nobody here has run it

Plan and Design Review (Grill Me)

Purpose

Plans fail when unstated assumptions stay hidden. This skill uses questioning to surface gaps in scalability, security, data modeling, operations, and edge cases before implementation.

Use Cases

A developer has an architecture proposal and wants critical feedback.
A team is planning a launch and needs to stress-test dependencies.
Someone says "grill me" on a design doc.

Approach

Cover the design systematically:

Requirements — Who uses it? What scale? What SLAs?
Architecture — Components, data flow, failure modes.
Security — Threat model, auth, data protection.
Operations — Deploy, monitor, rollback, on-call.
Tradeoffs — What are you optimizing for? What are you deferring?

For each area, ask probing questions and provide your recommended answer or direction so the user can compare their thinking.

Interaction Style

Be thorough. It is acceptable to ask several related questions in one turn when exploring a subsystem, then summarize recommended paths.

If the codebase holds answers (e.g., existing auth pattern), read the codebase before asking the user.

Error Handling

If the plan is too vague, ask for a one-paragraph summary of goal and constraints before deep questioning.

Output

End sections with a short "recommended direction" when you have a strong opinion based on common practice.