Content
87%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 tight, fully-executable CLI reference with excellent conciseness and actionability. Its main weakness is the absence of validation/verification steps around the batch update --all and publish operations, which the rubric caps at workflow clarity 3.
Suggestions
Add a verification step before destructive/batch operations, e.g. run `clawhub list` (and `clawhub whoami` before publish) to confirm state before running `clawhub update --all --force` or `clawhub publish`.
Show an error-recovery loop for publish (e.g., re-run with corrected flags if the slug/version is rejected) so the workflow has a feedback checkpoint.
Mark `clawhub update --all --force` and `clawhub publish` as destructive/batch and recommend confirming the target scope first.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean command reference with no concept over-explanation; every line is an executable command or a compact note, assuming Claude's competence. | 5 / 5 |
Actionability | Fully executable, copy-paste-ready commands covering the common cases including version flags, --all, --force, and a complete publish invocation with all required flags. | 5 / 5 |
Workflow Clarity | Commands are loosely sequenced by lifecycle but batch/destructive operations ("clawhub update --all --force", "clawhub publish") appear with no validation or verification checkpoint, which caps workflow clarity at 3 per the rubric. | 3 / 5 |
Progressive Disclosure | Under 50 lines, no external bundle files needed, and well-organized into clearly labeled sections (Install, Auth, Search, Update, List, Publish, Notes), qualifying for the simple-skill exception. | 5 / 5 |
Total | 18 / 20 Passed |