recipe-find-large-files
Identify large Google Drive files consuming storage quota.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-find-large-files68
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
40%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 a clear niche (Google Drive storage management) but is incomplete. It lacks explicit trigger guidance ('Use when...') and could benefit from additional action verbs and natural user phrases like 'free up space' or 'clean up Drive'.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'free up Drive space', 'clean up Google Drive', 'find what's using my storage'
Include additional concrete actions such as 'list files by size', 'identify files to delete', or 'analyze storage usage'
Add natural keyword variations users might say: 'Drive space', 'storage full', 'disk cleanup', 'what's taking up space'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Drive) and one action (identify large files), but doesn't list multiple concrete actions like listing, sorting, deleting, or providing size thresholds. | 2 / 3 |
Completeness | Describes what the skill does 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', 'large files', and 'storage quota' which are relevant, but misses common variations like 'Drive space', 'free up storage', 'disk usage', or 'cleanup'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Drive' + 'large files' + 'storage quota' creates a clear, specific niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%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 provides immediately actionable commands for finding large Drive files. The main weakness is the deletion workflow lacks an explicit verification step before permanent deletion, which is important for destructive operations. The caution callout is good but doesn't translate into a procedural safeguard.
Suggestions
Add a verification step before deletion, e.g., 'Verify file details: `gws drive files get --params '{"fileId": "FILE_ID", "fields": "name,size,owners"}'` before deleting'
Consider adding a step to check if file is in trash or suggest moving to trash first: `gws drive files update --params '{"fileId": "FILE_ID", "trashed": true}'`
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations about what Google Drive is or how storage works. Every line serves a purpose - prerequisite, warning, and actionable commands. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands with specific parameters. The gws CLI commands include exact field specifications and formatting options. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (list → review → delete), but lacks explicit validation checkpoint before deletion. The caution note exists but there's no feedback loop like 'verify file before deleting' or 'check trash status after deletion'. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. Clear prerequisite reference to gws-drive skill, well-organized sections, and no need for external file references. | 3 / 3 |
Total | 11 / 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.