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.
An exemplarily lean CLI reference: all guidance is executable, organized by command, and free of padding. The only weakness is the absence of validation/verification checkpoints around its batch and destructive operations (update --all --force, publish), which caps workflow clarity.
Suggestions
Add a verification step after batch updates, e.g. run "clawhub list" (or "clawhub list --json") after "clawhub update --all" to confirm the installed versions and catch failed upgrades.
Frame "clawhub whoami" as a pre-publish checkpoint in the Publish section so auth status is confirmed before an outward-facing release.
Briefly note what "clawhub update --force" overrides and when it is safe to use, since force-upgrading all skills without confirmation is the riskiest documented operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is pure command listings under terse headers ("Search", "Publish", "Notes") with zero explanation of concepts Claude already knows; every token earns its place, matching the lean-and-efficient anchor. It is clearly not the level-4 case since there is no over-explanation to trim at all. | 5 / 5 |
Actionability | Every example is a copy-paste-ready executable command covering the common cases, including flag variants ("clawhub install my-skill --version 1.2.3", "clawhub update --all --no-input --force") and a fully populated publish invocation. This matches the fully-executable top anchor with no gaps. | 5 / 5 |
Workflow Clarity | Per-command usage is unambiguous, but the skill documents batch and potentially destructive operations ("clawhub update --all --no-input --force", "clawhub publish") with no validation or verification steps such as confirming state with "clawhub list" or checking "clawhub whoami" before publishing. Per the rubric, missing feedback loops for batch operations caps workflow clarity at 3 even though each single command is clear. | 3 / 5 |
Progressive Disclosure | The body is under 50 lines, needs no external references, and is organized into clear per-command sections (Install, Auth, Search, Update, List, Publish, Notes). This satisfies the rubric's short-skill provision for a top score; no bundle files exist that should have been referenced (references/, scripts/, and assets/ are absent). | 5 / 5 |
Total | 18 / 20 Passed |