triage-zh SKILL.md skillA
triage-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/triage-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/triage-zh/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260910.0667b2c, committed Sep 10, 2026
- Size
- 6,436 bytes
- Repository stars
- 8
- License
- MIT
让项目中的 issues 和外部 PR 沿着一组 triage 角色的状态机流转——分类、验证、必要时追问(grill),并写出 agent-ready 的 brief。.
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
# 分流(Triage) 让项目 issue tracker 上的 issues 沿着小型 triage 角色状态机流转。 如果本仓库把外部 pull request 也当作请求入口(参见 issue-tracker 配置),triage 同样覆盖它们:**PR 就是附带了代码的 issue**——同样的角色、同样的状态、同样的状态机,只是下面标注了几处 "for a PR" 的差异。根据 tracker 配置把裸 `#42` 解析为 issue 或 PR。 triage 期间发布到 issue tracker 的每条评论或 issue **必须**以这段免责声明开头: ``` > *This was generated by AI during triage.* ``` ## 参考文档 - [AGENT-BRIEF.md](AGENT-BRIEF.md) — 如何撰写持久的 agent brief - [OUT-OF-SCOPE.md](OUT-OF-SCOPE.md) — `.out-of-scope/` 知识库如何运作 ## 角色 两个 **分类(category)** 角色: - `bug` — 某样东西坏了 - `enhancement` — 新功能或改进 五个 **状态(state)** 角色: - `needs-triage` — 维护者需要评估 - `needs-info` — 等待报告者提供更多信息 - `ready-for-agent` — 已完整说明,可供 AFK agent 接手 - `ready-for-human` — 需要人类实现 - `wontfix` — 不会被处理 对于 PR,同样的状态要对照其附带的代码来解读:`ready-for-agent` 意味着已附上 brief,agent 应对 diff 采取下一步行动;`ready-for-human` 意味着已准备好由人类合并。 每个经过 triage 的 issue 应恰好携带一个 category 角色和一个 state 角色。如果 state 角色冲突,先标记出来并向维护者询问,再做任何其它事情。 这些是规范角色名——issue tracker 中实际使用的标签字符串可能不同。映射关系应当已经提供给你。如果没有,告诉用户运行 `setup-matt-pocock-skills`。 状态转换:未打标签的 issue 通常先进入 `needs-triage`;从那里它移动到 `needs-info`、`ready-for-agent`、`ready-for-human` 或 `wontfix`。报告者回复后,`needs-info` 返回 `needs-triage`。维护者可以随时覆盖——标记看起来不寻常的转换,并在继续之前询问。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_a52zjxni4wg352js/7d67bf984f207dd3195bf1fca0ead43666d16ab33083688502017d1fc71b0a1f.json
Then /plugin install triage-zh@markdownregistry-a52zjxni4wg352js 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/triage-zh@sha256:7d67bf984f207dd3The 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_a52zjxni4wg352js)
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/triage-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 triage-zh from somewhere else? Ask it: where did my triage-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/triage-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 (6436 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_a52zjxni4wg352js GET https://markdownregistry.com/api/v1/resolve?ref=gongyijie85/mattpocock-skills-dsh-zh/triage-zh GET https://markdownregistry.com/api/v1/blob/7d67bf984f207dd3195bf1fca0ead43666d16ab33083688502017d1fc71b0a1f
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.