agentleFS
Sign inStart free
rengwurengwu/wayfinder-maps/skills/grill-me/SKILL.md

grill-me

Skill137 starsChanged 4 months agoMITView on GitHub

A relentless interview to sharpen a plan or design — one question at a time until every branch of the decision tree is resolved.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the questions one at a time, waiting for feedback on each question before continuing.

    line 9
  2. Distinctive:

    If a *fact* can be found by exploring the codebase or project files, look it up rather than asking me.

    line 11
  3. Distinctive:

    Do not enact the plan until I confirm we have reached a shared understanding.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 178 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

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.

Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.

If a fact can be found by exploring the codebase or project files, look it up rather than asking me. The decisions, though, are mine — put each one to me and wait for my answer.

Do not enact the plan until I confirm we have reached a shared understanding.

Download now (ZIP)

  • Other versions193 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 135

    1. mattpocock/skills★ 309k47% same
    2. QuivrHQ/quivr★ 40k47% same
    3. langfuse/langfuse★ 37k42% same
    4. windmill-labs/windmill★ 18k53% same
    5. GreyDGL/PentestGPT★ 16k53% same
    6. humanlayer/humanlayer★ 13k59% same
    7. jaredpalmer/kev★ 9.8k47% same
    8. openstatusHQ/openstatus★ 9.2k38% same
    9. webiny/webiny-js★ 8.1k43% same
    10. sanity-io/sanity★ 6.4k38% same

    125 more not listed

    Wrote their own version · 58

    1. nrwl/nx★ 29ksame name
    2. vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
    3. plugin87/ux-ui-agent-skills★ 3.1ksame name
    4. feiskyer/claude-code-settings★ 1.7ksame name
    5. marmelab/atomic-crm★ 1.4ksame name
    6. nateherkai/AIS-OS★ 1.4ksame name
    7. forcedotcom/salesforcedx-vscode★ 1ksame name
    8. Effect-TS/effect-smol★ 782same name
    9. AUTO-MAS-Project/AUTO-MAS★ 774same name
    10. RobMitt/grill-me-skill★ 549same name

    48 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use brief-to-tasks, decision-mapping 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.
    • julianoczkowskiSkill

      brief-to-tasks

      Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".

      Also in 7 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

    • LesaniSkill

      writing-beats

      Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

      Also in 59 projects that use this

    • simo97Skill

      migrate-to-shoehorn

      Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

      Also in 63 projects that use this

    • simo97Skill

      request-refactor-plan

      Use this skill when user wants to create a refactor plan.

      Also in 40 projects that use this

    • LesaniSkill

      writing-shape

      Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

      Also in 58 projects that use this

    • +2 more from simo97
  • In this repository13 other files it gives its agents.

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