gog
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
59
48%
Does it follow best practices?
Impact
75%
2.27xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gog/SKILL.mdQuality
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 its supported Google Workspace services but fails to describe any concrete actions or provide explicit trigger guidance for when Claude should use this skill. It reads more like a product tagline than a functional skill description, leaving Claude without clear signals for when to select it over other skills.
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, manage 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 'Google Drive', 'Google Docs', 'send email', 'schedule meeting', 'spreadsheet', '.gsheet'.
| 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 tool covering several 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 (no actions described), 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 the breadth of six different services without specific actions could overlap with individual skills for email, calendar, file management, or spreadsheets. | 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—commands are concrete, complete, and cover a wide range of Google Workspace operations. The main weaknesses are some verbosity (calendar color hex codes, HTML tag explanations Claude doesn't need) and the lack of explicit validation/error-recovery steps for potentially destructive operations like sending emails or modifying sheets.
Suggestions
Remove the HTML tag reference list (Claude knows HTML) and trim the calendar colors to just mention `gog calendar colors` without listing all hex values inline.
Add a brief validation/verification step after sending emails or creating events (e.g., 'verify with `gog gmail search` after sending').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with concrete commands, but the calendar colors section (listing all 11 hex codes) and some HTML tag explanations are unnecessary padding—Claude already knows HTML tags. The email formatting section could be tighter. | 2 / 3 |
Actionability | Excellent actionability—nearly every command is copy-paste ready with concrete flags, arguments, and realistic examples. The heredoc stdin example and sheets JSON examples are particularly well done. | 3 / 3 |
Workflow Clarity | Setup is clearly sequenced (auth credentials → auth add → auth list), and the note to confirm before sending mail/creating events is good. However, there's no explicit validation or error-recovery guidance (e.g., what to do if auth fails, how to verify a send succeeded). | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections (setup, common commands, calendar colors, email formatting, notes), but everything is inline in a single file. The calendar color table and email formatting examples could be split out, and there are no references to external files for advanced usage. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%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
- Hung-Reo/hungreo-openclaw
- Commit
a5bf5e0
- Reviewed
Table of Contents
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.