Agent skill

Grill Me

by plugin87 in plugin87/ux-ui-agent-skills

Interrogate the brief before a line is built — ask only the questions whose answers change the work, and put every unasked decision on the record as a stated assumption.

MITAuto-check passedAgent Workflows

Install Grill Me

skills CLI
$ npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install plugin87/ux-ui-agent-skills grill-me --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/plugin87/ux-ui-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/grill-me .claude/skills/grill-me && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
grill-me
GitHub stars
1.5k
Token cost
~1.4k tokens
SKILL.md length
647 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Interrogate the brief before a line is built — ask only the questions whose answers change the work, and put every unasked decision on the record as a stated assumption.

  • Works in 6 steps: Read before you ask → The bank — grouped by what no gate can see → The rule on asking → …
  • Tasks that involve Requirements gathering
  • SKILL.md covers 1. Read before you ask, 2. The bank — grouped by what…, 3. The rule on asking and 4. Everything unasked becomes…, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Grill Me is an agent skill from plugin87/ux-ui-agent-skills. Interrogate the brief before a line is built — ask only the questions whose answers change the work, and put every unasked decision on the record as a stated assumption.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Requirements gathering. The repository describes itself as: Turn Claude into a senior design architect: DTCG tokens, 52 components, WCAG 2.2 AA-AAA, 138 design systems, any-framework code, and 50 objective gates that fail the build… The licence is MIT.

When your agent uses it

  • Tasks that involve Requirements gathering

Example prompts

  • “/grill-me”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Read before you ask
  2. The bank — grouped by what no gate can see
  3. The rule on asking
  4. Everything unasked becomes a written assumption
  5. Output: a brief that can be checked later
  6. Then build, then prove it

What it can do on your machine

Read from SKILL.md and the folder at commit 14f8d44. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Grill Me loads about 1.4k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 647 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from plugin87/ux-ui-agent-skills at commit 14f8d44, republished under its MIT licence (© plugin87). 647 words, ~1,432 tokens.

Download SKILL.mdSave it as .claude/skills/grill-me/SKILL.md (or your agent's skills folder).
name
grill-me
description
Interrogate the brief before a line is built — ask only the questions whose answers change the work, and put every unasked decision on the record as a stated assumption.
disable-model-invocation
true

The gates catch a screen built wrongly. Nothing in this repo catches a screen built correctly from the wrong brief, and that is where the expensive rework comes from: four eval runs scored 14/14 on the gates and still came back from /critique as rework, every finding a decision no gate can see.

This command spends five minutes up front to remove that class of failure.

Target: $ARGUMENTS (the thing about to be built; if that is not clear, that is itself the first question).

1. Read before you ask

Asking for something the repo already answers is noise, and it teaches the user that answering you is a waste of time. Before writing a single question:

  • Look for an existing brief, CLAUDE.md, BRIEF.md, or a reference/ folder.
  • Look for an existing theme: ${CLAUDE_SKILL_DIR}/../../../tokens/*.json, design-tokens.json, theme.css. If one exists, the theme question is answered — do not ask it.
  • Look at the neighbouring screens and components. Framework, conventions, and the component inventory are usually visible, not unknown.

Every question you keep after this pass is one the code genuinely cannot answer.

2. The bank — grouped by what no gate can see

Pick from these. Do not ask all of them.

Purpose and lead

  • Who is this for, and what is the one task they came to finish?
  • What is the first thing their eye should land on? (Four equal cards means the answer is "nothing", and that is a composition bug before it is a design.)
  • What does success look like for them — what have they done when they leave?

Content reality

  • What does this look like with zero items? With one? With four hundred?
  • What is the longest string a real user will put in here — a 60-character project name, a nine-digit amount, an email with no spaces to break?
  • Which numbers are real and which are placeholder? Placeholder that ships as real is a lie the user catches immediately.

Irreversible actions

  • Which actions here destroy or cannot be undone, and what confirms them? (Destructive wears the danger variant in every place it appears — the trigger and the confirm dialog both. A blue Delete is an automatic fail.)
  • What happens when the action fails? What does the user read, and what can they do next?

Theme and platform

  • New theme or existing? If new: which direction, and does dark mode ship too?
  • What is the narrowest width this must survive? (The kit's floor is 280px.)
  • Which framework is the deliverable — and does it need RTL, AA or AAA?

Scope and done

  • How many screens or components exactly, and what is explicitly out of scope?
  • What has to be true before this is done: which gates, and is /critique part of the bar or not?
Show full SKILL.md (193 more words)Show less

3. The rule on asking

  • Maximum seven questions, asked in one round. A drip of one question at a time is worse than a wrong assumption.
  • Every question must change the work. If both answers produce the same build, it is not a question, it is a default — take it and say so.
  • Never ask what you can choose well. Taste is the job. Ask about intent, content, and constraint; decide the rest.

4. Everything unasked becomes a written assumption

An assumption held silently is indistinguishable from a guess. Each one gets a line: what was assumed, the default taken, and what it costs if it is wrong.

Assumption: no dark mode requested -> shipping both anyway (the theme is already
dual, so the cost of including it is zero and the cost of retrofitting is not).

5. Output: a brief that can be checked later

Write BRIEF.md next to the work, in this shape:

# <what is being built>

> **Step 0 — is the kit here?** This skill reads files from the kit. Check once:
> `ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING`
> On `KIT_MISSING` only the skill folders were installed, which is what
> `npx skills add` does. Say so plainly, point the user at
> `npx ux-ui-agent-skills init` or the plugin install, and stop. Do not guess the
> contents of a file you could not open.

Goal            one sentence, from the user's side
User and task   who, and the task they came to finish
Deliverables    exact list; N screens means N screens
Lead            the one thing the eye lands on first
Content reality empty / one / many, longest string, real vs placeholder
Irreversible    which actions, what confirms them, what failure reads like
Theme           source of truth, dark mode, brand direction
Platform floor  narrowest width, framework, RTL, AA or AAA
Out of scope    what this is deliberately not
Assumptions     each with its default and its cost if wrong
Done when       the gates that must pass, and whether /critique is part of the bar

This file is the thing /critique and a later reviewer argue against. A brief that lives only in the conversation cannot be checked, and so it will not be.

6. Then build, then prove it

/grill-me -> build -> /gate -> /critique. This command removes ambiguity. It does not produce quality, it does not score anything, and it is not a substitute for rendering the work and looking at it.

© plugin87, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/grill-me of plugin87/ux-ui-agent-skills.

Open the folder on GitHubat commit 14f8d44

Compare with similar skills

Grill Me next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Grill Me compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Grill Me this skillplugin87/ux-ui-agent-skills1.5k—~1.4kAutomated safety check: PassMIT
Cp Exploretangziwen/CubeMiniGame359—~535Automated safety check: PassMIT
Grill Designwill-ness-ai/skills168—~254Automated safety check: PassMIT
Layered Design Generatorbobbyz1x2c3/layer-designer117—~5.4kAutomated safety check: PassNone
Using Superpowersfarm-fe/farm5.6k34 repos~1.4kAutomated safety check: PassMIT
Interview Meaddyosmani/agent-skills102k6 repos~3.8kAutomated safety check: PassMIT

Similar skills

  • Cp Explore

    tangziwen/CubeMiniGame

    Explore and clarify a prospective CodePlan before writing design.md.

    359 GitHub stars~535 tokensUpdated 18 days ago
    Agent WorkflowsAuto-check passed
  • Grill Design

    will-ness-ai/skills

    Converge on a frontend look through rounds of prototypes and grilling verdicts.

    168 GitHub stars~254 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Layered Design Generator

    bobbyz1x2c3/layer-designer

    Generate professional UI/UX designs as layered PSD-like outputs with transparent layers.

    117 GitHub stars~5.4k tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check passed
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 34 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Interview Me

    addyosmani/agent-skills

    Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.

    102k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • Grilling

    bestofjs/bestofjs

    Grill the user relentlessly about a plan, decision, or idea.

    3.1k GitHub starsUsed in 30 repos~464 tokens
    Agent WorkflowsAuto-check passed

More from plugin87/ux-ui-agent-skills

All 23 skills in this repo
  • Data-Dense Dashboard Designer

    plugin87/ux-ui-agent-skills

    Lays out dense analytics or trading-terminal screens in banded sections with hand-drawn SVG charts, instead of a wall of identical stat cards.

    1.5k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • UI Component Spec Designer

    plugin87/ux-ui-agent-skills

    Writes a complete UI component spec with anatomy, variants, sizes, eight interaction states, design-token mapping and accessibility notes before or alongside code.

    1.5k GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Design Project Scaffold

    plugin87/ux-ui-agent-skills

    Creates a new design-product project from the kit's product-design template, then installs the engine folders and the Playwright dependency that the quality gates need.

    1.5k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Accessibility Audit

    plugin87/ux-ui-agent-skills

    Audits a UI or design against WCAG 2.2 and ARIA patterns and returns findings with the criterion, severity and a specific fix for each.

    1.5k GitHub stars~542 tokensUpdated today
    Auto-check passed
  • Apply Aesthetic

    plugin87/ux-ui-agent-skills

    Applies a chosen visual direction, an archetype or one of 138 named design systems, by remapping design tokens, then checks contrast before it finishes.

    1.5k GitHub stars~597 tokensUpdated today
    Auto-check passed
  • Brand Kit Design Tokens

    plugin87/ux-ui-agent-skills

    Builds a from-scratch brand design system as three-tier DTCG tokens plus one theme.css with light and dark modes, checked against WCAG contrast rules.

    1.5k GitHub stars~809 tokensUpdated today
    Auto-check passed

Questions about Grill Me

What does Grill Me do?

Interrogate the brief before a line is built — ask only the questions whose answers change the work, and put every unasked decision on the record as a stated assumption. Grill Me is an agent skill from plugin87/ux-ui-agent-skills. Interrogate the brief before a line is built — ask only the questions whose answers change the work, and put every unasked decision on the record as a stated assumption.

When should I use Grill Me?

Grill Me fits situations like: tasks that involve Requirements gathering.

How do I install Grill Me in Claude Code?

Run `npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a claude-code`. Or copy the skill folder (.claude/skills/grill-me in plugin87/ux-ui-agent-skills) into .claude/skills/grill-me in your project. Claude Code loads it when a task matches its description.

How do I install Grill Me in Codex?

Run `npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a codex`. Or copy the skill folder (.claude/skills/grill-me in plugin87/ux-ui-agent-skills) into .agents/skills/grill-me in your project. Codex loads it when a task matches its description.

Can I use Grill Me in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grill-me, .gemini/skills/grill-me, .github/skills/grill-me and .opencode/skills/grill-me in your project.

What does Grill Me need to run?

SKILL.md names no scripts, command-line tools or credentials: Grill Me is instructions for the agent only. Our summary lists: Node.js.

Does Grill Me access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Grill Me safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Grill Me use?

Grill Me is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Grill Me use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Grill Me?

Skills that share tags, products or a category with Grill Me: Cp Explore (tangziwen/CubeMiniGame, 359 stars), Grill Design (will-ness-ai/skills, 168 stars), Layered Design Generator (bobbyz1x2c3/layer-designer, 117 stars) and Using Superpowers (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Grill Me?

plugin87 (a GitHub user) maintains it in plugin87/ux-ui-agent-skills, which has 1,543 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 7, 2026.

Source: plugin87/ux-ui-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.