gog

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

Quality

73%

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

82%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 a dense, executable command reference with clear sectioning and a safety note for destructive actions, scoring high on actionability and organization; minor conciseness and workflow-validation gaps keep it from full marks.

Suggestions

Remove or relocate the 'PilotDeck Migration Note' and source path — this migration metadata is noise unrelated to using the skill.

Add an explicit validation/feedback step for destructive flows (e.g., 'gog gmail drafts create' then review before 'gog gmail drafts send'), rather than relying only on the general confirm note.

Consider moving the full Calendar Colors hex table and the extended command catalog into a reference file linked from SKILL.md to tighten the overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bullet-listed commands with minimal over-explanation, though the verbatim Calendar Colors hex table and the trailing PilotDeck migration note are padding that could be trimmed.	4 / 5
Actionability	Commands are fully executable and copy-paste ready across Gmail, Calendar, Drive, Contacts, Sheets, and Docs, with concrete examples (send variants, heredoc stdin, HTML body, sheets update JSON) covering the common cases.	5 / 5
Workflow Clarity	Setup is clearly sequenced as a one-time flow and the Notes section adds a 'Confirm before sending mail or creating events' checkpoint, but there is no explicit validate→fix→retry feedback loop for destructive operations.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections (Setup, Common commands, Calendar Colors, Email Formatting, Notes) with no external bundle files needed, though the skill is slightly long for pure inline reference and some material (color table, full command catalog) could live in separate files.	4 / 5
	Total	17 / 20 Passed

Description

65%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 is concise and clearly scoped to Google Workspace services with strong distinctiveness, but it omits explicit "when to use" trigger guidance and lists services rather than concrete actions.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill, e.g., 'Use when the user wants to send email, manage calendar events, or work with Google Drive/Sheets/Docs via CLI.'

Replace the generic 'CLI for' framing with a few concrete actions (e.g., 'send Gmail, create Calendar events, search Drive, read and update Sheets, export Docs').

Include common synonyms/extensions (email, spreadsheets, .xlsx, Google Docs) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Google Workspace CLI") and comprehensively lists six target services (Gmail, Calendar, Drive, Contacts, Sheets, Docs), but it states no concrete actions (e.g., send mail, create events) — only the generic "CLI for".	3 / 5
Completeness	It gives a clear "what" (a CLI covering six Google Workspace services) but no "when"/"Use when..." trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	It includes natural product names users say (Gmail, Calendar, Drive, Contacts, Sheets, Docs) with good coverage, but misses common synonyms and file extensions such as email, spreadsheets, .xlsx, or Google Docs.	4 / 5
Distinctiveness Conflict Risk	The Google Workspace scope with named services (Gmail, Calendar, Drive, Contacts, Sheets, Docs) is a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	15 / 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: 9a33f4d

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.