grill-me
Skill11 starsChanged 32 days agoMITView on GitHub
Stress-test a business idea by interviewing the user one question at a time, walking down the design tree and resolving dependencies between decisions until you reach a shared understanding. Use when the user wants to be grilled on an idea, pressure-test a thesis, find the holes in their thinking, or says "grill me" / "stress-test this".
193 other projects use a version of this, 60 of them edited.
Adopted by
Most recently taken up by
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- niki914/zafirotheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- HiteSit/real-scientist-skillstheir own version, first seen Nov 15, 2026
- alexj11324/Mikkatheir own version, first seen Nov 15, 2026
- QiYueran-source/waymarktheir own version, first seen Nov 15, 2026
Used with
Projects with it also use brief-to-tasks, writing-beats 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.
julianoczkowskiSkillbrief-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
LesaniSkillwriting-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 66 projects that use this
simo97Skillrequest-refactor-plan
Use this skill when user wants to create a refactor plan.
Also in 43 projects that use this
simo97Skillmigrate-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 71 projects that use this
LesaniSkillwriting-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 65 projects that use this
liufeng1976Skillsetup-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
- +2 more from simo97
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 60
- langfuse/langfuse★ 37k12% same
- humanlayer/humanlayer★ 13k13% same
- openstatusHQ/openstatus★ 9.3k13% same
- webiny/webiny-js★ 8k13% same
- sanity-io/sanity★ 6.4k13% same
- camunda/camunda★ 4.4k13% same
- event-catalog/eventcatalog★ 3k13% same
- Akylas/OSS-DocumentScanner★ 2.6k13% same
- openstatusHQ/data-table-filters★ 2.3k13% same
- owid/owid-grapher★ 1.6k12% same
50 more not listed
Wrote their own version · 133
- mattpocock/skills★ 325ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- nrwl/nx★ 29ksame name
- windmill-labs/windmill★ 19ksame name
- GreyDGL/PentestGPT★ 16ksame name
- jaredpalmer/kev★ 9.8ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- pollinations/pollinations★ 5.3ksame name
123 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.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- find-gapsSkill
- founder-profileSkill
- new-ideaSkill
- onboardingSkill
- research-deepSkill
- wiki-lintSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 177 edited versions we read keep these.
1
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
- Distinctive: line 10
Ask one question at a time.
“Common” is measured: kept by at least 6 in 10 of the 177 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.
Files
Interview the user relentlessly about every aspect of the idea until you reach a shared understanding — what they actually believe, what they're guessing, and what evidence would flip the verdict.
Walk down the design tree branch by branch, resolving dependencies between decisions one by one. Start at the load-bearing roots (who the customer is, what the core value prop is) and only descend into dependent branches (pricing, channels, team) once their parents are settled. The idea overview's sections (Problem, Solution, Traction, Why this works, Business model, Market, Team, Risks) are a useful map — but follow the dependencies, not the order on the page.
Ask one question at a time. Wait for the answer before moving on — multi-question dumps let the user dodge the hard one.
For each question, provide your recommended answer grounded in what the wiki already says. If a question can be answered by reading the wiki, read it instead of asking. Start with the relevant idea overview, then its deep-dive notes. Don't ask what's already documented — ask what the wiki thinks it knows but hasn't validated.
The goal is shared understanding, not theatrics. Surface shaky premises and hidden assumptions as the current branch demands — no manufactured objections, no padding.
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
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.

