gog

Search, send, and draft Gmail messages, manage Google Calendar events, query Drive and Contacts, and read/write Google Sheets and Docs via the gog CLI. Use when the user asks to send email, check their calendar, search Drive files, read a spreadsheet, or export a Google Doc.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is gog in openclaw/openclaw

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, executable command reference with good section structure. Weaker spots are minor token waste from re-teaching basic HTML and restating send variants, plus the absence of verification loops for destructive operations like sending mail.

Suggestions

Drop or compress the basic HTML tag primer ('<p> for paragraphs, <br> for line breaks...') — Claude already knows HTML; keep only the gog-specific guidance like when to prefer --body-html.

Consolidate the send/draft/reply variants so each --body-file / --body-file - / --body-html form appears once instead of being repeated across Common commands and Email Formatting.

Add a brief verification step for destructive operations, e.g. review a draft with 'gog gmail drafts list' or show the created event before confirming, and consider moving the calendar color hex table to a references/ file.

Dimension	Reasoning	Score
Conciseness	The body is a lean command catalog, but 'HTML tags: <p> for paragraphs, <br> for line breaks, <strong> for bold, <em> for italic' re-explains basic HTML Claude already knows, and the Email Formatting send variants partially duplicate the Common commands entries. Efficient with minor over-explanation to trim, so 4 rather than 5.	4 / 5
Actionability	Every entry is a fully executable, copy-paste-ready gog command with concrete flags and placeholders (e.g. 'gog gmail send --to a@b.com --subject "Hi" --body-file -', the heredoc example, and the sheets --values-json forms), covering the common cases across all services.	5 / 5
Workflow Clarity	Setup is clearly sequenced (auth credentials → auth add → auth list) and 'Confirm before sending mail or creating events' is an explicit checkpoint for the destructive operations, but there is no post-action verification (e.g. checking a draft before 'drafts send' or confirming an event was created). Clear sequence with minor validation gaps, not the 3 anchor where checkpoints are merely implicit.	4 / 5
Progressive Disclosure	No bundle files exist, and the body is well-organized into clear sections (Setup, Common commands, Calendar Colors, Email Formatting, Notes). The 11-entry color hex table and the exhaustive command catalog are borderline reference material inlined in a ~90-line body — good structure with minor placement gaps, so 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete, comprehensive action list paired with an explicit 'Use when' clause full of natural trigger phrases. The only weakness is that a few common trigger synonyms (Gmail, inbox, meeting, contacts) are not covered.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Search, send, and draft Gmail messages, manage Google Calendar events, query Drive and Contacts, read/write Google Sheets and Docs' — covering every gog domain comprehensively, matching the top anchor rather than the 4 anchor which expects coverage gaps.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated action list) and 'when' via the literal 'Use when the user asks to...' clause with concrete trigger phrases, matching the 5 anchor exactly.	5 / 5
Trigger Term Quality	Triggers like 'send email', 'check their calendar', 'search Drive files', 'read a spreadsheet', or 'export a Google Doc' are natural user phrases, but common variations such as 'Gmail', 'inbox', 'meeting', or 'contacts' are absent. Good coverage with a few natural terms missing, so 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The 'via the gog CLI' qualifier and service-specific triggers (Gmail, Calendar, Drive, Sheets, Docs) carve a clear niche with minimal overlap risk against generic email or document skills.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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 — 13 / 16 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	13 / 16 Passed

Repository: Bitterbot-AI/bitterbot-desktop
Path: skills/gog/SKILL.md
Commit: 1c7dc1b

Reviewed: 3 days 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.