Adversarial plan interview before implementation. An agent skill from Luciole-Studio/Misaka-Agent.

MITAuto-check passedAgent Workflows

Install Grill Me

skills CLI
$ npx skills add Luciole-Studio/Misaka-Agent --skill grill-me -a claude-code

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

GitHub CLI
$ gh skill install Luciole-Studio/Misaka-Agent 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/Luciole-Studio/Misaka-Agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/misaka/core/skills/assets/optional/software-development/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
158
Used in
1 other repo
Token cost
~1.2k tokens
SKILL.md length
598 words
Files
1
Skills in repo
77
Repo updated
First seen
Licence
MIT

At a glance

Adversarial plan interview before implementation. An agent skill from Luciole-Studio/Misaka-Agent.

  • Works in 3 steps: Summarize ALL decisions in bullet points → List anything left open, and what is… → Ask: "Aligned? Should I start…
  • Tasks that involve Requirements gathering
  • SKILL.md covers When to Use, Prerequisites, Core Mechanic: Frontier Rounds and Question Coverage (work these…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Grill Me is an agent skill from Luciole-Studio/Misaka-Agent. Adversarial plan interview before implementation.

Its SKILL.md is about 1.2k 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: A multi-agent research system for the humanities and social sciences. The licence is MIT.

When your agent uses it

  • Tasks that involve Requirements gathering

Example prompts

  • “/grill-me”

Workflow steps

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

  1. Summarize ALL decisions in bullet points
  2. List anything left open, and what is explicitly OUT of scope
  3. Ask: "Aligned? Should I start implementing, or adjust anything?"

What it can do on your machine

Read from SKILL.md and the folder at commit 3bcf7a3. 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.2k tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 598 words of instructions outside code blocks.

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

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 Luciole-Studio/Misaka-Agent at commit 3bcf7a3, republished under its MIT licence (© Luciole-Studio). 598 words, ~1,165 tokens.

Download SKILL.mdSave it as .claude/skills/grill-me/SKILL.md (or your agent's skills folder).
name
grill-me
description
Adversarial plan interview before implementation.
version
2.0.0
author
Rafael Zendron (rafaumeu) + Matt Pocock (mattpocock/skills, grilling) + Hermes Agent
license
MIT
platforms
linux, macos, windows

Grill Me

Stress-tests a plan through structured adversarial questioning before any code is written. Models the plan as a design tree — every decision branches into the decisions that hang off it — and interviews the user in rounds until every branch is resolved and nothing is silently assumed.

Combines the phase discipline of the original with the frontier-rounds mechanic from mattpocock/skills' grilling.

When to Use

  • User says "grill me", "interview my plan", "stress test this idea"
  • Before complex work: auth flows, schema changes, migrations, payments
  • A plan has unresolved decisions or seems vague
  • Before subagent-driven-development decomposition

Do NOT use for existing code (use requesting-code-review) or simple one-off tasks.

Prerequisites

None. The skill works on any plan or raw idea.

Core Mechanic: Frontier Rounds

Map the plan as a design tree. The frontier is every decision whose prerequisites are already settled — the questions you can ask NOW without guessing at answers you haven't heard yet.

Work in rounds: ask the whole current frontier in one message, numbered, each question carrying your recommended answer. Then wait. A question whose answer depends on another question still open in this round belongs to a LATER round, not this one.

Format each round like so:

❓ Q1 — <question title>: <question body, options if relevant>
➡️ Recommendation: <your recommended answer + one-line why>

❓ Q2 — <question title>: <question body>
➡️ Recommendation: <...>

Each answer reshapes the tree: settled decisions push the frontier outward and unblock dependent questions. Recompute the frontier and ask the next round.

Facts are your job; decisions are the user's. When a frontier question needs a fact from the environment (codebase, filesystem, config, docs), find it yourself with search_files / read_file / terminal — or dispatch a subagent via delegate_task for a heavy exploration. Never ask the user for anything you could look up. Don't block on an exploration: only the questions downstream of it wait; ask the rest of the frontier now.

Question Coverage (work these branches into the tree)

Understanding — the real goal and boundaries:

  • What is the ACTUAL objective? What is explicitly IN and OUT of scope?
  • What are the constraints (time, tech, team, budget)? Who are the users?

Technical decisions — for each architectural choice:

  • "Why this approach and not X?" / "What happens if Y fails?"
  • "What's the worst case?" / "How would you roll back?"
  • Cross-reference the existing codebase; if the project already has a pattern for this, call it out.

Edge cases:

  • "What happens if the user does Z?" / "What if dependency X goes down?"
  • "What if volume is 100x expected?" / "What are the security implications?"
Show full SKILL.md (201 more words)Show less

Synthesis (when the frontier is empty)

  1. Summarize ALL decisions in bullet points
  2. List anything left open, and what is explicitly OUT of scope
  3. Ask: "Aligned? Should I start implementing, or adjust anything?"

Do not act on the plan until the user confirms shared understanding.

Pitfalls

  1. Asking questions out of dependency order. A question that depends on an unanswered question is a guess wearing a question mark. Keep it for a later round.
  2. Skipping the codebase. Find facts in code with Hermes tools instead of asking the user.
  3. Accepting "I don't know" as final. Suggest options, explain trade-offs, make a recommendation.
  4. Writing code during the interrogation. Alignment only — code after the explicit green light.
  5. Being too agreeable. Your job is to find problems. If everything looks fine, look harder.
  6. Not adapting to the user's language. Interview in whatever language the user speaks.

Verification

  • Every question in a round had all its prerequisites already settled
  • Provided a recommendation with each question
  • Explored the codebase for facts instead of asking the user
  • Frontier empty (no branch silently assumed) before synthesizing
  • Produced a clear summary of all decisions and open items
  • Confirmed user alignment before stopping

© Luciole-Studio, 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 misaka/core/skills/assets/optional/software-development/grill-me of Luciole-Studio/Misaka-Agent.

Open the folder on GitHubat commit 3bcf7a3

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Luciole-Studio/Misaka-Agent, which our catalogue first saw on October 7, 2026.

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 skillLuciole-Studio/Misaka-Agent1581 repos~1.2kAutomated safety check: PassMIT
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Interview Meaddyosmani/agent-skills103k6 repos~3.8kAutomated safety check: PassMIT
Grillingpietheinstrengholt/rssmonster56431 repos~510Automated safety check: PassMIT
Agentic Workflow Designerdotnet/Open-XML-SDK4.6k2 repos~3.5kAutomated safety check: PassMIT
Ask User QuestionMemTensor/MemOS12k—~1kAutomated safety check: PassApache-2.0

Similar skills

  • 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 35 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.

    103k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • 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
  • Agentic Workflow Designer

    dotnet/Open-XML-SDK

    Official

    Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.

    4.6k GitHub starsUsed in 2 repos~3.5k tokens
    Agent WorkflowsAuto-check passed
  • Ask User Question

    MemTensor/MemOS

    Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.

    12k GitHub stars~1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Brainstorming Before Building

    jnMetaCode/superpowers-zh

    Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.

    8.3k GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from Luciole-Studio/Misaka-Agent

All 77 skills in this repo
  • Kanban Video Orchestrator

    Luciole-Studio/Misaka-Agent

    Plan and run multi-agent video production pipelines. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check: notes
  • Ast Grep

    Luciole-Studio/Misaka-Agent

    AST-aware structural code search and rewrite via ast-grep. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed
  • Drug Discovery

    Luciole-Studio/Misaka-Agent

    Drug discovery: ChEMBL search, drug-likeness, interactions. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • Fitness Nutrition

    Luciole-Studio/Misaka-Agent

    Workout planning, macros, and body metrics via wger/USDA. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check passed
  • Hyperframes

    Luciole-Studio/Misaka-Agent

    Render MP4/WebM videos from HTML compositions. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed
  • Osint Investigation

    Luciole-Studio/Misaka-Agent

    Follow the money via public records and sanctions data. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed

Categories

Questions about Grill Me

What does Grill Me do?

Adversarial plan interview before implementation. An agent skill from Luciole-Studio/Misaka-Agent. Grill Me is an agent skill from Luciole-Studio/Misaka-Agent. Adversarial plan interview before implementation.

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 Luciole-Studio/Misaka-Agent --skill grill-me -a claude-code`. Or copy the skill folder (misaka/core/skills/assets/optional/software-development/grill-me in Luciole-Studio/Misaka-Agent) 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 Luciole-Studio/Misaka-Agent --skill grill-me -a codex`. Or copy the skill folder (misaka/core/skills/assets/optional/software-development/grill-me in Luciole-Studio/Misaka-Agent) 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 Luciole-Studio/Misaka-Agent --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.

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 (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Grill Me use?

About 1.2k tokens (SKILL.md is roughly 4.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: Using Superpowers (farm-fe/farm, 5.6k stars), Interview Me (addyosmani/agent-skills, 103k stars), Grilling (pietheinstrengholt/rssmonster, 564 stars) and Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.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?

Luciole-Studio (a GitHub organization) maintains it in Luciole-Studio/Misaka-Agent, which has 158 GitHub stars. The repository holds 77 skills in this directory. The repository was last updated on October 8, 2026.

Source: Luciole-Studio/Misaka-Agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.