Content
73%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.
The body delivers exceptionally concrete, executable guidance with well-sequenced workflows and robust validation/error-recovery loops, and its reference navigation is genuinely on-demand with all paths resolving. Its main weaknesses are token efficiency — verbatim duplicated rules, massive run-on paragraphs, and specialized contract material inlined in the root file — which keep it well below ideal conciseness.
Suggestions
Deduplicate the repeated bullets in 执行约束 and 记录稳定约束 (write read-back, hasMore/partial_success checks, timestamp reuse, JSON field reuse) into a single occurrence each.
Move the specialized 表单分享用法回答契约 and 返回值评审专用查询 sections (~80 lines used only in narrow scenarios) into a dedicated reference file, keeping only the routing rule in SKILL.md.
Break the longest rule paragraphs (e.g. 链接保真必经步骤, the Golden Route psql paragraph) into bullet lists or route them to the existing references to cut root-file tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~47KB body contains verbatim duplicated bullet blocks ("新增或更新只使用真实返回的 ID 回读;写入效果未知时回读,不重放成功批次" and "全量查询检查 hasMore,批量写检查最终状态" each appear twice, as do the timestamp-reuse and JSON-reuse rules) and very long run-on rule paragraphs. While it avoids explaining concepts Claude already knows, the volume and repetition make it noticeably verbose rather than mostly efficient. | 2 / 5 |
Actionability | Guidance is fully executable: exact commands with placeholders ("dws aitable +url-resolve --url <URL>"), exact JSON configs ("{\"currencyType\":\"CNY\",\"formatter\":\"FLOAT_2\"}"), precise schema-query invocations ("dws schema --cli-path ... --compact --format json"), and copy-paste-ready two-line response templates for the form-share usage case. | 5 / 5 |
Workflow Clarity | Multi-step processes are explicitly sequenced with validation checkpoints and feedback loops: the psql flow (discover tables → inspect columns → LIMIT 3 minimal query → formal query), post-write independent read-back by real ID, token-based write-result reconciliation, INVALID_CURSOR recovery (discard all, requery without --cursor), and independent confirmation gates for destructive operations. | 5 / 5 |
Progressive Disclosure | The on-demand loading table maps trigger conditions to specific reference files, all of which exist in the bundle and are effectively one level deep. However, the root file inlines ~80 lines of highly specialized form-share/review contracts that belong in a reference, and reference placement is inconsistent (references/aitable-record-ops.md and aitable-section.md at the root while siblings live in references/aitable/). | 4 / 5 |
Total | 16 / 20 Passed |