Index of every page on this site: llms.txt
All skills
brianlovin avatar

/grill-me

@1a9819e official
by Brian Lovinbrianlovin/agent-config377 stars
33
Run it yourself

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Use this Skill: https://skilld.dev/gh/brianlovin/agent-config/grill-me

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈60 tokens for metadata: the name and description. ≈83 when used: this file.

Description uses 3.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈242 characters, or 3.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill is designed to interview the user to stress-test designs and plans, including codebase exploration. It is generally safe but carries a low risk of indirect prompt injection because it incorporates external codebase content into its reasoning process without explicit boundary markers.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at 1a9819e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Dormantupdated 7 months ago
  • interviewing
  • planning
  • design-review
  • decision-making
  • requirements
  • problem-solving
  • stakeholder-alignment

README badge

README badge for brianlovin/agent-config/grill-me

Conducts systematic interviews about a plan or design, asking probing questions down each decision branch until reaching shared understanding. Use when stress-testing an architecture, design decision, or plan—the skill walks dependencies methodically and suggests answers where codebase context exists.

Generated from the current SKILL.md.

When should I use this skill instead of just asking for feedback?
Use this when you want structured, deep interrogation of a plan or design. The skill walks through decision branches systematically and provides recommended answers for each question, rather than general critique.
Does this skill look at my codebase?
Yes. If a question can be answered by exploring the codebase, the skill will do that instead of asking you.
What counts as a valid trigger to activate this skill?
Explicitly mentioning 'grill me', saying you want to stress-test a plan, or asking to be grilled on a design. The skill is on-demand and requires a clear signal from the user.

Generated from the current SKILL.md. These answers refresh after source changes.