gws-drive

Google Drive: Manage files, folders, and shared drives.

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gws-drive/SKILL.md

Quality

Discovery

32%

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 identifies the platform (Google Drive) which provides some distinctiveness, but it is too vague in describing capabilities—'manage' is a catch-all verb that doesn't convey specific actions. It critically lacks a 'Use when...' clause, making it harder for Claude to know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to upload, download, share, search, or organize files in Google Drive.'

Replace the vague 'Manage' with specific concrete actions like 'Upload, download, search, share, move, and organize files and folders in Google Drive.'

Include natural keyword variations users might say, such as 'gdrive', 'Google Docs', 'cloud storage', 'sharing permissions', or 'drive link'.

Dimension	Reasoning	Score
Specificity	Names the domain (Google Drive) and some general actions (manage files, folders, shared drives), but doesn't list specific concrete actions like uploading, downloading, sharing, searching, or organizing.	2 / 3
Completeness	Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also quite weak/vague, bringing this to a 1.	1 / 3
Trigger Term Quality	Includes 'Google Drive', 'files', 'folders', and 'shared drives' which are relevant keywords, but misses common variations users might say like 'upload', 'download', 'share a file', 'Google Docs', 'gdrive', or 'cloud storage'.	2 / 3
Distinctiveness Conflict Risk	'Google Drive' is a fairly distinct trigger that narrows the domain, but 'manage files and folders' is generic enough to potentially overlap with local file management or other cloud storage skills.	2 / 3
	Total	7 / 12 Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially an API reference dump rather than an actionable guide. While it correctly references prerequisite skills and provides discovery commands, the bulk of the content is a verbose reproduction of the Google Drive API surface that Claude could discover through the CLI's help system. It lacks concrete usage examples, common workflow patterns, and validation steps for destructive operations.

Suggestions

Replace the exhaustive API reference listing with a concise summary of the most common resources (files, permissions, drives) and move the full reference to a separate REFERENCE.md file.

Add 3-5 concrete, executable examples for common tasks (e.g., list files, share a file, search with query parameter, export a Google Doc).

Add validation/confirmation guidance for destructive operations like `permissions.delete` and `revisions.delete`.

Include example `--params` and `--json` flag usage since the skill mentions these flags but never demonstrates them.

Dimension	Reasoning	Score
Conciseness	The content is extremely verbose, essentially reproducing the entire Drive API reference documentation inline. Most of these method descriptions are things Claude already knows or could discover via the `gws schema` command mentioned at the bottom. The repeated 'For more information, see [link]' patterns and full API surface listing waste significant tokens.	1 / 3
Actionability	The skill provides the basic command pattern (`gws drive <resource> <method> [flags]`) and the discovery commands (`gws schema`), which are concrete. However, there are no executable examples showing actual usage with real flags/params, no example outputs, and no concrete workflows for common tasks like listing files, sharing, or uploading.	2 / 3
Workflow Clarity	The 'Discovering Commands' section provides a basic two-step workflow (browse then inspect), but there are no workflows for common multi-step operations like sharing files, managing permissions, or handling uploads. Destructive operations like `revisions.delete` and `permissions.delete` lack any validation or confirmation steps.	2 / 3
Progressive Disclosure	The skill references a shared prerequisite file and links to an upload helper skill, which is good progressive disclosure. However, the massive inline API reference listing should be in a separate reference file rather than dominating the main SKILL.md. The content that should be the overview (quick start, common patterns) is minimal while the reference content is exhaustive.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	10 / 11 Passed

Repository: googleworkspace/cli
Commit: c7c6646

Reviewed: about 7 hours 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.