Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/jpol34-grilling
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: testing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/grilling
What's inside
- Skill 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.
- License
- MIT
- Instructions
- 25 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
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> ``` 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. If the fact is a credential or secret value, retrieve it via Strongbox (`strongbox get <name>` / `Get-StrongboxSecret`) rather than asking the user to paste it into chat. 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.
From jpol34/polyak-dev-kit, MIT.
More from jpol34/polyak-dev-kit
- 0.529score
frontend
jpol34
Detect a repo's current frontend state and bring it to a professional, cohesive look with minimal design decisions from the user — install or wire an…
SkillBFreshness: BClaude Code +9 - 0.524score
research
jpol34
Research a topic exhaustively before planning or building — discuss the goal, draft a comprehensive question set, dispatch parallel research agents against…
SkillBFreshness: BClaude Code +9 - 0.496score
to-tickets
jpol34
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker…
SkillBFreshness: BClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Sep 17, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/jpol34/polyak-dev-kit
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from jpol34
- 0.529score
frontend
jpol34
Detect a repo's current frontend state and bring it to a professional, cohesive look with minimal design decisions from the user — install or wire an…
SkillBFreshness: BClaude Code +9 - 0.528score
Chuckle
jpol34
Look up meme template images by name or description, with disambiguation for ambiguous names.
ConnectorBFreshness: BRemoteClaude Code +3 - 0.524score
research
jpol34
Research a topic exhaustively before planning or building — discuss the goal, draft a comprehensive question set, dispatch parallel research agents against…
SkillBFreshness: BClaude Code +9 - 0.496score
to-tickets
jpol34
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker…
SkillBFreshness: BClaude Code +9
Cite this page
grilling skill. Agent Mart. https://agentmart.dev/skills/jpol34-grilling (last updated 2026-10-24)