grill-me

A small planning skill that interviews you about a fuzzy request until the important branches are resolved—before Claude dumps a pile of code.

What grill-me is for

grill-me is for the moment your request is still fuzzy: “build me a dashboard,” “refactor auth,” “make onboarding better.” Instead of coding immediately, Claude is steered to interview you until the important decisions are explicit—scope, constraints, success criteria, and the branches that usually explode mid-session.

On easyskills it ranks #4 (editorial score 90/100 as of Nov 21, 2026). It scores high because the job is concrete, the skill is small and composable, and developers repeatedly call out grilling-style skills as high leverage for vague prompts. We are not claiming timed lab trials of every grill prompt; the ranking is editorial: task fit, clarity, and how well it complements a shortlist without pretending to own the whole coding loop.

Why this score

Ninety is intentionally below Superpowers and the strongest task skills. grill-me does one thing extremely well—clarify before build—but it is not a full engineering methodology and it is not a deliverable skill like pdf or frontend-design. That niche is why it sits at #4: high enough that people looking for planning leverage find it, low enough that we do not oversell a tiny interview skill as a replacement for process or domain packs.

Who should install it

Install if you often give Claude under-specified tasks and want friction before code. Typical signals: you keep rewriting the same half-built feature, Claude invents product decisions you never agreed to, or your tickets start as Slack one-liners.

Skip if you already have a strict intake checklist in CLAUDE.md, your tickets already include acceptance criteria and non-goals, or you only need a task skill like PDF export or UI taste. Also skip stacking it as a second “session owner” beside a heavy methodology pack.

Install vs skip examples

  • Install: “Add billing” with no plan for taxes, trials, or invoice format.
  • Install: “Improve onboarding” with no definition of success or which surfaces change.
  • Skip: A ticket that already lists endpoints, schemas, and test cases.
  • Skip: You only need pdf or frontend-design for a narrow deliverable.

What SKILL.md typically covers

Expect prompts and procedures for asking clarifying questions, offering branching options, and stopping before implementation. Read the installed SKILL.md for exact triggers and stop conditions—this page summarizes the job, not every upstream sentence. Confirm the publisher is Matt Pocock’s package before you treat the text as authoritative; name collisions happen.

Install

npx skills add mattpocock/skills --skill grill-me

Reload your agent after install. Prefer a pin when the tooling exposes one. Walkthrough: How to install Claude skills. First-run hygiene: safe Claude skills checklist.

How to use it in a real session

  1. State the fuzzy goal in one sentence.
  2. Let grill-me drive questions; answer out loud or in chat.
  3. When branches are resolved, write the plan down (or hand off to your coding workflow).
  4. Only then implement. If Claude starts coding mid-grill, stop it.

A common failure mode is treating grilling as optional theater—saying “just build it” after two questions. You will get the same vague output you always get. Another failure mode is endless grilling with no decision; set a time box and lock choices.

vs nearby skills

  • vs Superpowers — Superpowers is a fuller coding loop (clarify → plan → build with tests → review). grill-me is a focused interview step. Prefer one session owner; you can reuse grilling ideas without running two methodology packs that fight for context.
  • vs find-skills — find-skills discovers packages when you know the job but not the name; grill-me clarifies your plan for work you already intend to do.
  • vs skill-creator — skill-creator helps you author Agent Skills; grill-me clarifies product or engineering work before code.
  • vs vercel-react-best-practices — performance rules for React/Next; not a substitute for product clarity.

Risks and caveats

Low blast radius compared with browser control, but grilling can feel slow if you already know the answers—say so and move on. The skill can also annoy teammates who want “just ship.” Align expectations: grilling is for under-specified work, not every typo fix.

Still verify the install source and run the safety checklist on first install. Do not confuse a clarifying skill with permission to skip reading other skills’ SKILL.md files later.

Source and date

Publisher: Matt Pocock (mattpocock/skills, skill grill-me). Editorial score and notes as of Nov 21, 2026. Upstream docs win when commands change.

Hubs: Claude skills for coding, Claude skills for research. Shortlist: best Claude skills. Terminal habits: Claude Code skills.

FAQ

What is grill-me?

A Matt Pocock skill that pushes Claude to ask clarifying questions about your plan until vague branches are resolved.

How do I install grill-me?

npx skills add mattpocock/skills --skill grill-me

Should I use grill-me with Superpowers?

You can use grilling ideas before a build, but do not stack two full methodology packs that both try to own the session.

When should I skip grill-me?

Skip it when the ticket is already sharp, you have a strict intake checklist in CLAUDE.md, or you only need a narrow task skill like pdf or frontend-design.

Related