gog-save-attachments

Gmail attachment download and Google Drive archival with gog.

Quality

76%

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-save-attachments/SKILL.md

Quality

Content

100%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 lean, executable workflow: concrete commands, a clear numbered sequence, explicit verification and safety guards for destructive operations, and one-level-deep peer-skill pointers. It fully respects the token budget while remaining copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~40-line workflow with no concept explanation or padding; every line (commands, flags, the mktemp pattern, the overwrite guard) earns its place and assumes Claude's competence.	5 / 5
Actionability	Commands are fully executable and copy-paste ready with real flags (--readonly, --json, --wrap-untrusted, --download, --out-dir) and a concrete mktemp -d pattern, covering the common search→inspect→download→upload cases.	5 / 5
Workflow Clarity	A clearly sequenced 5-step process with explicit validation checkpoints (confirm Drive destination before upload, verify uploaded IDs, remove only the run's temp dir) plus an overwrite guard; the destructive/batch cap does not apply because validation is present.	5 / 5
Progressive Disclosure	The skill is short and self-organized as numbered steps, with well-signaled one-level-deep peer-skill references (Read ../gog/SKILL.md, ../gog-gmail/SKILL.md, ../gog-drive/SKILL.md first) and no nested references; no internal bundle files are needed for this simple skill.	5 / 5
	Total	20 / 20 Passed

Description

53%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 names a specific niche, but it lacks any explicit "Use when..." trigger guidance and does not comprehensively enumerate actions or synonyms. It is clear and distinct yet incomplete on the "when" dimension.

Suggestions

Add an explicit "Use when..." clause naming natural triggers (e.g., "Use when the user wants to save or back up Gmail attachments to Google Drive").

Broaden trigger terms with common synonyms and extensions (e.g., "save", "back up", ".eml", "inbox attachments") to improve trigger coverage.

Optionally enumerate a third concrete action (e.g., "verify uploads") to lift specificity toward several specific actions.

Dimension	Reasoning	Score
Specificity	"Gmail attachment download and Google Drive archival with gog" names the domain and two concrete actions (download, archival) but is not comprehensive, matching the 1-2 concrete actions anchor; not 4 because there are only two actions, not several.	3 / 5
Completeness	The "what" is clear (download Gmail attachments, archive to Drive) but there is no "Use when..." trigger clause, so per the missing-trigger guideline completeness is capped at 3 with the "when" only weakly implied.	3 / 5
Trigger Term Quality	Terms like "Gmail", "attachment", "download", "Google Drive", and "archival" are natural but common variations/synonyms and file extensions are missing, so it fits the "some relevant keywords but missing variations" anchor rather than 4.	3 / 5
Distinctiveness Conflict Risk	The combination of Gmail attachments, Drive archival, and the "gog" tool name carves a clear niche with minimal overlap, sitting between 4 (mostly distinct, minor overlap) and 5; not 5 only because triggers are less explicitly enumerated than the anchor example.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: openclaw/gogcli
Path: .agents/skills/gog-save-attachments/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.