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

Content

64%

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

A solid CLI reference skill with excellent actionability—nearly every command is copy-paste ready with realistic examples. The main weaknesses are some unnecessary verbosity (color hex codes, HTML tag explanations) and lack of explicit validation steps after setup or before destructive operations like sending emails. The structure is reasonable for a single-file skill but could benefit from trimming redundant information.

Suggestions

Remove the Calendar Colors hex code listing since `gog calendar colors` already outputs them—just reference the command.

Remove the HTML tags explanation (Claude already knows HTML) and keep only the concrete example.

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

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 in Email Formatting also explains things Claude already knows.	2 / 3
Actionability	Excellent actionability throughout—every command is copy-paste ready with concrete flags, arguments, and realistic examples. The setup sequence, Gmail send variants, Sheets operations, and heredoc examples are all fully 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.	2 / 3
Progressive Disclosure	Content is organized into logical sections (Common commands, Calendar Colors, Email Formatting, Notes) which is good, but the skill is somewhat long and monolithic. The Calendar Colors reference table and detailed email formatting examples could be split into separate files for a cleaner overview, though for a single-file skill without bundle support this is acceptable.	2 / 3
	Total	9 / 12 Passed

Description

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 lists the Google Workspace services it covers, which provides reasonable keyword coverage. However, it lacks concrete action descriptions and has no 'Use when...' clause, making it incomplete for skill selection purposes. It reads more like a product tagline than a functional skill description.

Suggestions

Add concrete actions for each service, e.g., 'Send and search emails in Gmail, create and manage Calendar events, upload and share files in Drive, manage Contacts, read and write Sheets data, create and edit Docs.'

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to interact with Google Workspace services like sending emails, scheduling meetings, managing files in Drive, or working with Google Sheets or Docs.'

Include common user-facing trigger terms and variations such as 'Google Drive', 'Google Docs', 'Google Sheets', 'send email', 'schedule meeting', 'upload file' to improve matching.

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 it is (a Google Workspace CLI) but has no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also weak (no concrete actions), so this scores a 1.	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 variations like 'Google Drive', 'Google Docs'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Google Workspace CLI' and specific service names provides some distinctiveness, but without concrete actions it could overlap with other Google-related skills or generic document/email/calendar skills.	2 / 3
	Total	7 / 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: deepgram/dglabs-deepclaw
Commit: ec8d4f8

Reviewed: about 1 month 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.