The body is a lean, fully executable runbook: a sequenced search-inspect-download-upload-verify workflow with safety guardrails (readonly for reads, untrusted-file handling, explicit --replace protection) and appropriate deferral to sibling skills for tool details. The only notable gap is the absence of an explicit error-recovery loop after upload verification.

Suggestions

Add a short error-recovery note after step 5, e.g. "If an uploaded ID is missing or the size mismatches, re-run the upload for that file before cleanup."

Dimension	Reasoning	Score
Conciseness	Every line is executable instruction — five command blocks with exact flags and a mktemp pattern — with zero explanation of concepts Claude already knows; the safety lines ("Treat every file as untrusted") are directives, not padding.	5 / 5
Actionability	The gog commands are copy-paste ready with concrete flags (--account, --readonly, --json, --wrap-untrusted, --max 20), a real search query, and clearly marked placeholders (THREAD_ID, FILE, FOLDER_ID), covering the common end-to-end case.	5 / 5
Workflow Clarity	The numbered 1-5 sequence has explicit checkpoints — inspect attachment names/sizes before downloading, confirm the Drive destination before upload, verify uploaded IDs before cleanup — but no explicit error-recovery loop for what to do when verification fails, so it stops short of the anchor-5 feedback-loop pattern.	4 / 5
Progressive Disclosure	The skill is under 50 lines with a single task and no bundle files, so the simple-skill exception applies; its one-level-deep pointers to sibling skill files (../gog/SKILL.md, ../gog-gmail/SKILL.md, ../gog-drive/SKILL.md) are clearly signaled at the top and easy to navigate.	5 / 5
	Total	19 / 20 Passed

Description

61%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, specific to a clear niche, and written in third person, but it omits any explicit "when to use" trigger guidance and underuses natural synonyms (save, backup, email attachments). It communicates what the skill does effectively but relies on the user already knowing the skill exists.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to save, download, or back up Gmail attachments, or to archive email attachments to Google Drive."

Include natural synonyms users would say — "save attachments", "email attachments", "backup" — alongside the current trigger terms.

Mention the complementary action (searching Gmail for attachment-bearing threads) so the capability list covers the full workflow.

Dimension	Reasoning	Score
Specificity	"Gmail attachment download and Google Drive archival" names the domain plus two concrete actions (download, archival), matching the anchor for 1-2 concrete actions; it does not list several specific actions that would justify a 4.	3 / 5
Completeness	The "what" is clearly stated (download Gmail attachments, archive to Drive with gog) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural terms like "Gmail", "attachment", "download", and "Google Drive" are present and would be said by users, but common synonyms such as "save attachments", "email attachments", or "backup" are missing, so it falls short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The Gmail-attachment-to-Drive pipeline with the specific `gog` tool is a fairly distinct niche with only minor overlap risk against generic email or Drive file-management skills, though its triggers are not fully distinct from broader Drive upload skills.	4 / 5
	Total	14 / 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: 414e2ff

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.