Content
68%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 well-organized CLI reference with excellent progressive disclosure into per-service files and nearly complete, executable command coverage. The main gaps are the absence of validation steps around destructive and batch operations (capping workflow clarity), a few non-executable placeholders, and an orphaned bundle file.
Suggestions
Add validation guidance to destructive and batch operations — e.g., before `gog drive delete`/`gog sheets clear`, verify the target with `gog drive get <fileId>` or `gog --dry-run drive delete <fileId>`, and confirm batch results after the download/export loop. This would lift the workflow_clarity cap.
Fix the executable gaps: show how to resolve the version in the manual-install tarball URL (e.g., fetch the release tag first), and align the error-table's `gog auth setup` with the authentication commands actually documented (`gog auth credentials set` / `gog auth add`).
Link `references/permissions.md` from SKILL.md (e.g., from the Agent Safety or Drive section) so it is discoverable, and drop or trim the Quick Reference block that duplicates commands already shown in the Commands sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is command-first with terse comments and almost no over-explanation ("All commands support `--json` for structured output and `--plain` for TSV"), assuming Claude's competence. Not 5 because the Quick Reference block duplicates commands restated verbatim in the Commands sections (e.g., `gog gmail search "is:unread"`, `gog drive search "quarterly report"`, `gog sheets get`, `gog slides info`), and the Examples section repeats `freebusy` from the Calendar section. | 4 / 5 |
Actionability | Nearly every command is copy-paste ready with concrete arguments, and examples cover common cases end-to-end. Not 5 because of minor gaps: the manual-install URL contains an unresolved `gogcli_VERSION_linux_amd64.tar.gz` placeholder with no instruction for resolving the version, and the error-handling table cites `gog auth setup` while the Authentication section only shows `auth credentials set`/`auth add`/`auth doctor`. | 4 / 5 |
Workflow Clarity | The auth sequence has an explicit validation checkpoint (`gog auth doctor`) and the exit-code table with retryability is a feedback loop, but the skill exposes destructive operations (`drive delete`, `gmail trash`, `calendar delete`, `sheets clear`) and a batch loop ("Download recent documents") with no verify-before/verify-after steps. Per the rubric, missing validation in destructive/batch contexts caps this at 3 — the `--dry-run` and `--readonly` flags exist in the Agent Safety section but are never wired into any destructive workflow. | 3 / 5 |
Progressive Disclosure | The SKILL.md is a genuine overview with clearly signaled one-level-deep per-service references ("See [gmail.md](references/gmail.md) for the full command reference"), and the linked files all exist. Not 5 because scoring against the actual bundle reveals `references/permissions.md` (179 lines) is orphaned — linked from neither SKILL.md nor any reference file — and the Docs Workflows subsection uses a misplaced `####` heading level under `### Google Docs`. | 4 / 5 |
Total | 15 / 20 Passed |