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 lists the Google Workspace services it covers, which provides reasonable keyword coverage. However, it lacks concrete action descriptions and entirely omits a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others. The breadth of six services without specific capabilities makes it feel more like a product tagline than a skill description.

Suggestions

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

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

Include common natural-language variations users might say, such as 'email', 'schedule a meeting', 'spreadsheet', 'google drive', 'upload file'.

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 a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores 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 variations like 'email', 'spreadsheet', 'google docs', 'schedule meeting', or action-oriented terms users would say.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Google Workspace CLI' and specific service names provides some distinctiveness, but the broad scope covering six different services could overlap with more specialized skills for email, calendars, spreadsheets, or file management.	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, highly actionable CLI reference skill with excellent concrete examples covering all major gog subcommands. Its main weaknesses are some verbosity in sections like Calendar Colors and Email Formatting (explaining HTML tags Claude already knows), and the lack of explicit validation/verification steps after destructive or important operations like sending emails or creating events.

Suggestions

Remove the full calendar color hex code listing and just reference `gog calendar colors`; similarly, remove the HTML tags explanation since Claude already knows HTML.

Add explicit verification steps after key operations (e.g., after sending email, check with `gog gmail search` to confirm; after creating calendar events, list events to verify).

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the Calendar Colors section with all 11 hex codes is verbose and could be replaced by just referencing the `gog calendar colors` command. The HTML tags list and some email formatting guidance also explain things Claude already knows.	2 / 3
Actionability	Excellent actionability — nearly every command is copy-paste ready with concrete flags, arguments, and realistic examples. The setup steps, 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 are no validation checkpoints after operations. The note to 'confirm before sending mail or creating events' is mentioned but not integrated into a workflow with explicit verification steps.	2 / 3
Progressive Disclosure	Content is organized into logical sections (Common commands, Calendar Colors, Email Formatting, Notes) which is good, but the inline calendar color table and detailed HTML formatting guidance could be split into separate reference files. For a skill of this length, some content bloats the main file unnecessarily.	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: deepgram/dglabs-deepclaw
Commit: ec8d4f8

Reviewed: about 6 hours 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.