Content
86%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 skill body: terse, well-structured, with copy-paste startup commands, a complete command table, and smart progressive disclosure that pushes per-command detail to the CLI's help/schema system. The main gaps are the lack of worked examples for common operations and no post-write verification step for destructive commands.
Suggestions
Add one or two worked command examples for the most common operations (e.g., an upload, a share, or a search invocation) so common cases don't require a help lookup.
Include a post-write verification step (e.g., re-checking permissions or metadata after a delete/share/bulk operation) to close the feedback loop for destructive and batch commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean throughout — a three-command 'Safe start' block, one-line purposes in the command table, and no explanation of concepts Claude already knows; every token earns its place, matching the anchor-5 example. | 5 / 5 |
Actionability | The Safe start commands ("gog auth list --check --json --no-input", "gog schema drive --json", "gog --readonly ... drive ls ...") are copy-paste ready, and per-command contracts are delegated to "gog drive <command> --help" and "gog schema drive <command> --json". However, no worked invocations are given for the most common operations (upload, share, search), leaving minor gaps versus the fully-executable coverage of a 5. | 4 / 5 |
Workflow Clarity | A clear startup sequence with an auth validation checkpoint is present, and destructive/batch operations have explicit checkpoints ("--dry-run before supported writes", "Confirm the exact account, object, and mutation before any write or delete"), so validation is not missing and the cap of 3 does not apply. What keeps it at 4 rather than 5 is the absence of post-write verification or an error-recovery loop for risky operations like "delete --permanent" and "bulk". | 4 / 5 |
Progressive Disclosure | The body is a clean overview: the single file reference ("Read ../gog/SKILL.md first for shared auth, output, safety, and live-write rules") is well-signaled and one level deep, and bulk per-command detail is appropriately deferred to the CLI's own "--help" / "gog schema" layer rather than inlined, making navigation easy with no nested references. | 5 / 5 |
Total | 18 / 20 Passed |