CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-organize-drive-folder

Create a Google Drive folder structure and move files into the right locations.

67

Quality

60%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/recipe-organize-drive-folder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

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 concise and identifies the core domain (Google Drive) with two concrete actions, but it lacks an explicit 'Use when...' clause that would help Claude know when to select this skill. It also misses common user trigger terms like 'organize', 'file organization', or 'sort files into folders' that would improve matching.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks 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', 'rearrange folders'.

Expand the capability list slightly to cover edge cases, e.g., 'Create nested folder hierarchies, move and organize files by type or project, and restructure existing Google Drive directories.'

DimensionReasoningScore

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

The mention of 'Google Drive' provides some specificity, but 'folder structure' and 'move files' could overlap with general file management or other cloud storage skills. It's somewhat distinct but not sharply delineated.

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). The structure and token efficiency are excellent for a skill of this scope.

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 what to do if the move fails.

Consider noting that removeParents is destructive (removes file from old location) and suggest confirming the old parent ID before executing the update.

DimensionReasoningScore

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 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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

10

/

11

Passed

Repository
googleworkspace/cli
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.