CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-gmail

Gmail through gog. Use for Gmail search, messages, threads, drafts, sending, labels, filters, and settings; use gog-inbox-triage for inbox review or gog-save-attachments for attachment archival.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An efficient, well-structured CLI-wrapper skill: copy-paste safe-start commands, a complete command overview table, and excellent deferral of detail to runtime help and schema. Its weakness is workflow safety for mutations — destructive and batch commands lack post-write verification and error-recovery loops, capping workflow clarity at 3 per the rubric.

Suggestions

Add a post-write verification step for mutations, e.g. re-run `gog gmail get` or `gmail search` after `send`/`trash`/`batch` to confirm the change took effect.

Add an explicit error-recovery loop for failed writes: inspect the `--json` error output, correct the request, and retry — the missing feedback loop is what caps workflow_clarity for a skill with destructive and batch commands.

Show one complete exemplar write workflow for a common operation (e.g. `send`: `--dry-run` → confirm account/object/mutation → execute → verify) so the pre-write safety bullets are grounded in a concrete sequence.

DimensionReasoningScore

Conciseness

The body is lean throughout: three copy-paste safe-start commands, five terse safety bullets, a one-line purpose per command, and a closing pointer to `--help` and `gog schema` — no concept explanations, no padding, every token earns its place. It is not a 4 because there are no instances of over-explanation to trim; the command table is the minimal useful form of this information.

5 / 5

Actionability

"gog auth list --check --json --no-input", "gog schema gmail --json", and the readonly search command are copy-paste ready, and the closing guidance "Run `gog gmail <command> --help` ... `gog schema gmail <command> --json` ... Do not guess command syntax" gives a concrete discovery path. It is not a 5 because specific examples only cover the search/auth case; common operations like send, reply, and drafts have no example invocation, leaving minor gaps.

4 / 5

Workflow Clarity

The safe start is a clear sequence with pre-write checkpoints ("Use `--readonly` when the task must not mutate", "`--dry-run` before supported writes", "Confirm the exact account, object, and mutation before any write or delete"), but the skill exposes destructive and batch operations (`trash`, `batch` — "permanent delete") with no post-write verification or validate-fix-retry feedback loop. Per the rubric, missing feedback loops for batch/destructive operations caps workflow clarity at 3 despite the present pre-write checks.

3 / 5

Progressive Disclosure

The body is a compact overview — safe start plus a command table — that defers per-command detail to runtime resources (`--help`, `gog schema`) and gives one clearly signaled, one-level-deep reference up front: "Read `../gog/SKILL.md` first for shared auth, output, safety, and live-write rules". No nested references, no inlined bulk content; navigation is trivial. (Note: the parent skill file is not present in this review copy, but it is a cross-skill pointer rather than a bundle reference.)

5 / 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: it states the tool and domain, enumerates comprehensive concrete capabilities, gives an explicit "Use for..." trigger clause, and cleanly delegates boundary cases to sibling skills. The only gap is missing common synonyms such as "email", "compose", "reply", and "forward" in the trigger terms.

DimensionReasoningScore

Specificity

"Use for Gmail search, messages, threads, drafts, sending, labels, filters, and settings" enumerates eight concrete capability areas — comprehensive coverage of the Gmail domain, matching the anchor's "multiple specific concrete actions; comprehensive coverage". It is not a 4 because the coverage spans essentially all Gmail surface area with no notable gaps, only minor phrasing as object nouns rather than verbs.

5 / 5

Completeness

Explicitly answers both: what ("Gmail through gog" plus the enumerated capabilities) and when ("Use for Gmail search, messages, threads, drafts, sending, labels, filters, and settings") — a concrete trigger clause equivalent to "Use when...". It is not a 4 because the when-clause is explicit and specific rather than only "could be more explicit", and the what is fully elaborated by the capability list.

5 / 5

Trigger Term Quality

Natural terms users would say are present — "Gmail search", "messages", "threads", "drafts", "sending", "labels", "filters", "settings" — giving good keyword coverage. It is not a 5 because common synonyms and variations are missing, most notably "email" itself (users say "email" far more often than "Gmail"), plus "compose", "reply", and "forward".

4 / 5

Distinctiveness Conflict Risk

"use gog-inbox-triage for inbox review or gog-save-attachments for attachment archival" explicitly routes overlapping cases to sibling skills, and Gmail is a clear niche with distinct triggers — minimal conflict risk. It is not a 4 because the sibling delegation removes even the minor overlap risk a closely-related skill would carry.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/gogcli

Path

.agents/skills/gog-gmail/SKILL.md

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.