recipe-find-large-files
Identify large Google Drive files consuming storage quota.
70
63%
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/recipe-find-large-files/SKILL.mdQuality
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 and distinct niche (finding large Google Drive files consuming storage), which makes it unlikely to conflict with other skills. However, it is a single-sentence description lacking a 'Use when...' clause and missing common trigger term variations that users might naturally use when seeking this functionality.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to free up Google Drive space, find their biggest files, or check what's consuming their storage quota.'
Include additional natural trigger terms users might say, such as 'free up space', 'cleanup', 'disk usage', 'biggest files', 'storage full', or 'running out of space'.
Expand the capability description to list more specific actions, e.g., 'Scans Google Drive to identify large files consuming storage quota, lists files by size, and helps prioritize files for deletion or archival.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Drive) and a specific action (identify large files consuming storage quota), but only describes a single action rather than listing multiple concrete capabilities. | 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. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Google Drive', 'large files', and 'storage quota' that users might naturally say, but misses common variations like 'disk space', 'free up space', 'cleanup', 'biggest files', or file size thresholds. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Drive' + 'large files' + 'storage quota' creates a clear, narrow niche that is unlikely to conflict with other skills. This is a very specific use case. | 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 concise, well-targeted skill that provides an immediately executable command for finding large Drive files. Its main weakness is that step 2 is vague about follow-up actions, which slightly reduces workflow clarity. Overall it's a strong simple skill that respects token budget and delivers actionable guidance.
Suggestions
Make step 2 more actionable by suggesting specific follow-up actions (e.g., 'To delete: `gws drive files delete --fileId <id>`' or 'To move to a shared drive: ...').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean — no unnecessary explanation. Every line serves a purpose. The prerequisite note is essential context, and the command is directly actionable. | 3 / 3 |
Actionability | Provides a fully copy-paste ready command with specific parameters (orderBy, pageSize, fields) that can be executed immediately. No ambiguity about what to run. | 3 / 3 |
Workflow Clarity | This is a simple read-only query (non-destructive), so validation/feedback loops are less critical. However, step 2 ('Review the output and identify files') is vague — it could suggest concrete next actions like deleting, moving, or checking sharing permissions. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with a clear prerequisite callout and numbered steps. No need for external references. | 3 / 3 |
Total | 11 / 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 | |
- Repository
- googleworkspace/cli
- Commit
a3768d0
- 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.