CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-drive

Google Drive through gog. Use for Drive file search, uploads, downloads, sharing, folders, and metadata; use gog-drive-audit for a sharing audit.

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

86%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 exemplary lean skill body: terse, well-structured, with copy-paste startup commands, a complete command table, and smart progressive disclosure that pushes per-command detail to the CLI's help/schema system. The main gaps are the lack of worked examples for common operations and no post-write verification step for destructive commands.

Suggestions

Add one or two worked command examples for the most common operations (e.g., an upload, a share, or a search invocation) so common cases don't require a help lookup.

Include a post-write verification step (e.g., re-checking permissions or metadata after a delete/share/bulk operation) to close the feedback loop for destructive and batch commands.

DimensionReasoningScore

Conciseness

The body is lean throughout — a three-command 'Safe start' block, one-line purposes in the command table, and no explanation of concepts Claude already knows; every token earns its place, matching the anchor-5 example.

5 / 5

Actionability

The Safe start commands ("gog auth list --check --json --no-input", "gog schema drive --json", "gog --readonly ... drive ls ...") are copy-paste ready, and per-command contracts are delegated to "gog drive <command> --help" and "gog schema drive <command> --json". However, no worked invocations are given for the most common operations (upload, share, search), leaving minor gaps versus the fully-executable coverage of a 5.

4 / 5

Workflow Clarity

A clear startup sequence with an auth validation checkpoint is present, and destructive/batch operations have explicit checkpoints ("--dry-run before supported writes", "Confirm the exact account, object, and mutation before any write or delete"), so validation is not missing and the cap of 3 does not apply. What keeps it at 4 rather than 5 is the absence of post-write verification or an error-recovery loop for risky operations like "delete --permanent" and "bulk".

4 / 5

Progressive Disclosure

The body is a clean overview: the single file reference ("Read ../gog/SKILL.md first for shared auth, output, safety, and live-write rules") is well-signaled and one level deep, and bulk per-command detail is appropriately deferred to the CLI's own "--help" / "gog schema" layer rather than inlined, making navigation easy with no nested references.

5 / 5

Total

18

/

20

Passed

Description

87%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 names the tool and domain, enumerates six concrete operations, and provides an explicit 'Use for' trigger clause plus sibling-skill disambiguation. The only weaknesses are moderate coverage gaps in the action list and a few missing natural synonyms.

Suggestions

Add a few more common Drive verbs (e.g., copy, move, delete, rename) to the action list to reach comprehensive coverage.

Include natural synonyms such as 'Google Docs files' or 'shared drives / Team Drives' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Drive file search, uploads, downloads, sharing, folders, and metadata" lists six concrete actions, matching the 'several specific actions' anchor, but coverage has gaps — common Drive verbs like copy, delete, rename, and move are absent, so it falls short of the 'comprehensive coverage' of a 5.

4 / 5

Completeness

"Google Drive through gog" states what the skill does, and "Use for Drive file search, uploads, downloads, sharing, folders, and metadata" is an explicit trigger clause with concrete use cases — both what and when are clearly and explicitly answered, mirroring the anchor-5 example structure.

5 / 5

Trigger Term Quality

Natural terms users would actually say are present ("Google Drive", "file search", "uploads, downloads, sharing"), giving good keyword coverage, but common variations like "Google Docs", "shared drives", or "Team Drives" are missing, which keeps it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

"Google Drive through gog" carves out a clear niche, and the routing clause "use gog-drive-audit for a sharing audit" explicitly disambiguates the closest sibling skill, minimizing conflict risk.

5 / 5

Total

18

/

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