recipe-bulk-download-folder
List and download all files from a Google Drive folder.
59
50%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-bulk-download-folder/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 is concise and clearly identifies the platform (Google Drive) and two core actions (list and download), giving it good distinctiveness. However, it lacks a 'Use when...' clause, which is critical for skill selection, and could benefit from additional trigger terms and capability details to improve completeness and discoverability.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to list, browse, or download files from a Google Drive folder, shared drive, or GDrive link.'
Include additional natural trigger terms like 'GDrive', 'shared drive', 'export files', or 'bulk download' to improve keyword coverage.
Expand the capability list to mention specifics like recursive folder traversal, file type filtering, or handling of Google Docs/Sheets export formats if applicable.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Drive) and two specific actions (list and download files), but the scope is narrow and doesn't mention other potential capabilities like filtering, recursive folder traversal, or file type handling. | 2 / 3 |
Completeness | Describes what the skill does (list and download files from Google Drive) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps this at 2, and the 'what' is also minimal, so it scores 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'Google Drive', 'folder', 'download', and 'files' which users would say, but misses common variations like 'GDrive', 'shared drive', 'export', or file type mentions. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Drive folder' with 'list and download' creates a clear, distinct niche that is unlikely to conflict with other skills. The platform-specific trigger (Google Drive) makes it highly distinguishable. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is admirably concise and well-structured for its scope, but falls short on actionability and workflow clarity. The critical gap is the missing connection between listing files (step 1) and iterating over them for download (step 2), which is the core challenge of bulk downloading. There's also no validation that downloads completed successfully.
Suggestions
Show how to parse the JSON output from step 1 and loop over file IDs to execute step 2 for each file (e.g., a shell loop or jq pipeline).
Add a validation step to verify downloads succeeded, such as checking file sizes or counting downloaded files against the listed count.
Clarify how to distinguish between regular files (use 'get') and Google Workspace files (use 'export') from the listing output, e.g., by checking mimeType.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations. Every line serves a purpose—prerequisite, steps, and commands only. | 3 / 3 |
Actionability | Provides concrete CLI commands with specific flags, but the commands use placeholders (FOLDER_ID, FILE_ID) without showing how to iterate over the file list to download each file. The escaping in the query parameter is awkward and the workflow for connecting step 1's output to step 2's input is missing. | 2 / 3 |
Workflow Clarity | Steps are listed but there's no guidance on how to loop over results from step 1 to feed into step 2, no validation/verification that downloads succeeded, and no error handling for batch operations. Batch download operations without validation should cap this at 2, and the missing iteration logic drops it further. | 1 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines, the structure is appropriate: a clear prerequisite callout, a concise description, and numbered steps. No need for external references given the scope. | 3 / 3 |
Total | 9 / 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.