gog

Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

2.27x

Quality

69%

Does it follow best practices?

Impact

75%

2.27x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/gog/SKILL.md

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.

The body is an exemplary CLI skill reference: concrete executable commands, gog-specific gotchas that Claude could not infer, an ordered setup sequence, and safety checkpoints for send/create operations. Its only weaknesses are minor — a small amount of over-explanation (the HTML tag primer) and inline reference-style content (the color hex table) that could live in a separate file.

Dimension	Reasoning	Score
Conciseness	The body is a lean command cheat-sheet — every bullet is a concrete gog command or a gog-specific gotcha (e.g. "`--body` does not unescape `\n`") that Claude cannot know. Not a 5 because the HTML tags bullet ("<p> for paragraphs, <br> for line breaks...") re-teaches HTML Claude already knows and could be trimmed.	4 / 5
Actionability	Nearly every line is a copy-paste-ready command with real flags and placeholders, including two complete executable bash examples (stdin heredoc, HTML send). The common cases (search, send, reply, drafts, events, sheets read/write, docs export) are all covered concretely — a clear match for anchor 5.	5 / 5
Workflow Clarity	The one-time auth sequence is clearly ordered (credentials → auth add → auth list to verify), and the Notes provide a checkpoint for outward-facing operations ("Confirm before sending mail or creating events"), plus a drafts-create-then-send pattern that acts as a safe feedback loop. Not a 5 because validation is stated as a rule rather than built into an explicit validate-then-act workflow with error-recovery steps.	4 / 5
Progressive Disclosure	A single well-organized file with clear sections (Setup, Common commands, Calendar Colors, Email Formatting, Notes) and no bundle files; for a CLI command reference this is appropriate. Not a 5: at ~116 lines, content like the full 11-entry color hex table and the long HTML example is a candidate for a one-level-deep reference file, which keeps the overview even leaner.	4 / 5
	Total	17 / 20 Passed

Description

56%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.

The description is concise and accurately scoped to the gog CLI's domain, with good natural keywords, but it names no concrete actions and entirely lacks a 'Use when...' trigger clause, which caps completeness and limits its triggering power.

Suggestions

Add a 'Use when...' trigger clause, e.g. "Use when the user asks to search or send Gmail, create or edit Calendar events, or manage Drive/Contacts/Sheets/Docs and the gog CLI is available."

Add 1-2 concrete actions to the description, e.g. "Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs — search and send email, create calendar events, read and update spreadsheets."

Include common synonyms (email, meetings/events, spreadsheets) so the description triggers on phrasings users naturally say.

Dimension	Reasoning	Score
Specificity	The description names the domain precisely ("Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs") but lists zero concrete actions — no search, send, create, or export verbs. This matches anchor 2 ("Names the domain but actions are minimal or generic", e.g. "Processes PDF files") and not anchor 3, which requires 1-2 concrete actions.	2 / 5
Completeness	The "what" is clear (a Google Workspace CLI covering six services), but there is no "when" — no "Use when..." or equivalent trigger guidance. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Six natural service names (Gmail, Calendar, Drive, Contacts, Sheets, Docs) plus "Google Workspace" give good keyword coverage users would actually say. Not anchor 5 because common synonyms and variations are missing ("email" for Gmail, "events/meetings" for Calendar, "spreadsheet", "Google Docs" phrasing).	4 / 5
Distinctiveness Conflict Risk	The Google Workspace scope plus named services and "CLI" mark a clear niche that most skills would not collide with. Not anchor 5 because the named services could overlap with dedicated Sheets/Docs/email skills in the same environment, and no distinctive trigger phrases sharpen the boundary.	4 / 5
	Total	13 / 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: trpc-group/trpc-agent-go
Path: openclaw/skills/gog/SKILL.md
Commit: 9bb1c42

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