Content
86%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, high-signal instruction skill: dense domain constraints, explicit dry-run/confirmation checkpoints for risky operations, and exemplary one-level progressive disclosure to five real reference files. The main gaps are abbreviated (non-copy-paste) command forms and workflows expressed as constraints rather than sequenced steps.
Suggestions
Inline one or two complete, copy-paste-ready command examples (full flags for a common create and connect) so the skill body is executable without opening references.
Convert the unbind→connect and create-failure recovery rules into short numbered sequences with explicit success/failure checkpoints, keeping the constraint list for the rest.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every bullet is dense, domain-specific policy Claude cannot know (e.g., "digitalTagEmployeeProfile.type…仅支持 open_code、local_agent", "deviceId 是稳定设备标识，runtimeBindingId 是服务端绑定 ID") with zero padding and no explanation of known concepts. Not 4: there is no over-explanation anywhere to trim — each token earns its place. | 5 / 5 |
Actionability | Gives concrete commands and flags ("dws dingtalk-tag connect --agent-uuid ... --channel dsh", "先用 --dry-run --format json 展示计划", "connect list/status/stop/restart") plus exact field names. Not 5: commands are abbreviated with '...' and alternatives like 'skill|mcp create|update|delete|list|query' rather than copy-paste-ready full invocations, and complete argument details are delegated to the reference files. | 4 / 5 |
Workflow Clarity | Multi-step flows carry explicit checkpoints — "两步先 dry-run 并汇总确认", "旧机器 connect unbind 成功后，新机器…connect", "connect 失败后…检查 connect status 再恢复", "重试禁止再次执行 create" — including validation for destructive ops (delete 不可逆, confirmation requirements). Not 5: these are stated as constraint bullets rather than a sequenced workflow with feedback loops; the step-by-step sequences themselves live in the reference files, leaving some sequence assembly implicit. | 4 / 5 |
Progressive Disclosure | The ~45-line body is a genuine overview: a routing table plus a purpose-signaled index ("先用 dingtalk-tag-index.md 路由；生命周期读取 manage.md…能力资源读取 capability.md；执行排障读取 run.md"), with all five referenced files present in references/ and only one level deep. Not 4: navigation is explicit (an index file with per-topic pointers), and no content that belongs in a reference file is inlined. | 5 / 5 |
Total | 18 / 20 Passed |