Agent skill

Grill Me

by macalbert in macalbert/envilder

Grilling session that challenges a plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.

MITAuto-check passedAgent Workflows

Install Grill Me

skills CLI
$ npx skills add macalbert/envilder --skill grill-me -a claude-code

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

GitHub CLI
$ gh skill install macalbert/envilder 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/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/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
138
Token cost
~1k tokens
SKILL.md length
488 words
Files
3
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Grilling session that challenges a plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.

  • Works in 3 steps: Hard to reverse: the cost of changing… → Surprising without context: a future… → The result of a real trade-off: there…
  • Stress-testing a plan
  • SKILL.md covers Rules, Domain Awareness and During the Session
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Grill Me is an agent skill from macalbert/envilder. Grilling session that challenges a plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when stress-testing a plan, exploring trade-offs, validating a design, or refining domain language.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `ADR-FORMAT.md` and `CONTEXT-FORMAT.md`).

It sits in Agent Workflows, covering Requirements gathering, Architecture decision records and Load testing. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.

When your agent uses it

  • Stress-testing a plan
  • Exploring trade-offs
  • Validating a design
  • Refining domain language

Example prompts

  • “/grill-me”

Workflow steps

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

  1. Hard to reverse: the cost of changing your mind later is meaningful
  2. Surprising without context: a future reader will wonder "why did they
  3. The result of a real trade-off: there were genuine alternatives and you

What it can do on your machine

Read from SKILL.md and the folder at commit b6a0327. 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

    Links to these hosts (documentation or services it may open):

    • github.com

    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 1k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 488 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~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 macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 488 words, ~1,025 tokens.

Download SKILL.mdSave it as .claude/skills/grill-me/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
grill-me
description
Grilling session that challenges a plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when stress-testing a plan, exploring trade-offs, validating a design, or refining domain language.

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one. For each question, provide your recommended answer.

Ask the questions one at a time, waiting for feedback on each question before continuing.

If a question can be answered by exploring the codebase, explore the codebase instead.

Rules

  • Ask questions one at a time
  • For each question, provide your recommended answer with brief rationale
  • If a question can be answered by exploring the codebase, explore it instead of asking
  • Reference existing ADRs in docs/adr/: don't re-litigate settled decisions
  • Use project domain vocabulary (map-file, provider, facade, etc.)
  • When a decision crystallizes that contradicts an existing ADR, flag it explicitly
  • Stop when all branches are resolved or user says "enough"

Domain Awareness

During codebase exploration, look for existing documentation:

File structure

Most repos have a single context:

/
├── CONTEXT.md
├── docs/
│   └── adr/
│       ├── 0001-event-sourced-orders.md
│       └── 0002-postgres-for-write-model.md
└── src/

If a CONTEXT-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives:

/
├── CONTEXT-MAP.md
├── docs/
│   └── adr/                          ← system-wide decisions
├── src/
│   ├── ordering/
│   │   ├── CONTEXT.md
│   │   └── docs/adr/                 ← context-specific decisions
│   └── billing/
│       ├── CONTEXT.md
│       └── docs/adr/

Create files lazily: only when you have something to write. If no CONTEXT.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.

During the Session

Challenge against the glossary

When the user uses a term that conflicts with the existing language in CONTEXT.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y: which is it?"

Sharpen fuzzy language

When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account': do you mean the Customer or the User? Those are different things."

Show full SKILL.md (209 more words)Show less
Discuss concrete scenarios

When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.

Cross-reference with code

When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible: which is right?"

Update CONTEXT.md inline

When a term is resolved, update CONTEXT.md right there. Don't batch these up: capture them as they happen. Use the format in CONTEXT-FORMAT.md.

CONTEXT.md should be totally devoid of implementation details. Do not treat CONTEXT.md as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.

Offer ADRs sparingly

Only offer to create an ADR when all three are true:

  1. Hard to reverse: the cost of changing your mind later is meaningful
  2. Surprising without context: a future reader will wonder "why did they do it this way?"
  3. The result of a real trade-off: there were genuine alternatives and you picked one for specific reasons

If any of the three is missing, skip the ADR. Use the format in ADR-FORMAT.md.


Based on grill-with-docs by Matt Pocock.

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

Files

SKILL.md and 2 other files in .github/skills/grill-me of macalbert/envilder.

  • SKILL.md
  • ADR-FORMAT.md
  • CONTEXT-FORMAT.md

Open the folder on GitHubat commit b6a0327

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 skillmacalbert/envilder138—~1kAutomated safety check: PassMIT
Deep Divebyungjunjang/jangpm-meta-skills121—~2.5kAutomated safety check: PassNone
Grill Menrwl/nx29k—~1.2kAutomated safety check: PassMIT
Grill With Docsmeain/dotfiles28521 repos~875Automated safety check: PassMIT
Grill With Docsayoubben18/ab-method192—~2.1kAutomated safety check: PassMIT
Grill With Docsalirezarezvani/claude-skills28k—~1.8kAutomated safety check: PassMIT

Similar skills

  • Deep Dive

    byungjunjang/jangpm-meta-skills

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

    121 GitHub stars~2.5k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed
  • Grill Me

    nrwl/nx

    Grill the user relentlessly about a plan, design, decision, or set of review findings — working the decision tree in rounds until nothing is left silently assumed.

    29k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Grill With Docs

    meain/dotfiles

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.

    285 GitHub starsUsed in 21 repos~875 tokens
    DevelopmentAuto-check passed
  • Grill With Docs

    ayoubben18/ab-method

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.

    192 GitHub stars~2.1k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Grill With Docs

    alirezarezvani/claude-skills

    Docs-anchored grilling session — challenges a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs/adr/), and updates those files inline as terminology and…

    28k GitHub stars~1.8k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Model Domain

    danielvm-git/bigpowers

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates specs/tech-architecture/tech-stack.md and specs/adr/ inline as decisions crystallise.

    257 GitHub stars~1.2k tokensUpdated 16 days ago
    DevelopmentAuto-check passed

More from macalbert/envilder

All 30 skills in this repo
  • Code Review Perspectives

    macalbert/envilder

    Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity.

    138 GitHub stars~1k tokensUpdated 3 days ago
    Auto-check passed
  • Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions.

    138 GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed
  • Common Git

    macalbert/envilder

    Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning.

    138 GitHub stars~991 tokensUpdated 3 days ago
    Auto-check passed
  • Common Testing Conventions

    macalbert/envilder

    Mandatory testing conventions including the narrow diagnostic exception for testing test-only code, AAA pattern, test naming, and assertions across all stacks (.NET, TypeScript, Python).

    138 GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed
  • Doc Maintenance

    macalbert/envilder

    Workflow for maintaining changelogs, READMEs, and documentation files.

    138 GitHub stars~904 tokensUpdated 3 days ago
    Auto-check passed
  • Doc Sync

    macalbert/envilder

    Audit and synchronize documentation across website, READMEs, and docs/.

    138 GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Grill Me

What does Grill Me do?

Grilling session that challenges a plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Grill Me is an agent skill from macalbert/envilder.md, ADRs) inline as decisions crystallise.

When should I use Grill Me?

Grill Me fits situations like: stress-testing a plan; exploring trade-offs; validating a design; refining domain language.

How do I install Grill Me in Claude Code?

Run `npx skills add macalbert/envilder --skill grill-me -a claude-code`. Or copy the skill folder (.github/skills/grill-me in macalbert/envilder) 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 macalbert/envilder --skill grill-me -a codex`. Or copy the skill folder (.github/skills/grill-me in macalbert/envilder) 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 macalbert/envilder --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 names 1 domain. As links in the text: github.com. 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 1k tokens (SKILL.md is roughly 4.1k 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: Deep Dive (byungjunjang/jangpm-meta-skills, 121 stars), Grill Me (nrwl/nx, 29k stars), Grill With Docs (meain/dotfiles, 285 stars) and Grill With Docs (ayoubben18/ab-method, 192 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Grill Me?

macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.

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