Content
100%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 exemplary SKILL.md body: dense, unambiguous, and honest about validation scope and delivery boundaries. Structure is a routing layer over a well-organized one-level-deep reference bundle, with executable commands and a complete construction example. No notable weaknesses found.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean, imperative, and assumes Claude's competence throughout — no padding, no explanation of what JSON, DingTalk, or card protocols are. The version strings ("v1.0", "1.0", V0.8) are functional protocol constants the agent must write into files, not time-sensitive drift, so they cost nothing. | 5 / 5 |
Actionability | Concrete copy-paste commands cover the common cases: `dws aicard explain Tabs --format json`, `dws aicard lint --file card.a2ui.json --format json`, full `update-a2ui-card --biz-id <bizId> --content <message-strings> --flow-status <state>` invocations, and a complete executable three-message JSON array for card construction. The send command's flags and JSON-encoding requirement are fully specified. | 5 / 5 |
Workflow Clarity | The route-by-intent table sequences entry points, the scenario table maps each case (new card, host-created surface, existing-card update) to its required messages and preflight mode, and validation checkpoints are explicit ("Check exit status and `data.valid` plus `data.preflight.valid`"). Error-recovery feedback loops are present: "An uncertain result must be checked before another create; do not resend automatically" and "inspect `updateWarning` and the receipt; do not recreate automatically", plus readback verification after sending. | 5 / 5 |
Progressive Disclosure | The body is a pure routing overview with two navigation tables pointing to a well-split bundle; every referenced path was verified to exist (design.md with #root-surface and #headers-and-card-insets anchors, patterns/progress.md#examples-and-replay, all six pattern files, three index files, protocol/examples/README.md). References are one level deep, and the single indirection (the example index) is explicitly framed as a chooser with "Read a named example directly" guidance. | 5 / 5 |
Total | 20 / 20 Passed |