Content
82%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.
This is a strong, highly actionable skill body: concrete executable commands dominate, safety guards are woven into examples rather than stated abstractly, and fragile flows include real validation and recovery guidance. The remaining improvements are structural — moving the deep reauth procedure out of the overview — and tightening a few explanatory paragraphs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with commands and non-obvious operational gotchas (the mandatory `-J` flag, UTF-16 range resolution, silent scope narrowing) with no padding about concepts Claude already knows. A few sections could still be tightened, such as the `--fields`/`--select` aliasing rules and the length of the browser-reauth walkthrough, matching anchor 4 rather than the lean anchor 5. | 4 / 5 |
Actionability | Nearly every section is copy-paste-ready: Fast Path diagnostics, guarded command invocations, complete read examples across gmail/calendar/drive/docs/sheets/contacts, write commands including tab and range targeting, first-class reply commands, and discovery commands. Placeholders like `<messageId>` are appropriately parameterized and the common cases are covered. | 5 / 5 |
Workflow Clarity | The reauth workflow is explicitly sequenced with validation checkpoints and error-recovery loops (verify `response_type` before using the URL, require both account validity and scope breadth, restart the CLI leg rather than reusing a stale URL). The writes section has protective checkpoints (--dry-run, --readonly, --force discipline, trash over batch delete) but post-write verification for batch/destructive operations is advisory rather than an explicit checkpoint, so it fits anchor 4. | 4 / 5 |
Progressive Disclosure | Flag-level detail is delegated to runtime discovery (`gog schema`, `--help`, generated `docs/commands/`) with a clearly signaled Docs section listing one-level-deep paths, and sections are well organized. However, the ~70-line browser-driven reauth subsection is specialized procedural content inlined in the overview that would fit better in a separate reference file, matching anchor 4 rather than 5. | 4 / 5 |
Total | 17 / 20 Passed |