CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

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 well-organized, highly actionable command reference that avoids explaining concepts Claude already knows and includes a safety checkpoint for destructive operations. Slight room to tighten the color table and email examples or split them into a reference file.

Suggestions

Move the 11-entry Calendar Colors hex table into a references file (or reduce to 'run `gog calendar colors`') to tighten the body and improve progressive disclosure.

Collapse the two full Email Formatting bash examples into one, or link out to a reference, to reduce token overhead while keeping a copy-paste exemplar.

Add a brief verify step after send/create (e.g., re-list the sent message or created event) to turn the confirm checkpoint into a full validate->fix->retry feedback loop.

DimensionReasoningScore

Conciseness

The body is a lean command catalog with no padding about what Gmail/Calendar are, but the 11-row color hex table and two full multi-line email examples are slightly more than minimal and could be trimmed, landing just below the lean-and-efficient anchor.

4 / 5

Actionability

Nearly every line is an executable `gog` command with real flags, plus two copy-paste-ready bash examples covering the common send cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

Setup is a clear 3-step sequence and the 'Confirm before sending mail or creating events' note supplies a checkpoint for the outward-facing/destructive operations, satisfying the destructive-op cap; minor gaps remain (no verify-after-send feedback loop).

4 / 5

Progressive Disclosure

Content is organized into clearly headed sections (Setup, Common commands, Calendar Colors, Email Formatting, Notes) with no nested references, but at ~90 lines all inline with no external file split it sits just below the ideal overview-plus-references anchor.

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 that concisely states capabilities across all supported Google services and pairs them with explicit, natural-language trigger phrases. The only minor gap is trigger-term coverage for Contacts and missing synonyms/extensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across all six services ('Search, send, and draft Gmail messages, manage Google Calendar events, query Drive and Contacts, and read/write Google Sheets and Docs'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (the full action inventory 'via the gog CLI') and when ('Use when the user asks to...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ('send email, check their calendar, search Drive files, read a spreadsheet, or export a Google Doc'), but Contacts lacks a natural trigger and no synonyms/file extensions are included, so a few terms are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly bound to 'the gog CLI' with distinct per-service triggers, giving minimal conflict risk despite the broad Google scope.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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