Score
9.3
/ 10
Installs
430K
Repo Stars
215.5K
Last Updated
5d ago
Quality Ratio
95%
Description
Verified
Language
Shell
First Published
Jun 2026
Summary
The Grilling agent skill equips AI agents with specific knowledge and procedures for executing grilling tasks effectively. It is particularly useful for developers configuring AI agents intended to manage, instruct on, or simulate real-world grilling scenarios. This is a skill with 11K installs, indicating a notable level of adoption within the registry. Details on how it specifically instructs an AI agent, including particular patterns, rules, or commands, are not available as there is no SKILL.md content provided. Nonetheless, its purpose is to equip agents with foundational knowledge for navigating various aspects of grilling.
Skill Definition
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.
Each question should be formatted like so:
❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <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.