gog
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
71
Quality
67%
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
47%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 effectively lists the Google Workspace services covered, providing good trigger terms for service names. However, it lacks concrete action descriptions (what can you DO with these services?) and critically missing a 'Use when...' clause that would help Claude know when to select this skill over others.
Suggestions
Add a 'Use when...' clause specifying triggers like 'send email', 'schedule meeting', 'upload to Drive', 'read spreadsheet', 'create document'
List specific actions for each service (e.g., 'Send and read emails, schedule calendar events, upload/download Drive files, manage contacts, read/write spreadsheets, create/edit documents')
Include common user phrasings like 'check my email', 'add to my calendar', 'save to Google Drive'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Workspace CLI) and lists the services covered (Gmail, Calendar, Drive, Contacts, Sheets, Docs), but doesn't describe what concrete actions can be performed with these services. | 2 / 3 |
Completeness | Only answers 'what' at a high level (it's a CLI for Google services) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Gmail', 'Calendar', 'Drive', 'Contacts', 'Sheets', 'Docs', and 'Google Workspace' - these are all terms users naturally use when requesting help with these services. | 3 / 3 |
Distinctiveness Conflict Risk | The Google Workspace focus provides some distinctiveness, but without specifying actions, it could overlap with other Google-related skills or general document/email handling skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted CLI reference skill that efficiently documents the gog tool with concrete, executable examples. The command reference format is appropriate and token-efficient. The main weakness is the lack of explicit validation workflows for destructive operations like sending emails or creating events, though the skill does mention confirmation as a note.
Suggestions
Add an explicit validation workflow for email sending (e.g., 'Create draft first with `gog gmail drafts create`, verify content, then send with `gog gmail drafts send`')
Include a brief troubleshooting section or error recovery guidance for common OAuth or permission issues
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting commands in a reference-style format without explaining what Gmail, Calendar, or Drive are. Every line provides actionable command syntax or essential notes. | 3 / 3 |
Actionability | All commands are copy-paste ready with concrete examples including flags, arguments, and realistic placeholders. The heredoc and HTML examples are fully executable. | 3 / 3 |
Workflow Clarity | Setup steps are clearly sequenced, but the skill lacks validation checkpoints for potentially problematic operations. The 'Confirm before sending mail or creating events' note is mentioned but not integrated into a workflow with explicit verification steps. | 2 / 3 |
Progressive Disclosure | For a CLI reference skill of this scope, the content is well-organized into logical sections (Setup, Common commands, Calendar Colors, Email Formatting, Notes) without needing external file references. Navigation is clear and content is appropriately structured. | 3 / 3 |
Total | 11 / 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
50ef2f3
- 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.