mattpocock-skills-zh-CN is a Simplified Chinese localization of a collection of reusable instructions for coding agents. Chinese-speaking developers use the translated skills to support engineering workflows while keeping their original commands, paths, identifiers, and behavior. The catalogue contains the localized skills, instructions, and plugin components.
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 vinvcn/mattpocock-skills-zh-CN --skill to-specgit clone --depth 1 https://github.com/vinvcn/mattpocock-skills-zh-CNWrote 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/vinvcn/mattpocock-skills-zh-cn/to-spec)<a href="https://agentmods.dev/skills/vinvcn/mattpocock-skills-zh-cn/to-spec"><img src="https://agentmods.dev/badge/skills/vinvcn/mattpocock-skills-zh-cn/to-spec/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/vinvcn/mattpocock-skills-zh-cn/to-spec"><img src="https://agentmods.dev/badge/skills/vinvcn/mattpocock-skills-zh-cn/to-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00029 | $0.00598 |
| Opus 5.5 | $0.00012 | $0.00239 |
| Sonnet 5.5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
to-spec 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 18d 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.
What it actually says
这个 skill 使用当前 conversation context 和 codebase understanding 产出 spec。不要访谈用户，只综合你已经知道的内容。
Issue tracker 和 triage label vocabulary 应该已经提供给你；如果没有，请让用户运行 /setup-matt-pocock-skills。
流程
-
如果还没有探索 repo，先探索它以理解 codebase 当前状态。在 spec 中始终使用项目 domain glossary vocabulary，并遵守相关 ADRs。
-
草拟你准备在哪些 seams 上测试这个 feature。优先使用现有 seams，而不是新增 seams。使用尽可能高层的 seam。如果确实需要新增 seams，尽可能在最高层提出。
Seams 越少越好，理想数量是一个。与用户确认这些 seams 是否符合预期。
- 使用下面模板写 spec，并发布到项目 issue tracker。应用
ready-for-agenttriage label；不需要额外 triage。
Problem Statement
用户正在面对的问题，从用户视角描述。
Solution
问题的解决方案，从用户视角描述。
User Stories
一份很长的编号 user stories 列表。每条 user story 使用以下格式：
- As an , I want a , so that
这份 user stories 列表应该非常完整，覆盖 feature 的所有方面。
Implementation Decisions
已作出的 implementation decisions 列表。可以包括：
- 将 build/modify 的 modules
- 将 modify 的 module interfaces
- 来自 developer 的技术澄清
- Architectural decisions
- Schema changes
- API contracts
- Specific interactions
不要包含具体 file paths 或 code snippets。它们可能很快过时。
例外：如果 prototype 产出的 snippet 比 prose 更精确地编码了某个决策（state machine、reducer、schema、type shape），可以内联到相关 decision 中，并简短说明它来自 prototype。只保留决策密集部分，不要放完整 working demo。
Testing Decisions
已作出的 testing decisions 列表。包括：
- 什么是好测试的描述（只测试 external behavior，不测试 implementation details）
- 哪些 modules 会被测试
- 测试的 prior art（即 codebase 中类似类型的 tests）
Out of Scope
本 spec 范围外事项的描述。
Further Notes
关于 feature 的其他 notes。
What ships with it
1 file 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.
- 18d ago Changed 4cb2a1cd86e6
- 1mo ago Changed b8ef330a1143
- 1mo ago First seen · 76 lines · 29 tokens per session scan A e8f622fc0826
to-spec is a skill published in the GitHub repository vinvcn/mattpocock-skills-zh-CN (5,317 stars, last pushed 7d ago), licensed MIT. It adds 29 tokens to every session and 598 once invoked, about $0.0001 per session on Opus 5.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
wayfinder
A planning method for large or unclear work that maps the decisions needed between the current situation and a defined destination. It records the map and decision tickets in an issue tracker.
triage
A structured issue-triage process that moves issues and, where configured, pull requests through classification and status steps. Triage means deciding what a report is, whether more information is needed, and who should handle it.
to-tickets
A method for turning a plan, specification, or conversation into small work tickets that each deliver a complete, testable slice of functionality. Each ticket records which other tickets must be finished first.
chief-of-staff
A coordination role for pursuing a long-running goal in one session by directing smaller helper agents. It keeps the strategic view while those agents handle individual tasks and shares progress through references to notes or commits.
to-spec
A method for turning the current conversation and codebase understanding into a detailed software specification, then publishing it as an issue in the project’s issue tracker. An issue tracker is a tool for recording and managing development work.
claude-handoff
A handoff tool that prepares a summary of the current conversation for another coding agent and starts that agent in the background.