Content
81%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A dense, well-structured execution contract: the situation→reference loading table, sequenced routing order, and bounded error-retry path with explicit validation gates make it highly actionable for its router role. The main gaps are minor: some duplicated error-handling rules between the inline contract and the error section, and a few orphaned bundle files not reachable from SKILL.md.
Suggestions
Consolidate the unknown command/flag fallback rules so they appear once — either in the 最小 DWS 执行契约 block or in 错误最短路径 — with the other location cross-referencing it, removing the current duplication.
Link or remove the orphaned bundle files (channel-login.md, runtime-contract.md, recipes/meta.md) from the 渐进加载 table or a bundle index so every reference is discoverable from SKILL.md.
Break the run-on contract sentences (e.g., the Schema/Help fallback bullet) into discrete rules so each fallback condition and its one-retry bound is scannable without re-parsing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean, telegraphic rule lists with essentially no padding and no explanation of concepts Claude already knows (e.g., "只用 dws;结构化读取加 --format json,按真实返回判断"). Not 5 because the unknown command/flag handling rules appear in both the inline contract block and again in 错误最短路径, and the contract block packs multiple fallback policies into single run-on sentences. | 4 / 5 |
Actionability | Concrete, executable guidance throughout: real commands and flags ("dws auth login --intl", "--format json", "--yes", "--verbose") and field-level specifics for the URL chain ("extension=dlink 时将 drive info 的 result.fileId 保存为入口 ID 并传给 dws doc info,再按 linkSourceInfo.nodeId 逐跳解析"). Not 5 because several steps remain at policy level or delegate mechanics to references ("按行动指南组合需要的产品 skill", "按真实返回判断") rather than fully specifying execution. | 4 / 5 |
Workflow Clarity | The 路由顺序 section is a clearly sequenced 5-step precedence order, and the error path has explicit bounded feedback loops: "写后验证结果,不凭退出码宣称成功", confirmation gate before adding --yes, "只有明确 retryable=true 时才按服务端节奏重试", and one-retry caps for unknown flag. Terminal states are enumerated (完成、部分、阻塞、待确认、失败). This satisfies the validation requirement for write/batch operations. | 5 / 5 |
Progressive Disclosure | The 渐进加载 table cleanly maps each situation to exactly one existing one-level-deep reference file, and all 11 referenced paths exist in the bundle. Not 5 because channel-login.md, runtime-contract.md, and recipes/meta.md sit in references/ unreferenced from SKILL.md, and the ../dingtalk-misc/references/profile.md link points outside this bundle — minor navigation gaps. | 4 / 5 |
Total | 17 / 20 Passed |