gog

Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/gog/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an excellent, dense command reference with fully executable examples and a clear setup sequence, scoring top marks on actionability. It is held back by missing validation checkpoints for destructive operations, non-header section formatting, inlined reference material, and an irrelevant migration note.

Suggestions

Add validation/feedback steps for destructive and batch operations, e.g. 'Before sheets clear, run gog sheets get on the target range to confirm it is the right data' and 'After gmail send, check the sent thread with gog gmail search in:sent' — this is required to lift workflow clarity above 3.

Remove the 'PilotDeck Migration Note' section and the hex color table (the 'gog calendar colors' command already provides it), trimming the body toward anchor 4-5 conciseness.

Convert section labels to proper markdown headers (## Setup, ## Common commands, ## Email formatting, ## Notes) and move the full command catalog or color reference into a references/ file to improve organization and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The command listings are lean, but the 11-entry hex color table duplicates what 'gog calendar colors' already prints, and the 'PilotDeck Migration Note' (source path, review status, platform metadata) is review-process chatter irrelevant to using the skill. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than anchor 4, since roughly 15% of the body is unnecessary.	3 / 5
Actionability	Every entry is a complete, copy-paste-ready command with real flags and placeholders, including heredoc/stdin and HTML email examples, the full OAuth setup sequence, and scripting notes ('--json plus --no-input'). This matches anchor 5: fully executable commands covering the common cases.	5 / 5
Workflow Clarity	Setup is sequenced (auth credentials → auth add → auth list) and a 'Confirm before sending mail or creating events' checkpoint exists, but destructive and batch operations ('gmail send', 'sheets clear', 'sheets update', 'calendar create') have no validation or feedback loops, such as verifying a send succeeded or checking a sheet before clearing. Per the judging guideline, missing validation in destructive/batch operations caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Sections exist (Setup, Common commands, Calendar Colors, Email Formatting, Notes) but most are plain text lines rather than markdown headers, and reference-grade material (the full command catalog and color table) is inlined in a 105-line single file with no bundle files to offload it. This fits anchor 3 ('some structure but could be better organized') rather than anchor 4's well-signaled structure.	3 / 5
	Total	14 / 20 Passed

Description

56%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names the domain and all six services clearly and with good natural keywords, but it specifies no concrete actions and has no 'when to use' trigger clause. It functions as a product label rather than an invocable skill description.

Suggestions

Add concrete actions to the description, e.g. 'Search and send Gmail, create and update Calendar events, search Drive, read and write Sheets, and export Docs' to lift specificity from 2 to 4.

Add an explicit trigger clause such as 'Use when the user asks about Gmail messages, Calendar events, Drive files, Contacts, Sheets data, or Docs content, or mentions gog.' to satisfy the 'when' half of completeness.

Include common user-facing synonyms (email, spreadsheet, Google Docs, Google Sheets) alongside the product names to improve trigger term coverage and reduce misses on natural phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain ('Google Workspace CLI') and all six services but states no concrete actions — no search/send/create verbs appear. It matches anchor 2 ('Names the domain but actions are minimal or generic') and falls short of anchor 3, which requires 1-2 concrete actions.	2 / 5
Completeness	There is a clear 'what' (a CLI covering the six named services) but no 'when' — no 'Use when...' clause or equivalent trigger guidance at all. Per the judging guideline, a missing 'Use when' clause caps completeness at 3; it cannot be 4 because the 'when' is entirely absent, not merely imprecise.	3 / 5
Trigger Term Quality	'Gmail', 'Calendar', 'Drive', 'Contacts', 'Sheets', 'Docs', and 'Google Workspace' are natural terms users would say. Missing common variations such as 'email', 'spreadsheet', 'Google Docs', or file extensions, so it fits anchor 4 rather than anchor 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	A distinct niche (Google Workspace CLI across six services) with clear brand-specific triggers. Minor overlap risk remains with dedicated per-service skills (e.g., a Gmail-only or Drive-only skill), which keeps it below anchor 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: OpenBMB/PilotDeck
Path: skills/gog/SKILL.md
Commit: 66bfd09

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.