recipe-organize-drive-folder
Create a Google Drive folder structure and move files into the right locations.
67
60%
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-organize-drive-folder/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 functional but incomplete. It identifies the domain (Google Drive) and two core actions but lacks an explicit 'Use when...' clause, which is critical for skill selection. It would benefit from more specific capability listing and natural trigger terms users might employ.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to organize files in Google Drive, create a folder hierarchy, or sort/move documents into folders.'
Include additional natural trigger terms users might say, such as 'organize files', 'file organization', 'directory structure', 'sort files into folders', or 'clean up Drive'.
Expand the capability list with more specific actions, e.g., 'Create nested folder hierarchies, move and categorize files by type or project, and reorganize existing Google Drive structures.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Drive) and two actions (create folder structure, move files), but doesn't elaborate on specific capabilities like sharing, permissions, nested structures, or file type handling. | 2 / 3 |
Completeness | Describes what the skill does (create folder structure, move files) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also only moderately detailed, placing this at 1-2. Given the missing 'when' clause entirely, scoring at the lower end. | 1 / 3 |
Trigger Term Quality | Includes natural terms like 'Google Drive', 'folder structure', and 'move files', but misses common variations users might say such as 'organize files', 'file organization', 'folders', 'directory structure', or 'sort files'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Google Drive' provides some distinctiveness from generic file management skills, but could overlap with other Google Drive skills (e.g., sharing, searching) or general file organization skills. | 2 / 3 |
Total | 7 / 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 fully actionable CLI commands for organizing Google Drive files. Its main weakness is the lack of error handling or feedback loops for the file move operation (removeParents is potentially destructive), which limits workflow clarity. Overall it's a strong, focused recipe.
Suggestions
Add a feedback loop after step 3: verify the file appears in the new folder before considering the move complete, and include guidance for handling errors (e.g., invalid file/folder IDs).
Consider noting that removeParents effectively moves the file and could result in the file being inaccessible if the wrong parent is removed—add a 'confirm before proceeding' checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It assumes Claude knows what Google Drive is and how folder structures work. Every line serves a purpose with no unnecessary explanation. | 3 / 3 |
Actionability | Each step provides a concrete, copy-paste-ready CLI command with the exact flags, JSON payloads, and parameters needed. Placeholder values (PARENT_FOLDER_ID, FILE_ID, etc.) are clearly marked. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and include a verification step (step 4), but there's no error handling or feedback loop—e.g., what to do if folder creation fails, or how to confirm the move succeeded before proceeding. For operations that restructure files (potentially destructive with removeParents), a validation/retry loop would be appropriate. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with a clear prerequisite note, a concise description, and a numbered step list. No need for external references given the scope. | 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.