RonanCodes/grill-me
skills/grill-me/SKILL.md
Ephemeral grill mode (no durable artefacts). PREFER /ro:grill-with-docs as the default for ANY grill since it captures CONTEXT.md + ADRs alongside the interrogation. Use /ro:grill-me only when (a) the user explicitly asks for a no-docs grill, or (b) the repo has nowhere sensible to write durable docs (e.g. a throwaway scratch directory). Both skills walk the same decision tree the same way; the only difference is whether decisions get written down. Triggers on "grill me ephemeral", "quick grill no docs". For everyday "grill me / let's build / before we code / pressure-test this / interview me about", grill-with-docs is the default.
development
Updated Jun 8, 2026
$ install --global
skillsauthnpx skillsauth add RonanCodes/ronan-skills grill-meInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 8, 2026, 2:15 AM146.0s1 file scanned
SKILL.md
- name:
- grill-me
- description:
- Ephemeral grill mode (no durable artefacts). PREFER /ro:grill-with-docs as the default for ANY grill since it captures CONTEXT.md + ADRs alongside the interrogation. Use /ro:grill-me only when (a) the user explicitly asks for a no-docs grill, or (b) the repo has nowhere sensible to write durable docs (e.g. a throwaway scratch directory). Both skills walk the same decision tree the same way; the only difference is whether decisions get written down. Triggers on "grill me ephemeral", "quick grill no docs". For everyday "grill me / let's build / before we code / pressure-test this / interview me about", grill-with-docs is the default.
- allowed-tools:
- Bash Read Glob Grep
Grill Me
PREFER /ro:grill-with-docs by default. This skill is the ephemeral version: same interrogation, no durable artefacts. The transcript dies with the session. Almost every grill is more useful WITH docs (CONTEXT.md + ADRs survive into the next agent's context window), so reach for grill-with-docs first. Only use this skill when the user explicitly says "no docs" or the repo can't write to a docs/ folder.
Thin facade around Matt Pocock's grill-me skill. The pattern: interview the user relentlessly about a plan or design until shared understanding is reached, walking the decision tree one branch at a time, resolving dependencies in order.
Bootstrap (idempotent)
Before grilling, ensure the upstream skill is installed globally so /grill-me works in any project, not just this one:
test -e ~/.claude/skills/grill-me || npx -y skills@latest add mattpocock/skills/skills/productivity/grill-me -g
Run this once at the top of the session. The npx call is a no-op if Matt's skill is already symlinked.
How to grill
- One question at a time. Never a numbered list. The user is more likely to skim and confirm than write a long reply.
- Always include your recommended answer with the question, and a short why. Skim-and-confirm is the unit of progress.
- Walk the tree. Resolve foundations before details. Choices that gate later choices come first.
- Explore over ask. If a question can be answered by reading the codebase or docs, do that instead of asking the user.
- Stop when shared understanding is reached, not when the user runs out of patience. If you sense impatience, summarise the resolved decisions and offer to switch out of grill mode.
When to switch out
The user says "enough", "let's start", "go AFK", or pivots to a different task. Hand off cleanly: list resolved decisions, flag what's still open, then proceed to implementation.
Meeting-transcript variant
Same pattern, different input. If the user pastes (or points at a file containing) a recorded meeting transcript, run the grilling over the transcript instead of starting from a fresh brief:
- Read the transcript end-to-end.
- Extract the decisions that were made, and the gaps where decisions should have been made but weren't.
- Grill the user on the gaps only. Skip questions the transcript already settled.
This is how post-meeting "we kind of agreed" becomes a written contract before any code is touched. Pairs with /matt-pocock-coding-workflow step 1.
Conceptual background
The pattern (interrogation precedes specification) is documented at llm-wiki-ai-research:grill-before-spec. The skill is one implementation of that pattern; the principle holds regardless of tooling.
Why this skill exists in ronan-skills
Two reasons:
- Bootstrap. Anyone who installs the
roplugin gets Matt Pocock's upstream skill for free on first invocation, without having to know about it. - Better triggers. The upstream
descriptiononly fires on the literal phrase "grill me". This one nudges Claude into interview mode whenever the user is about to build, design, or spec out something new.
Related Skills
RonanCodes/skills/linear-pipeline
testing
VerifiedTrustedCommunity
--- name: linear-pipeline description: The Fable orchestrator for a single dispatched Linear ticket. Holds almost no context itself; it receives `--issue <ID> --detached`, decides the stage sequence, and fans out a sub-agent per stage, passing forward only each stage's artifact (never re-derived, never inlined into its own context). Step zero, before any planning or stage routing, is a boundary triage against `canon/security-boundary.md` (#199): a match tags Ronan Connolly and stops the run, no
SKILL.mdUpdated Jul 5, 2026
RonanCodes/skills/in-your-face
development
VerifiedTrustedCommunity
--- name: in-your-face description: Capture a chat-only answer into a durable artifact (markdown + HTML, PDF when cheap) and launch it automatically so the user cannot miss it. Use when user says "in your face", "don't let me lose this", "save that answer", "make that durable", or right after answering a substantive side question (a recipe, comparison, how-to, or generated prompt) that would otherwise die with the context. category: workflow argument-hint: [--no-open] [--vault <short>] [hint of
SKILL.mdUpdated Jul 5, 2026
RonanCodes/codex
tools
VerifiedTrustedCommunity
One-shot headless OpenAI Codex CLI calls for background/admin AI tasks — summaries, classification, extraction, admin glue. The default engine for anything that runs AI constantly in the background (daemon-driven, per-event), because it bills the flat ChatGPT subscription instead of Claude usage or per-token API spend, and it keeps working while Claude is rate-limited. NEVER for coding — coding stays Claude. Use when a skill or daemon needs a cheap always-on AI call, when the user says "use codex", "ask codex", "codex as backup", or when building a background summarizer/classifier into a listener or loop. Reads auth from ~/.codex/auth.json (ChatGPT account, no API key).
SKILL.mdUpdated Jul 5, 2026
RonanCodes/warranty-check
research
VerifiedTrustedCommunity
Turn a warranty rejection, repair quote, or RMA email into a cited decision brief — legal read (NL/EU consumer law), is the part user-serviceable, live part and new-unit prices, repair-vs-DIY-vs-new economics, before-you-send-it checklist, deadlines. Use when the user pastes or screenshots a repair quote, warranty rejection, "not covered" email, onderzoekskosten fee, or asks "should I repair or replace this".
SKILL.mdUpdated Jul 4, 2026