Agent skill

Grill

by koolamusic in koolamusic/claudefiles

Adversarial questioning and collaborative shaping in one skill.

MITAuto-check passedAgent Workflows

Install Grill

skills CLI
$ npx skills add koolamusic/claudefiles --skill grill -a claude-code

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

GitHub CLI
$ gh skill install koolamusic/claudefiles grill --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/koolamusic/claudefiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/grill .claude/skills/grill && 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
GitHub stars
130
Token cost
~1.1k tokens
SKILL.md length
494 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Adversarial questioning and collaborative shaping in one skill.

  • Works in 5 steps: One question at a time. Never batch. The… → Provide your recommended answer… → Walk the decision tree depth-first. When… → …
  • User says grill me
  • SKILL.md covers Pick the mode, Rules (both modes), Stress-test mode and Shape mode, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Grill is an agent skill from koolamusic/claudefiles. Adversarial questioning and collaborative shaping in one skill. Two modes: stress-test (challenge a plan/design until gaps surface) and shape (iterate on requirements and solution options until alignment). Use when user says 'grill me', 'stress-test this', 'challenge this plan', 'shape this', 'let's explore options', or wants to pressure-test any design before committing.

Its SKILL.md is about 1.1k 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 Load testing and Requirements gathering. The repository describes itself as: A minimal catalog of my favourite skills for working with claude. The licence is MIT.

When your agent uses it

  • User says grill me
  • Stress-test this
  • Challenge this plan
  • Lets explore options

Example prompts

  • “grill me”
  • “stress-test this”
  • “challenge this plan”
  • “/grill”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. One question at a time. Never batch. The user's answer to Q1 determines Q2.
  2. Provide your recommended answer alongside each question. The user can accept, reject, or redirect. Don't ask questions you could answer by…
  3. Walk the decision tree depth-first. When a branch opens (e.g. "we'll use a queue"), follow it to its leaf (retry policy, dead-letter…
  4. Track resolved branches. Maintain a mental ledger. Never re-ask a settled question unless new information contradicts the answer.
  5. Flag when you're satisfied. When all branches resolve, say so explicitly. Present the final state as a compact summary of decisions.

What it can do on your machine

Read from SKILL.md and the folder at commit b99ca65. 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 loads about 1.1k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 494 words of instructions outside code blocks.

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

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 koolamusic/claudefiles at commit b99ca65, republished under its MIT licence (© koolamusic). 494 words, ~1,067 tokens.

Download SKILL.mdSave it as .claude/skills/grill/SKILL.md (or your agent's skills folder).
name
grill
description
Adversarial questioning and collaborative shaping in one skill. Two modes: stress-test (challenge a plan/design until gaps surface) and shape (iterate on requirements and solution options until alignment). Use when user says 'grill me', 'stress-test this', 'challenge this plan', 'shape this', 'let's explore options', or wants to pressure-test any design before committing.

Grill

Relentless questioning that finds the gaps before code does. Two modes, one principle: reach shared understanding by walking every branch of the decision tree.

Pick the mode

Read the user's intent from context:

  • Stress-test (default) — a plan, design, or decision already exists. Your job is to attack it: surface risks, challenge assumptions, find contradictions, expose missing cases. You are the adversary.
  • Shape — no plan exists yet, or the user is exploring options. Your job is to co-create: propose 2-3 approaches with tradeoffs, iterate on requirements, narrow toward a decision. You are the collaborator.

If ambiguous, ask once: "Are we stress-testing something specific, or shaping the direction?"

Rules (both modes)

  1. One question at a time. Never batch. The user's answer to Q1 determines Q2.
  2. Provide your recommended answer alongside each question. The user can accept, reject, or redirect. Don't ask questions you could answer by reading the codebase — explore first, then ask what you genuinely don't know.
  3. Walk the decision tree depth-first. When a branch opens (e.g. "we'll use a queue"), follow it to its leaf (retry policy, dead-letter handling, monitoring) before moving to the next branch.
  4. Track resolved branches. Maintain a mental ledger. Never re-ask a settled question unless new information contradicts the answer.
  5. Flag when you're satisfied. When all branches resolve, say so explicitly. Present the final state as a compact summary of decisions.

Stress-test mode

Your stance is adversarial. For each aspect of the plan:

  • What breaks under load?
  • What breaks with bad input?
  • What's the failure mode and who notices?
  • What's the implicit assumption that nobody stated?
  • What's the dependency that isn't in the plan?
  • What happens when this interacts with the part three sections above?

Don't soften. If the plan has a hole, name it. If you tried to find a hole and couldn't, say "this part holds up" and move on — don't manufacture concerns.

When stress-testing is complete, output:

## Stress-Test Summary

**Holes found:** N
<numbered list with severity: BLOCKER / RISK / NITPICK>

**Held up under scrutiny:**
<numbered list of aspects that survived>

**Recommended next step:** <what to do with the findings>
Show full SKILL.md (174 more words)Show less

Shape mode

Your stance is collaborative. The flow:

  1. Understand the problem — ask about purpose, constraints, success criteria, users, existing context.
  2. Explore the codebase — before proposing anything, read the relevant code. Use the project's vocabulary.
  3. Propose 2-3 approaches — with your recommendation first. Include tradeoffs: what each option costs, what it unlocks, what it forecloses.
  4. Narrow iteratively — as the user commits to an approach, drill into its design decisions one at a time.
  5. Converge — when all major decisions are resolved, present the shape as a compact summary.

When shaping is complete, output:

## Shape Summary

**Problem:** <one sentence>
**Chosen approach:** <name and one-line description>

**Decisions made:**
<numbered list: decision + rationale>

**Deferred:**
<items explicitly pushed to later>

**Recommended next step:** <what to build first, or which skill to invoke>

Codebase awareness

Before the first question in either mode, scan for:

  • .project/PROJECT.md or .project/ROADMAP.md — project-level context
  • .jira/STATE.md — active sprint context
  • CLAUDE.md — project conventions
  • Recent git history — what's in flight

Reference what you find. Questions grounded in the actual codebase are sharper than abstract ones.

Ending early

The user can say "enough" or "ship it" at any time. When they do, produce the summary (stress-test or shape) with whatever branches are resolved and flag the unresolved ones as open risks.

© koolamusic, 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 skills/grill of koolamusic/claudefiles.

Open the folder on GitHubat commit b99ca65

Compare with similar skills

Grill 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 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Grill this skillkoolamusic/claudefiles130—~1.1kAutomated safety check: PassMIT
Grillingpietheinstrengholt/rssmonster56431 repos~510Automated safety check: PassMIT
Deep Divebyungjunjang/jangpm-meta-skills120—~2.5kAutomated safety check: PassNone
Grillingopencrvs/opencrvs-core1202 repos~205Automated safety check: PassCustom licence
Deep Divebyungjunjang/jangpm-meta-skills120—~2.7kAutomated safety check: PassNone
Grillingfossasia/eventyay-interpretation1.6k6 repos~167Automated safety check: PassApache-2.0

Similar skills

  • Grilling

    pietheinstrengholt/rssmonster

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

    564 GitHub starsUsed in 31 repos~510 tokens
    Agent WorkflowsAuto-check passed
  • Deep Dive

    byungjunjang/jangpm-meta-skills

    Socratic interview skill to deepen a spec or refine an existing agent blueprint.

    120 GitHub stars~2.5k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed
  • Grilling

    opencrvs/opencrvs-core

    Grill the user relentlessly about a plan or design. An agent skill from opencrvs/opencrvs-core.

    120 GitHub starsUsed in 2 repos~205 tokens
    Agent WorkflowsAuto-check passed
  • Deep Dive

    byungjunjang/jangpm-meta-skills

    A Codex skill for Socratic interviews that deepen a spec or refine an existing agent blueprint.

    120 GitHub stars~2.7k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed
  • Grilling

    fossasia/eventyay-interpretation

    Interview the user relentlessly about a plan or design. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 6 repos~167 tokens
    Agent WorkflowsAuto-check passed
  • Interview Me

    kdlbs/kandev

    Clarify a standalone idea or check assumptions before feature or fix planning.

    909 GitHub stars~1.4k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from koolamusic/claudefiles

All 13 skills in this repo
  • Explainer Formats

    koolamusic/claudefiles

    A skill your agent uses when asked to explain a topic, codebase, process, or document in a specific output format — plain language or Simplified Technical English (STE, in the style of ASD-STE100…

    130 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Breadboarding

    koolamusic/claudefiles

    Transform a workflow description into affordance tables showing UI and Code affordances with their wiring.

    130 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Orchestrator

    koolamusic/claudefiles

    Turn the current session into a chief-of-staff thread that runs a war room of three role slots — surveyor, executor, auditor — and routes per-branch work to durable, reusable child agents.

    130 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Retro

    koolamusic/claudefiles

    A skill your agent uses when a user completes a phase, sprint, milestone, or meaningful unit of work and needs a retrospective.

    130 GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Skill Creator

    koolamusic/claudefiles

    Guide for creating effective skills. An agent skill from koolamusic/claudefiles.

    130 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Debug

    koolamusic/claudefiles

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework with built-in backward tracing for deep-stack failures…

    130 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

Questions about Grill

What does Grill do?

Adversarial questioning and collaborative shaping in one skill. Grill is an agent skill from koolamusic/claudefiles. Adversarial questioning and collaborative shaping in one skill.

When should I use Grill?

Grill fits situations like: user says grill me; stress-test this; challenge this plan; lets explore options.

How do I install Grill in Claude Code?

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

How do I install Grill in Codex?

Run `npx skills add koolamusic/claudefiles --skill grill -a codex`. Or copy the skill folder (skills/grill in koolamusic/claudefiles) into .agents/skills/grill in your project. Codex loads it when a task matches its description.

Can I use Grill 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 koolamusic/claudefiles --skill grill -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, .gemini/skills/grill, .github/skills/grill and .opencode/skills/grill in your project.

What does Grill need to run?

SKILL.md names no scripts, command-line tools or credentials: Grill is instructions for the agent only.

Does Grill 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 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 use?

Grill 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 use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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?

Skills that share tags, products or a category with Grill: Grilling (pietheinstrengholt/rssmonster, 564 stars), Deep Dive (byungjunjang/jangpm-meta-skills, 120 stars), Grilling (opencrvs/opencrvs-core, 120 stars) and Deep Dive (byungjunjang/jangpm-meta-skills, 120 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Grill?

koolamusic (a GitHub user) maintains it in koolamusic/claudefiles, which has 130 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 8, 2026.

Source: koolamusic/claudefiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.