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

MITAuto-check passedAgent Workflows

Install Grilling

skills CLI
$ npx skills add pietheinstrengholt/rssmonster --skill grilling -a claude-code

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

GitHub CLI
$ gh skill install pietheinstrengholt/rssmonster grilling --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/pietheinstrengholt/rssmonster.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/grilling .claude/skills/grilling && 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
grilling
GitHub stars
564
Used in
32 other repos
Token cost
~510 tokens
SKILL.md length
259 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

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

  • The user wants to stress-test their thinking
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Uses any grill trigger phrases

What it does

Grilling is an agent skill from pietheinstrengholt/rssmonster. Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Agent Workflows, covering Requirements gathering and Load testing. The repository describes itself as: Modern, self-hosted RSS reader with smart folders, powerful search, and a clean three-pane reading experience. Built with Vue and Express. The licence is MIT.

When your agent uses it

  • The user wants to stress-test their thinking
  • Uses any grill trigger phrases

Example prompts

  • “/grilling”

What it can do on your machine

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

Grilling loads about 510 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 259 words of instructions outside code blocks.

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

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 pietheinstrengholt/rssmonster at commit d2c278d, republished under its MIT licence (© pietheinstrengholt). 259 words, ~510 tokens.

Download SKILL.mdSave it as .claude/skills/grilling/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
grilling
description
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Interview the user relentlessly until you reach a shared understanding. Map this as a design tree: every decision branches into the decisions that hang off it.

Work the tree in rounds. 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. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round.

Format a round like so:

❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>

➡️ <your recommended answer>

---

❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>

➡️ <your recommended answer>

Word each question so "yes" accepts your recommended answer.

Each round the user answers reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a later round, not this one.

Finding facts is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it; don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report; ask the rest of the frontier now. The decisions are the user's: put each to them and wait.

The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.

© pietheinstrengholt, 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 1 other file in .agents/skills/grilling of pietheinstrengholt/rssmonster.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit d2c278d

Used in at least 30 other repositories

We found 62 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 32 other GitHub owners. This page covers the copy in pietheinstrengholt/rssmonster, which our catalogue first saw on October 8, 2026.

…and 12 more copies not listed here.

Compare with similar skills

Grilling 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.

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

    121 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
  • Grill

    koolamusic/claudefiles

    Adversarial questioning and collaborative shaping in one skill.

    130 GitHub stars~1.1k tokensUpdated 2 days ago
    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 pietheinstrengholt/rssmonster

  • Codebase Design

    pietheinstrengholt/rssmonster

    Shared vocabulary for designing deep modules. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 36 repos~1.5k tokens
    Auto-check passed
  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Auto-check passed
  • Improve Codebase Architecture

    pietheinstrengholt/rssmonster

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    564 GitHub starsUsed in 34 repos~1.5k tokens
    Auto-check passed
  • Close The Loop

    pietheinstrengholt/rssmonster

    A skill your agent uses when a feature has already gone through multiple implementation and review cycles and the work is starting to loop.

    564 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Rssmonster Browser

    pietheinstrengholt/rssmonster

    Use Codex browser capabilities to inspect and validate the RSSMonster UI in a real browser.

    564 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Final Review

    pietheinstrengholt/rssmonster

    Perform a rigorous final review of an implementation before considering it ready to merge or ship.

    564 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

Questions about Grilling

What does Grilling do?

Grill the user relentlessly about a plan, decision, or idea. Grilling is an agent skill from pietheinstrengholt/rssmonster. Grill the user relentlessly about a plan, decision, or idea.

When should I use Grilling?

Grilling fits situations like: the user wants to stress-test their thinking; uses any grill trigger phrases.

How do I install Grilling in Claude Code?

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

How do I install Grilling in Codex?

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

Can I use Grilling 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 pietheinstrengholt/rssmonster --skill grilling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grilling, .gemini/skills/grilling, .github/skills/grilling and .opencode/skills/grilling in your project.

What does Grilling need to run?

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

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

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

About 510 tokens (SKILL.md is roughly 2k 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 Grilling?

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

Who maintains Grilling?

pietheinstrengholt (a GitHub user) maintains it in pietheinstrengholt/rssmonster, which has 564 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

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