agentleFS
Sign inStart free
igorkravcenkoigorkravcenko/snowshoe/.cursor/skills/grilling/SKILL.md

grilling

Skill1 starsChanged 36 days agoApache-2.0View on GitHub

Grill a plan or decision in interview rounds using frontier questions. Use when the user wants to stress-test thinking, or uses grill / grilling trigger phrases. Not for implementing.

193 other projects use a version of this, 111 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture-learning-tools, design-frontend-dev and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • The-Vibe-CompanySkill

    capture-learning-tools

    Turn technical conversations, bugs, CI failures, review comments,

    Also in 5 projects that use this

  • The-Vibe-CompanySkill

    design-frontend-dev

    Clean Impeccable frontend design skill. Use when the user wants to

    Also in 5 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 58 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 8 projects that use this

  • AWSSkill

    wizard

    Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

    Also in 136 projects that use this

  • +3 more from The-Vibe-Company

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 71 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the whole frontier in one round.

    line 16
  2. Very specific:

    Do not invent ARR, users, or competitors.

    line 30
  3. Very specific:

    No trading/Nautilus/portfolio gates — this is a personal git-comprehension product.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 71 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Grilling

Interview until shared understanding. Do not implement during a grill.

Map the subject as a design tree: every decision branches into the decisions that hang off it.

Rounds and frontier

Work the tree in rounds. The frontier is every decision whose prerequisites are already settled — questions you can ask now without guessing unanswered ones.

Ask the whole frontier in one round. Number each question. Give a recommended answer. Then wait.

❓ **Q1** - **<title>**: <body; choices if useful>

➡️ <recommended answer>

Settled answers push the frontier outward. A question that depends on another still open in this round belongs to a later round.

Facts vs decisions

  • Facts (repo, CURRENT, ADRs, public sources): look them up. Do not ask the user what you can read.
  • Decisions: the user's. Put each to them and wait.
  • Do not invent ARR, users, or competitors. If unknown, say unknown.
  • No trading/Nautilus/portfolio gates — this is a personal git-comprehension product.

Done

The frontier is empty: every material branch visited, nothing silently assumed. Do not act on the result until the user confirms shared understanding. Then offer (do not silently write) an ADR + CURRENT patch if a durable decision crystallized.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free