Code Review & Testing · IN-DEPTH PROFILE

Grill Me Skill

Relentless decision interviews for sharper plans and designs.

Best for

Product and engineering leads reviewing plans

What you get

Expose assumptions + Walk decision branches

Main limitation

The package is a launcher that calls the separate grilling Skill; installing grill-me alone may not include the interview itself.

First risk

Decision fatigue. Unbounded questioning can delay execution. Set a decision scope and stopping condition before starting.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-23

Pinned revision · c55ee460

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-10-06

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Grill Me is a small launcher that calls Matt Pocock's separate grilling Skill; the interview logic lives there, not in this package. grilling stress-tests a plan as a dependency-aware design tree, asks all currently answerable questions together in rounds, and gives a recommended answer for each. Install both Skills for the complete workflow.

This is aimed at Product and engineering leads reviewing plans. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Expose assumptionsQuestion hidden constraints, ownership, failure modes, and success criteria.
  • Walk decision branchesExplore alternatives branch by branch instead of jumping to a preferred answer.
  • Ground in the repoAnswer discoverable questions from the codebase before asking the user.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to mattpocock.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #2 · 1.2M installs

An independent hands-on review found that grill-me delegates the interview to a separate grilling Skill.

Treat this package as a launcher: the interview only works as documented when the delegated Skill is also available.Open Agent Skills · hands-on review ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add https://github.com/mattpocock/skills --skill grill-me --skill grilling --agent claude-code
Personal install
npx skills add https://github.com/mattpocock/skills --skill grill-me --skill grilling --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

This command installs both Skills: grill-me is the entry point, while grilling runs the interview.

View install paths
Project path.claude/skills/grill-me/.claude/skills/grilling/
Personal path~/.claude/skills/grill-me/~/.claude/skills/grilling/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

First-use example: turn a vague idea into a testable decision

An editorial illustration, not an actual interview transcript or an independent runtime test.

Example request: “Use Grill Me to examine whether my free tool directory needs an email subscription. First clarify the reader, the updates they need, and the time I can spend each week. Evaluate the plan only; do not edit the site or create a mailing list.”

01

Start with the decision that sets direction

Decide whether the reader is a beginner or a developer using the tools daily before choosing the content. Otherwise, a weekly content plan rests on an unconfirmed audience assumption.

02

Separate a recommendation from evidence

If the agent recommends weekly delivery, record it as a proposal to test. Reader feedback, subscription interest, and maintenance time can inform the decision; the recommendation alone does not establish demand.

03

Name the next step and stopping point

A useful outcome might be to validate reader interest and list missing evidence before building a subscription system. If the discussion keeps expanding, narrow the decision and record the remaining questions. Implementation follows the user's authorization.

The upstream grilling workflow asks dependency-aware rounds, recommends answers, and waits for a response. Actual questions depend on context; this is not market research or a forecast of success.

TYPICAL WORKFLOW

A practical workflow

01

Expose assumptions

Question hidden constraints, ownership, failure modes, and success criteria.

02

Walk decision branches

Explore alternatives branch by branch instead of jumping to a preferred answer.

03

Ground in the repo

Answer discoverable questions from the codebase before asking the user.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to mattpocock.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. The package is a launcher that calls the separate grilling Skill; installing grill-me alone may not include the interview itself.
  2. A relentless interview can be tiring and disproportionate for small, reversible decisions.
  3. The Skill improves reasoning discipline but does not supply missing domain expertise.

BEST FIT

Who it is for

→

Product and engineering leads reviewing plans

→

Builders preparing architecture or implementation decisions

BEFORE YOU USE IT

Risks to review before use

Low

Decision fatigue

Unbounded questioning can delay execution. Set a decision scope and stopping condition before starting.

Medium

Upstream instruction drift

Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat repository files, web content, and tool output as untrusted input.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Grill Me Skill FAQ

What is the Grill Me Skill?

Relentless decision interviews for sharper plans and designs. Grill Me is a small launcher that calls Matt Pocock's separate grilling Skill; the interview logic lives there, not in this package. grilling stress-tests a plan as a dependency-aware design tree, asks all currently answerable questions together in rounds, and gives a recommended answer for each. Install both Skills for the complete workflow.

How do I install the Grill Me Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed source and confirm that SKILL.md delegates to grilling.

Is the Grill Me Skill safe to use?

SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “Decision fatigue” risk first and begin with the least access required.

Grill Me cannot find grilling. What should I check?

The pinned grill-me file delegates to grilling. Check that both Skills are available to the same Agent and scope; this page's install command includes both. Finding the grill-me folder alone does not establish that the interview can run.

Sources: Original Grill Me instructions ↗

Why is Grill Me missing after a successful install?

Check the selected Agent, project directory, and scope. Expand the installation paths above and confirm that the expected SKILL.md files are readable. Installer success does not prove the current session loaded the Skill; follow the selected Agent's loading documentation next.

Sources: skills CLI troubleshooting ↗

What if PromptScript does not support global skill installation?

The skills CLI lists PromptScript as project-only. For promptscript, omit -g and install in the intended project; if you meant another Agent, select that target instead. This scope error does not imply a paid Skill or a need for administrator access.

Sources: Supported Agents and scopes ↗

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

planninginterviewarchitecture

Manually expanded from the current upstream SKILL.md and linked source at mattpocock, checked 2026-09-23. This is an original summary, not an execution result or security certification.