gog-gmail

Gmail operations through gog.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-gmail/SKILL.md

Quality

Content

93%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 efficient, highly actionable reference: concrete commands, a compact command index, and explicit safety guidance for writes and deletes. The only gap is the absence of an explicit validate-and-retry feedback loop for destructive or batch operations.

Suggestions

Add a short explicit write/delete workflow with a feedback loop, e.g. 1) confirm account/object/mutation, 2) run with --dry-run, 3) inspect JSON result, 4) only then execute without --dry-run, 5) re-read to verify.

For destructive commands (batch permanent delete, trash), note the verification step to take after the mutation (e.g. re-search or get the message to confirm state).

Dimension	Reasoning	Score
Conciseness	The body is lean: a compact safe-start command block, terse safety bullets, and a one-line-per-command reference table, with no concept explanations Claude already knows — every token earns its place, matching 'Lean and efficient; assumes Claude's competence'.	5 / 5
Actionability	It gives copy-paste-ready executable commands with concrete flags (--account, --readonly, --json --wrap-untrusted, --dry-run), a full command-to-purpose table, and explicit pointers to --help and 'gog schema ... --json', matching 'Fully executable; copy-paste ready code or commands'.	5 / 5
Workflow Clarity	The safe-start sequences auth check, schema fetch, and a readonly probe, and the bullets supply validation checkpoints (confirm account/object/mutation, --dry-run, --readonly), but there is no explicit validate->fix->retry feedback loop for destructive/batch writes, fitting 'Clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	At under 50 lines with no local bundle files, the content is cleanly split into well-signaled sections (Safe start, Commands) and points one level deep to ../gog/SKILL.md plus --help/schema for detail, matching the simple-skill 'well-organized sections' criterion for a 5.	5 / 5
	Total	19 / 20 Passed

Description

40%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 correctly identifies the domain and tool but is too terse: it states no concrete actions and provides no usage trigger, leaving Claude without guidance on when to invoke it. It is distinct but underspecified.

Suggestions

List 2-4 concrete capabilities (e.g. search, send, reply, label, and trash messages) instead of the generic 'operations'.

Add an explicit 'Use when...' trigger clause naming natural terms users say (e.g. email, inbox, sending or searching Gmail).

Mention the gog prerequisite briefly so the description stands alone, e.g. 'Gmail operations (search, send, reply, labels, trash) through the gog CLI. Use when the user wants to read, send, or organize Gmail email.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('Gmail') and tool ('gog') but the only action word is the generic 'operations', with no concrete capabilities listed, matching the 'Names the domain but actions are minimal or generic' anchor rather than 3 (which requires 1-2 concrete actions).	2 / 5
Completeness	It offers only a vague 'what' ('Gmail operations through gog') and no 'when'/Use-when clause at all, matching 'Has a vague what and no when'; the missing trigger guidance also caps completeness at 3 per the guidelines, and this is below that.	2 / 5
Trigger Term Quality	'Gmail' is a natural keyword users would say, but common variations like 'email', 'inbox', or 'send email' are absent and 'operations'/'gog' are not user-natural terms, fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The Gmail + gog pairing carves a clear niche with only minor overlap risk against sibling gog skills (e.g. calendar), fitting 'Mostly distinct; minor overlap risk with closely related skills' rather than 5 because 'operations' is broad.	4 / 5
	Total	11 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: openclaw/gogcli
Path: .agents/skills/gog-gmail/SKILL.md
Commit: eb85a99

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.