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.
A lean, highly operational shared-entry SKILL.md: dense runtime contract, explicit routing order, and error handling with validation checkpoints and retry semantics. The only gaps are mechanics deferred to references without a named entry command, and a few orphan bundle files not discoverable from the entry table.
Suggestions
Name the actual node-type probe command (or a one-line example) in routing step 1 for the alidocs /i/nodes/ flow, so the URL resolution chain is executable without first opening url-patterns.md.
Add 渐进加载 table rows (or a one-line pointer) for channel-login.md, runtime-contract.md and recipes/meta.md so every bundle file is discoverable from the entry point.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~80-line body is dense and operational throughout: the runtime contract bullets, the situation→file table, and the routing/error sequences contain zero padding and no explanations of concepts Claude already knows. Every token carries a rule, a command, or a routing decision, matching the 'lean and efficient; every token earns its place' anchor. | 5 / 5 |
Actionability | Guidance is concrete and executable: exact flags and commands (`--format json`, `dws auth login --intl --device`, `dws doc info`), concrete JSON fields (`result.fileId`, `linkSourceInfo.nodeId`, `isOrgCurrent=true`, `retryable`, `retry_after_seconds`), and a specific multi-hop URL resolution chain. It is not 5 because key mechanics are delegated to references (e.g. "先执行节点类型探测" names no command, and leaf-Schema lookup procedure lives in schema-usage.md), leaving minor gaps for a cold start. | 4 / 5 |
Workflow Clarity | Multi-step processes are explicitly sequenced with validation checkpoints: a 5-step routing order ending in "向用户追问，不要猜测", a 5-step error shortest-path with retry caps ("最多重试一次"), retry gated on "明确 retryable=true", a confirmation gate ("确认后才加 --yes"), and mandatory post-write verification ("写后验证结果，不凭退出码宣称成功"). This matches the top anchor including feedback loops and stop conditions. | 5 / 5 |
Progressive Disclosure | The body is a clear entry overview with a well-signaled situation→must-read-file table, and all eleven referenced bundle files exist and are one level deep. It is not 5 because three bundle files (references/channel-login.md, references/runtime-contract.md, references/recipes/meta.md) are not reachable from any entry-point link, and the cross-skill link ../dingtalk-misc/references/profile.md is unverifiable within this bundle — minor organization gaps. | 4 / 5 |
Total | 18 / 20 Passed |