Google Drive: Upload a file with automatic metadata.
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-drive-upload/SKILL.mdQuality
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 is very brief and only partially communicates the skill's purpose. While it names the platform (Google Drive) and a single action (upload with metadata), it lacks a 'Use when...' clause, multiple concrete actions, and sufficient trigger terms to reliably distinguish it from other file or cloud storage skills.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'upload to Google Drive', 'Google Drive upload', 'share file on Drive', 'add file to Drive'.
List additional concrete capabilities beyond just uploading, such as setting permissions, specifying folder destinations, or describing what 'automatic metadata' includes.
Include natural keyword variations users might say, such as 'GDrive', 'Google Docs', 'Drive folder', or specific file types supported.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Drive) and one action (upload a file with automatic metadata), but does not list multiple concrete actions or elaborate on what 'automatic metadata' entails. | 2 / 3 |
Completeness | Describes what it does (upload a file with automatic metadata) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric, missing 'Use when' caps completeness at 2, and the 'what' is also thin, so this scores 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Drive' and 'upload a file' which are natural terms users might say, but misses common variations like 'upload to Drive', 'share file', 'Google Docs', or file type mentions. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Google Drive' and 'upload' provides some distinctiveness, but 'upload a file' is generic enough to potentially overlap with other cloud storage or file management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that does exactly what it needs to. It provides clear CLI usage, a complete flag table, practical examples, and appropriate safety warnings for a write operation. The progressive disclosure through prerequisite and see-also references is well-structured.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every token earns its place. No unnecessary explanations of what Google Drive is or how uploads work. The content is lean, with just flags, examples, and essential tips. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready CLI commands with clear flag descriptions and multiple usage examples covering common scenarios. | 3 / 3 |
Workflow Clarity | This is a simple single-step command skill. The workflow is unambiguous: upload a file with optional flags. The caution box about confirming with the user before executing serves as a validation checkpoint for this write operation. | 3 / 3 |
Progressive Disclosure | Clear prerequisite reference to shared skill for auth/global flags, well-signaled 'See Also' links to related skills one level deep, and the main content is appropriately scoped to just this command. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%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 | |
a3768d0
Table of Contents
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.