Content
88%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.
An exceptionally dense, highly actionable routing skill: concrete dws commands for every user endpoint, explicit validation and retry semantics, and a clean one-level reference bundle. Its weaknesses are mild — a duplicated policy block between the runtime contract and Shortcut sections, and a few inline sections that could be pushed to references.
Suggestions
De-duplicate the Schema/Help/unknown-command policy: state it once in 最小 DWS 执行契约 and have the Shortcut 发现 section reference it instead of repeating it verbatim.
Move the inline DWS_RUNTIME_CONTRACT policy detail into a shared reference (e.g. references/contracts.md, which already exists) and keep only a one-line pointer in the body.
Consider moving the dws-intent HTML comment markers out of the Golden Route table cells into a maintenance note or build artifact, since they consume context tokens without guiding runtime behavior.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is telegraphic and rule-dense with essentially zero explanation of concepts Claude already knows — every line is a routing rule or boundary. However, the Schema/Help/unknown-command policy is stated twice in nearly verbatim form (in 最小 DWS 执行契约 and again in Shortcut 发现), and the dws-intent HTML comments add tokens, so minor trimming is possible. This is 'efficient with minor instances that could be trimmed' (anchor 4) rather than the every-token-earns-its-place ideal of anchor 5. | 4 / 5 |
Actionability | The Golden Route table gives copy-paste-ready commands with flags and placeholders (e.g. `dws chat +dm --to <姓名> --content <内容>`, `dws chat +search-msg ... --start/--end`), and the schema inspection command is fully specified with --jq projection. Specific commands cover all common cases, matching the top anchor. | 5 / 5 |
Workflow Clarity | Multi-step flows are explicitly sequenced with validation checkpoints: write lifecycle (校验目标/限制/内容/确认 → 串行执行 → 验证), group lifecycle shown as a chain (创建 → 保存 CID → dismiss), and a numbered 错误最短路径 with a bounded retry feedback loop (仅 retryable=true 重试一次) and confirmation gating. Destructive/batch operations all carry explicit validation (写后读回, 清理须确认、验证, 检查 complete/hasMore), so no cap applies. | 5 / 5 |
Progressive Disclosure | The body is an overview/routing layer with a clearly signaled 按需加载 table mapping scenarios to one-level-deep references, and all 14 referenced bundle files (references/chat/*.md, references/card/*.md, references/*.md) exist as real files. Minor gaps keep it below anchor 5: the Help/Schema policy block is duplicated between the contract section and Shortcut 发现, and the inline DWS contract block is policy detail that could live in a shared reference. | 4 / 5 |
Total | 18 / 20 Passed |