Conciseness

The body is lean and every token earns its place: a short safe-start code block, five one-line bullets, a five-row command table, and a closing pointer to '--help' and 'gog schema ... --json'. It explains nothing Claude already knows and never pads. It clearly matches anchor 5 rather than 4, which would require some over-explanation to trim — none is present.

Actionability

The safe-start block gives copy-paste-ready commands ('gog auth list --check --json --no-input', 'gog schema maps --json', 'gog --readonly --account user@example.com maps --help') and the table pairs each command with its purpose. It stops short of anchor 5 only because no example invocation of an actual operation is shown (e.g. 'gog maps geocode "1600 Amphitheatre Pkwy"'), leaving real-usage syntax to --help; this is 'mostly executable guidance ... with minor gaps' (4), not vague or pseudocode.

Workflow Clarity

The 'Safe start' section gives a clear sequence (verify auth with '--check', read the schema, inspect help) plus explicit pre-write checkpoints: '--readonly' when mutation is forbidden, '--dry-run before supported writes', and 'Confirm the exact account, object, and mutation before any write or delete'. This matches anchor 4 ('clear sequence with most checkpoints present; minor validation gaps'); it misses 5 because there is no error-recovery feedback loop (e.g. what to do when auth --check fails or a dry-run surfaces a problem) and post-write verification is only implied by the shared-rules pointer.

Progressive Disclosure

At roughly 38 lines this is a simple skill with well-organized sections and no bundle files to disclose, so per the simple-skill scoring note it can score 5 on organization alone. It also pushes detail to clearly-signaled, one-level-deep surfaces: 'Read ../gog/SKILL.md first' for shared rules, 'gog maps <command> --help' and 'gog schema maps <command> --json' for per-command contracts — nothing that belongs in a separate file is inlined.

Specificity

The description "Google Maps operations through gog" names the domain but lists no concrete actions — no geocoding, directions, places search, or distance matrix appear, matching the anchor 'Names the domain but actions are minimal or generic' (e.g. 'Processes PDF files'). A score of 3 would require naming 1-2 concrete operations, which this lacks; a 1 would mean entirely vague language with no domain named, which understates it.

Completeness

The 'what' is present and reasonably clear (Google Maps operations performed through the gog CLI), but there is no 'Use when...' clause or any equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines. It does not reach 4, which requires both 'what' and 'when' with the 'when' merely needing more specificity; and it is above 2 because the 'what' is not vague.

Trigger Term Quality

"Google Maps" is a natural keyword a user would actually say, giving some relevant trigger coverage, but the description misses common variations and synonyms users would phrase requests with — 'directions', 'routes', 'geocoding', 'address to coordinates', 'nearby places', 'maps'. Anchor 3 ('some relevant keywords but missing common variations or synonyms') is the best fit; it is above 2 ('one or two generic keywords') because 'Google Maps' is specific and natural rather than generic.

Distinctiveness Conflict Risk

The description carves out a clear niche — Google Maps, specifically via the 'gog' tool — that is unlikely to trigger for unrelated skills, satisfying 'mostly distinct; minor overlap risk with closely related skills'. It falls short of 5 because the shared 'gog' tool name creates minor overlap with sibling gog-* skills (e.g. other Google services through the same CLI), and without explicit trigger phrases the boundary is drawn only by domain mention.