gws-drive
Google Drive: Manage files, folders, and shared drives.
59
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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) but is too brief and generic. It lacks specific actions beyond 'manage' and critically missing explicit trigger guidance ('Use when...') that would help Claude know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger terms like 'upload to drive', 'share Google doc', 'access my drive', 'cloud storage'
Replace vague 'Manage' with specific actions like 'Upload, download, share, search, and organize files'
Include common user phrases and variations like 'gdrive', 'Google docs', 'share link', 'drive permissions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Drive) and mentions general actions (manage files, folders, shared drives), but lacks specific concrete actions like 'upload', 'download', 'share', 'search', or 'organize'. | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 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 'gdrive', 'cloud storage', 'share a file', or 'upload to drive'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Drive' is a specific platform which helps distinguish it, but 'manage files, folders' is generic enough to potentially overlap with other file management or cloud storage skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill serves well as an API reference document with excellent organization and progressive disclosure. However, it lacks concrete executable examples showing actual command usage with parameters, and missing validation guidance for potentially destructive operations like file deletion or permission changes limits its actionability.
Suggestions
Add 2-3 concrete executable examples showing common operations like listing files, uploading, or sharing with actual --params usage
Include validation/verification guidance for destructive operations (e.g., 'Before deleting, list files first to confirm targets')
Add a 'Common Patterns' section with copy-paste ready commands for frequent use cases
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, serving as a reference document that lists API resources and methods without explaining concepts Claude already knows. Every section earns its place with no unnecessary padding. | 3 / 3 |
Actionability | Provides the command structure and schema inspection commands, but lacks concrete executable examples showing actual usage with parameters. The API method descriptions are informative but don't include copy-paste ready command examples. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a basic workflow for exploring the API, but there are no validation checkpoints or feedback loops for operations like file deletion or permission changes that could be destructive. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear prerequisite reference to shared skill, helper command links, organized API resources by category, and well-signaled navigation. The content is appropriately split with one-level-deep references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.