gog
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 75%
↑ 2.27xAgent success when using this skill
Validation for skill structure
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 scope (Google Workspace CLI) and lists covered services, which provides moderate specificity. However, it lacks concrete action verbs describing what operations can be performed and completely omits trigger guidance for when Claude should select this skill. The description reads more like a product label than actionable skill guidance.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when user mentions Gmail, Google Calendar, Google Drive, or asks to send emails, schedule meetings, manage files in Drive'
Include concrete actions for each service: 'Send and read emails, create calendar events, upload/download Drive files, manage contacts, read/write spreadsheets, edit documents'
Add natural language variations users might say: 'google email', 'gcal', 'google spreadsheet', 'gdocs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Workspace CLI) and lists specific services (Gmail, Calendar, Drive, Contacts, Sheets, Docs), but doesn't describe concrete actions like 'send emails', 'create events', or 'upload files'. | 2 / 3 |
Completeness | Only describes what services are covered, 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 good product names users might mention (Gmail, Calendar, Drive, Sheets, Docs), but misses natural action terms like 'email', 'schedule meeting', 'upload', 'spreadsheet', or 'google docs'. | 2 / 3 |
Distinctiveness Conflict Risk | The Google Workspace focus provides some distinctiveness, but 'Sheets' and 'Docs' could overlap with generic spreadsheet or document skills without clearer trigger boundaries. | 2 / 3 |
Total | 7 / 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 high-quality CLI reference skill that excels at conciseness and actionability. It provides comprehensive, copy-paste ready commands organized into clear sections. The main weakness is the lack of explicit validation workflows for potentially destructive operations like sending emails or creating events.
Suggestions
Add explicit validation workflow for email sending (e.g., 'Create draft first with `gog gmail drafts create`, verify with `gog gmail drafts get <id>`, then send with `gog gmail drafts send <id>`')
Include a verification step example for calendar events (e.g., how to list/confirm an event after creation)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient - pure command reference with no unnecessary explanation of what Gmail/Calendar/etc. are. Every line provides actionable command syntax. | 3 / 3 |
Actionability | Fully copy-paste ready commands with concrete examples including flags, arguments, and realistic placeholders. The heredoc and HTML examples are complete and executable. | 3 / 3 |
Workflow Clarity | Setup steps are clear and sequential, but the skill lacks validation checkpoints. 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 | Well-organized into logical sections (Setup, Common commands, Calendar Colors, Email Formatting, Notes). For a CLI reference skill of this scope, the flat structure with clear headers is appropriate - no need for external file references. | 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 | |
- 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.