gws-drive

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

Quality

33%

Does it follow best practices?

Impact

—

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

Content

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 establishes the command pattern and discovery mechanism, the bulk of the content is a verbose reproduction of Google Drive API documentation that Claude doesn't need inline. The skill would be dramatically improved by moving the API reference to a separate file and replacing it with concrete usage examples for common operations.

Suggestions

Move the full API resource listing to a separate REFERENCE.md file and keep only the most common resources (files, permissions, drives) with brief mentions in the main skill

Add 3-5 concrete executable examples for common operations (e.g., list files, share a file, search with q parameter, export a Google Doc) with actual --params and --json flag usage

Add validation/verification guidance for destructive operations like permissions.delete and revisions.delete, including how to confirm the operation succeeded

Remove the repeated 'For more information, see [link]' patterns - these external doc links are not useful to Claude during execution

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 (inspect then call), but there are no validation steps, no error handling guidance, and no workflows for potentially destructive operations like deleting permissions or revisions. The prerequisite reference to shared skills is good but the actual operational workflows are missing.	2 / 3
Progressive Disclosure	The skill correctly references a shared SKILL.md for auth and links to an upload helper skill, which is good progressive disclosure. However, the massive API reference listing should have been in a separate reference file rather than inline, making the main skill a wall of text that buries the actionable content.	2 / 3
	Total	7 / 12 Passed

Description

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 is too terse and generic, relying on the 'Google Drive' brand name to do most of the differentiation work. It lacks specific concrete actions (upload, download, share, search, create) and entirely omits a 'Use when...' clause, making it difficult for Claude to confidently select this skill over others in a large skill library.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user mentions Google Drive, uploading to Drive, sharing Drive files, or managing Drive permissions.'

List specific concrete actions instead of the vague 'manage', e.g., 'Upload, download, search, share, and organize files and folders in Google Drive. Create and manage shared drives and permissions.'

Include natural trigger terms users would say, such as 'Google Docs', 'Drive link', 'share a file', 'cloud storage', 'upload to Drive', '.gdoc'.

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, searching, sharing permissions, moving files, etc.	2 / 3
Completeness	Provides a brief 'what' (manage files, folders, shared drives) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric should cap completeness at 2, and the 'what' itself is quite weak, pushing 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', 'Drive link', 'Google Docs', or 'cloud storage'.	2 / 3
Distinctiveness Conflict Risk	'Google Drive' is a fairly distinct domain identifier that separates it from generic file management skills, but 'manage files and folders' is generic enough to potentially overlap with local file system or other cloud storage skills.	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: a3768d0

Reviewed: 2 months 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.