gog

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

2.27x

Quality

48%

Does it follow best practices?

Impact

75%

2.27x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gog/SKILL.md

Quality

Discovery

32%

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 identifies the tool and the Google services it covers, which provides reasonable keyword coverage, but it reads more like a product tagline than a skill description. It lacks concrete actions (what can be done with each service) and entirely omits a 'Use when...' clause, making it difficult for Claude to know precisely when to select this skill over others.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks to send emails, manage calendar events, upload or search Drive files, manage contacts, edit spreadsheets, or work with Google Docs.'

List specific concrete actions for each service, e.g., 'Send and read Gmail messages, create and list Calendar events, upload and search Drive files, manage Contacts, read and write Sheets data, create and edit Docs.'

Include common natural-language trigger terms users might say, such as 'send email', 'schedule meeting', 'upload to Drive', 'Google Sheets', 'Google Docs', etc.

Dimension	Reasoning	Score
Specificity	Names the domain (Google Workspace CLI) and lists the specific services (Gmail, Calendar, Drive, Contacts, Sheets, Docs), but does not describe concrete actions like 'send emails', 'create events', 'upload files', etc.	2 / 3
Completeness	Describes what at a high level (Google Workspace CLI for various services) but completely lacks any 'Use when...' clause or explicit trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also quite thin, a score of 1 is appropriate.	1 / 3
Trigger Term Quality	Includes good product-name keywords (Gmail, Calendar, Drive, Sheets, Docs, Google Workspace) that users would naturally mention, but misses common action-oriented terms like 'send email', 'schedule meeting', 'upload file', 'create spreadsheet', or file extensions.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Google Workspace CLI' and specific Google services provides some distinctiveness, but without concrete actions, it could overlap with other Google-related or document/email skills. The CLI aspect helps differentiate somewhat.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

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

This is a solid CLI reference skill with excellent actionability—nearly every command is concrete and copy-paste ready. Its main weaknesses are moderate verbosity (calendar color hex codes, HTML tag explanations that Claude already knows) and lack of explicit validation steps in workflows. The organization is functional but could benefit from trimming redundant information.

Suggestions

Remove the Calendar Colors hex code listing—the command `gog calendar colors` already provides this, and Claude doesn't need a static lookup table.

Remove the HTML tags reference (p, br, strong, em, a, ul/li)—Claude already knows HTML and this wastes tokens.

Add a validation step after auth setup, e.g., 'Verify: `gog auth list` should show your account with all services enabled.'

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the Calendar Colors section listing all 11 hex codes is unnecessary padding—Claude doesn't need a color lookup table when `gog calendar colors` already provides it. The HTML tags list and some email formatting guidance also explain things Claude already knows.	2 / 3
Actionability	Excellent actionability throughout—every command is copy-paste ready with concrete flags, arguments, and realistic examples. The heredoc stdin example and sheets JSON values are particularly well-specified and executable.	3 / 3
Workflow Clarity	The setup sequence is clear (auth credentials → auth add → auth list), but there's no validation checkpoint after setup (e.g., verify auth works). The note to 'confirm before sending mail or creating events' is mentioned but not integrated into a workflow with explicit checkpoints. For a CLI reference skill this is acceptable but not exemplary.	2 / 3
Progressive Disclosure	Content is organized into logical sections (Setup, Common commands, Calendar Colors, Email Formatting, Notes) which is good, but the Calendar Colors and Email Formatting sections add significant inline bulk that could be split into separate reference files. For a single-file skill with no bundle, the structure is reasonable but the inline detail level is borderline monolithic.	2 / 3
	Total	9 / 12 Passed

Validation

72%

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 — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	8 / 11 Passed

Repository: attilaczudor/Test
Commit: b4fc4af

Reviewed: about 2 months 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.