Content
93%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 lean CLI skill body: executable safe-start commands, a complete command table with explicit syntax-discovery pointers, and clear pre-write safety checkpoints. The only gap is the absence of post-write verification or an error-recovery loop for its destructive and batch operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | At roughly 45 lines with zero padding, the body never explains concepts Claude already knows — every line is operational (commands, flags, a command table, syntax pointers). This matches anchor 5: lean, efficient, every token earning its place. | 5 / 5 |
Actionability | The 'Safe start' block gives three copy-paste-ready commands (e.g. 'gog --readonly --account user@example.com contacts search alice --json --wrap-untrusted'), the command table maps all twelve subcommands to purposes, and 'gog contacts <command> --help' plus 'gog schema contacts <command> --json' provide exact syntax — fully executable guidance covering common cases (anchor 5). | 5 / 5 |
Workflow Clarity | The safe-start sequence (auth check → schema → read-only search) plus pre-write checkpoints ('--readonly', '--dry-run before supported writes', 'Confirm the exact account, object, and mutation before any write or delete') satisfy the destructive/batch validation requirement, so the cap of 3 does not apply. It stops short of anchor 5 because there is no post-write verification step (e.g. re-get the contact to confirm the mutation) and no error-recovery feedback loop. | 4 / 5 |
Progressive Disclosure | No bundle files exist, and this under-50-line body is well organized into 'Safe start' and 'Commands' sections — per the simple-skill guidance that merits a 5. Bulk detail is appropriately deferred to '--help' and 'gog schema … --json' rather than inlined, and the one external dependency ('Read ../gog/SKILL.md first for shared auth, output, safety, and live-write rules') is clearly signaled and one level deep. | 5 / 5 |
Total | 19 / 20 Passed |