grill
Skill2 starsChanged 5 days agoApache-2.0View on GitHub
对用户进行无情盘问,追问其计划、决定或想法。适用于用户想要检验自身思维能力,或使用任何带有“盘问”字眼的触发词的情况。
87 other projects use a version of this.
Adopted by
Most recently taken up by
- Yesterday-AI/ytstacktheir own version, first seen Nov 8, 2026
- therealtinhtute/mono-harnesstheir own version, first seen Nov 8, 2026
- gaoyu06/harnesstheir own version, first seen Nov 8, 2026
- afawfawffaf/my-skillstheir own version, first seen Nov 8, 2026
- BSSE23047/nauraiz-devtheir own version, first seen Nov 8, 2026
- Mahesh-Bishnoi/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use write-skill, root-cause 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.
NoaiRoxSkillwrite-skill
Use when creating a new skill, editing an existing skill, or verifying a skill works before deployment.
Also in 5 projects that use this
Ingramradical235Skillroot-cause
Structured root cause analysis using WHERE (MECE decomposition) then WHY (causal structure diagrams) pipeline. Includes coin-flip detection, logical-leap detection, and vicious cycle intervention. Use when buffer enters YELLOW/RED, when metrics stall, or when Actions execute but don't produce results.
Also in 4 projects that use this
Neko-Catpital-LabsSkillprove-it
Shared evidence rule for investigating, diagnosing, debugging, proving, or explaining what happened or why for any problem or situation: do not assert something is fixed, working, passing, merged, or running unless you personally observed it this turn and can show what you saw; do not assert it was caused by X until a repro and controlled isolation prove that cause.
Also in 4 projects that use this
sahinSkillexecute
Also in 5 projects that use this
assisjpSkillfile-pr
Prepare and open or update an authorized pull request with a concise problem-first description and verifiable evidence. Use when the user asks to create, file, open, or update a PR. Do not use merely to review a diff or when publication is not authorized.
Also in 3 projects that use this
Arman-KudaibergenovSkillwrite-plan
Этот скилл MUST быть вызван когда есть design.md и нужно разбить доработку на атомарные задачи (2-5 мин) с точными путями файлов и критериями проверки в tasks.md. SHOULD также вызывать как промежуточный шаг между brainstorm и subagent-dev. Do NOT использовать для обсуждения идеи — используй brainstorm; для выполнения задач — используй subagent-dev.
Also in 3 projects that use this
Other versions87 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 87
- kirodotdev/KiroCrew★ 4.8ksame name
- crbnos/carbon★ 2.8ksame name
- JuliusBrussee/cavekit★ 1.1ksame name
- SethGammon/Citadel★ 927same name
- nagi-studio/skills★ 470same name
- KerberosClaw/kc_ai_skills★ 79same name
- alamops/skills★ 53same name
- Kanevry/session-orchestrator★ 53same name
- oakreader/oakreader★ 46same name
- manusco/resonance★ 38same name
77 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 repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- database-designSkill
- drizzle-migration-conflictSkill
- git-stackSkill
- hugo-to-markdownSkill
- postgresql-cliSkill
- prdSkill
- pre-release-reviewSkill
- rclone-cliSkill
- redis-cliSkill
- to-specSkill
- to-taskSkill
The file
Files
grill
反复与用户访谈,直到达成共识。将此过程绘制成 设计树:每个决策都会衍生出后续的决策。
流程
分轮处理决策树。边界 是指所有前提条件已经确定的决策:即你 现在 可以提出的问题,而无需猜测你尚未听到的答案。在一轮中询问整个边界:给每个问题编号并给出你的建议答案。然后等待用户的回复,之后再进行下一轮。
格式如下:
❓ **Q1** - **<问题标题>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <你推荐的答案>用户每回答一轮问题,问题树就会重塑:已确定的答案会将边界向外推移,并解锁依赖于这些答案的问题。重新计算边界,然后进行下一轮提问。如果某个问题的答案依赖于本轮中尚未解决的问题,则该问题属于 后续 轮次,而非本轮。
寻找 事实 是你的工作,而不是用户的。当一个前沿问题需要从环境(文件系统、工具等)中获取事实时,派出一个子代理去查找;不要向用户询问任何你可以自己查找的信息。不要因此而阻塞:正在进行的探索是一个尚未确定的前提条件,因此只有其下游的问题才需要等待子代理的报告;现在就可以向前沿问题的其他部分提出请求。决策权 在用户手中:把每个问题都交给他们,然后等待。
注意: 每次只提问一个问题,避免提问所有问题。
保存
引导用户保存文档,当设计树的每个分支都已遍历完毕,没有任何未加假设的内容时,会议即告结束。在用户确认已达成共识之前,请勿采取任何行动。
**是否保存文档**
A. docs/grill/grill-<subject>.md (推荐)
B. 不保存留在原地
C. 自定义目录或其他说明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.

