Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add devcxl/mattpocock-skills-zh --skill triagegit clone --depth 1 https://github.com/devcxl/mattpocock-skills-zhWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/devcxl/mattpocock-skills-zh/triage)<a href="https://agentmods.dev/skills/devcxl/mattpocock-skills-zh/triage"><img src="https://agentmods.dev/badge/skills/devcxl/mattpocock-skills-zh/triage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/devcxl/mattpocock-skills-zh/triage"><img src="https://agentmods.dev/badge/skills/devcxl/mattpocock-skills-zh/triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.01739 |
| Opus 5 | $0.00019 | $0.00870 |
| Sonnet 5 | $0.00008 | $0.00348 |
| Haiku 4.5 | $0.00004 | $0.00174 |
Grade A, and why
triage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
分类（Triage）
让项目问题跟踪器上的 issue 走一遍由分类角色组成的小型状态机。
如果本仓库把外部拉取请求（PR）也当作请求入口（见 issue-tracker 配置），分类也覆盖它们：PR 就是带着代码的 issue——同样的角色、同样的状态、同样的状态机，只有少数几处下面标注了"仅限 PR"的差异。根据跟踪器配置，把裸的 #42 解析为 issue 或 PR。
分类期间发布到问题跟踪器的每条评论或 issue 必须以这段免责声明开头：
> *This was generated by AI during triage.*
参考文档
- AGENT-BRIEF.md — 如何写出耐用的 agent brief
- OUT-OF-SCOPE.md —
.out-of-scope/知识库如何运作
角色
两个类别角色：
bug— 有东西坏了enhancement— 新功能或改进
五个状态角色：
needs-triage— 等待维护者评估needs-info— 等待报告人补充信息ready-for-agent— 已完全明确，可供 AFK agent 接手ready-for-human— 需要人工实现wontfix— 不会处理
对 PR 而言，同样的状态对应到所附代码上：ready-for-agent 意味着已附上 brief，agent 应该对 diff 采取下一步；ready-for-human 意味着已准备好由人来合并。
每个经过分类的 issue 都应恰好带一个类别角色和一个状态角色。如果状态角色冲突，先标记出来并询问维护者，再做任何其他事情。
这些是规范角色名——问题跟踪器中实际使用的标签字符串可能不同。映射关系应该已经提供给你了——如果没有，告诉用户运行 /setup-matt-pocock-skills。
状态转换：未打标签的 issue 通常先进入 needs-triage；从那里转到 needs-info、ready-for-agent、ready-for-human 或 wontfix。报告人回复后，needs-info 回到 needs-triage。维护者随时可以推翻——遇到看起来不寻常的转换要标记出来，先问再行动。
调用
维护者调用 /triage 并用自然语言描述想要什么。理解请求并行动。例如：
- "把需要我关注的东西都给我看看"
- "看看 #42"（issue 或 PR）
- "把 #42 移到 ready-for-agent"
- "有哪些是 agent 可以接手的？"
展示需要关注的内容
查询问题跟踪器，按从旧到新展示三个桶：
- 未打标签——从未被分类过。
needs-triage——正在评估中。needs-info且报告人在上次分类笔记之后有活动——需要重新评估。
当 PR 在范围内时，把外部 PR 也放进这些桶，并在每一行标注 [PR] 或 [issue]。发现面只呈现外部 PR（跟踪器配置定义谁算外部）——协作者进行中的 PR 不是分类工作。这个过滤只作用于发现面；被明确点名的 PR 无论作者是谁都要分类。
展示每个条目的数量和一行摘要。让维护者挑选。
分类某个具体的 issue 或 PR
-
收集上下文。 读完整的 issue 或 PR（正文、评论、标签、作者、日期；PR 还要读 diff）。解析之前的分类笔记，不要重复问已解决的问题。使用项目的领域词汇表探索代码库，尊重相关区域的 ADR。对代码库做两项检查：(a) 冗余——按领域概念（而不只是请求的措辞）搜索请求的行为是否已有实现，并报告你查过哪里。如果找到了，就是已实现的
wontfix（步骤 5）。(b) 先前拒绝——读.out-of-scope/*.md，找出任何与本请求相似的条目。 -
给出建议。 告诉维护者你的类别和状态建议及理由，外加与请求相关的简要代码库摘要——包括是否已实现。等待指示。
-
验证主张。 在任何盘问之前，先确认主张站得住脚。对 bug，按报告人的步骤复现。对 PR，确认 diff 确实做了它声称的事——checkout 下来，运行相关测试或命令。报告发生了什么：已确认（附代码路径）、失败、或细节不足（强烈的
needs-info信号）。确认过的验证能产生强得多的 agent brief。
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 113 lines · 39 tokens per session scan A f2a8854794d1
triage is a skill published in the GitHub repository devcxl/mattpocock-skills-zh (343 stars, last pushed 7d ago), licensed MIT. It adds 39 tokens to every session and 1,739 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
requirement-delivery
A workflow for turning a new software request into a small, working deliverable. It clarifies acceptance criteria, identifies boundaries, breaks work into demonstrable parts, and looks for existing code or tools to reuse.
loop-orchestrator
Operate a fleet of durable agent loops under .loop/ — schedule which loop runs next, assign agents to roles (maker vs checker), enforce promotion gates from propose-only to write access, allocate budgets, detect stalled or dead loops, and roll up fleet status into one report. Use when asked to "run the loops"…
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
product-management-expert
Product management expertise for strategy, discovery, prioritization, roadmaps, PRDs, metrics, and stakeholder communication. Use when defining what to build, why, and how to measure success.
todo-discipline
Use when starting any complex task (3+ steps) or before declaring work complete. Enforces todo/task state to match reality — merge updates + read verification. Prevents false completion.