grilling-zh SKILL.md skillA
grilling-zh from gongyijie85/mattpocock-skills-dsh-zh is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gongyijie85/mattpocock-skills-dsh-zh/grilling-zh@git:20260910.0667b2cPins git:20260910.0667b2c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gongyijie85/mattpocock-skills-dsh-zh
- Path
skills/grilling-zh/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260910.0667b2c, committed Sep 10, 2026
- Size
- 2,087 bytes
- Repository stars
- 8
- License
- MIT
对用户的计划、决策或想法进行穷追不舍的盘问。当用户想要压力测试自己的思路,或使用了任何 'grill' 触发短语时使用。.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
持续盘问用户,直到达成共识。将整个过程建模为一棵 **design tree(设计树)**:每个决策都会分支成挂在其下的各个决策。 以 **rounds(轮次)** 的方式推进这棵树。**frontier(前沿)** 是所有前提条件已经确定、可以 _现在就_ 提出的决策——这些问题无需猜测你尚未听到的答案。每一轮提出整个 frontier 上的全部问题:为每个问题编号,并给出你推荐的答案。然后等待用户回答,再进行下一轮。 按轮次格式化如下: ``` ❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices> ➡️ <your recommended answer> --- ❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices> ➡️ <your recommended answer> ``` 用户每一轮的回答都会重塑这棵树:已确定的决策把 frontier 向外推进,并解锁依赖它们的提问。重新计算 frontier,然后提出下一轮问题。某个问题的答案如果依赖于本轮仍处于开放状态的另一个问题,它应属于_更靠后_的轮次,而不是本轮。 查找_事实_是你的职责,永远不是用户的。当 frontier 上的某个问题需要来自环境(文件系统、工具等)的事实时,派遣一个 sub-agent 去查明;不要向用户询问任何你自己能查到的东西。不要因此阻塞:一次进行中的探查属于尚未确定的前提条件,所以只有它下游的问题需要等待 sub-agent 回报;现在就提出 frontier 上其余的问题。_决策_属于用户:把每个决策交还给用户,然后等待。 当 frontier 为空时,本次会话即告完成:design tree 的每个分支都已遍历,没有任何遗留的静默假设。在用户确认我们已达成共识之前,不要据此采取行动。
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qqurxmdyic3gukv5/fe4908114ff9a5736778183110e9613ed15332abf162cfbb5b1cb05bac0c0539.json
Then /plugin install grilling-zh@markdownregistry-qqurxmdyic3gukv5 in Claude Code. It installs git:20260910.0667b2c, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add gongyijie85/mattpocock-skills-dsh-zh/grilling-zh@sha256:fe4908114ff9a573The line at the top of this page pins the label git:20260910.0667b2c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qqurxmdyic3gukv5)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in gongyijie85/mattpocock-skills-dsh-zh/grilling-zh since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of grilling-zh from somewhere else? Ask it: where did my grilling-zh come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Sep 10, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/grilling-zh/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2087 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gongyijie85/mattpocock-skills-dsh-zh · 8 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qqurxmdyic3gukv5 GET https://markdownregistry.com/api/v1/resolve?ref=gongyijie85/mattpocock-skills-dsh-zh/grilling-zh GET https://markdownregistry.com/api/v1/blob/fe4908114ff9a5736778183110e9613ed15332abf162cfbb5b1cb05bac0c0539
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.