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 ./openclaw/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 include explicit trigger guidance ('Use when...'). It reads more like a product tagline than a skill description that would help Claude reliably select it from a large skill library.
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 Google Drive, manage contacts, edit Google Sheets, or work with Google Docs.'
List concrete actions for each service, e.g., 'Send and read Gmail messages, create and manage Calendar events, upload and share Drive files, 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 highly actionable, copy-paste ready commands covering all major Google Workspace services. Its main weaknesses are some unnecessary content (calendar color hex codes, HTML tag explanations) that Claude already knows, and the lack of explicit validation workflows for destructive operations like sending emails or modifying spreadsheets. The flat structure works reasonably well for a reference document but could benefit from splitting detailed sections into separate files.
Suggestions
Remove the calendar color hex code listing—Claude can retrieve these via `gog calendar colors` as already noted, and the hex values waste tokens.
Remove the HTML tag reference (p, br, strong, em, a, ul/li)—Claude already knows HTML.
Add explicit verification steps for destructive operations, e.g., 'After sending, verify with `gog gmail search` to confirm delivery' or 'After sheets update, verify with `gog sheets get`'.
| 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 and the colors can be retrieved via the listed command. | 2 / 3 |
Actionability | Highly actionable with copy-paste ready commands for every operation—setup, Gmail, Calendar, Drive, Sheets, Docs. Includes concrete examples with real flags and arguments, plus multi-line heredoc examples for email formatting. | 3 / 3 |
Workflow Clarity | Setup is clearly sequenced (auth credentials → auth add → auth list), and the 'confirm before sending' note is present, but there's no explicit validation/verification workflow for potentially destructive operations like sending emails or modifying sheets. The skill is mostly a command reference rather than a workflow guide. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections (Setup, Common commands, Calendar Colors, Email Formatting, Notes) which is good, but the calendar color table and detailed HTML formatting guidance could be split into separate reference files. Everything is inline in one document. | 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
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.