google-drive-automation
Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives programmatically.
77
66%
Does it follow best practices?
Impact
97%
1.36xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/google-drive-automation/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and natural trigger terms covering Google Drive file operations. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The mention of the specific tooling (Rube MCP/Composio) adds distinctiveness.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to upload, download, search, share, or organize files in Google Drive, or mentions Google Drive file management.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: upload, download, search, share, organize, manage folders, share with permissions, and search across drives. These are clear, actionable capabilities. | 3 / 3 |
Completeness | The 'what' is well-covered with specific actions and tooling (Rube MCP/Composio), but there is no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the nature of the actions described. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Google Drive', 'upload', 'download', 'search', 'share', 'folders', 'permissions', 'drives'. These cover common variations of how users would describe file operations on Google Drive. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Google Drive operations via a specific tool (Rube MCP/Composio). The combination of 'Google Drive' and the specific MCP tool makes it highly distinctive and unlikely to conflict with generic file or document skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference-style skill that covers Google Drive operations comprehensively with specific tool names, parameters, and pitfalls. Its main weaknesses are redundancy between the per-workflow pitfalls and the consolidated Known Pitfalls section, the lack of concrete executable examples showing full tool invocations, and missing validation/feedback loops in multi-step workflows. The content would benefit from trimming duplicated information and adding explicit verification steps.
Suggestions
Add at least one complete, copy-paste-ready tool invocation example per workflow (e.g., showing exact parameters for GOOGLEDRIVE_FIND_FILE and GOOGLEDRIVE_UPLOAD_FILE in sequence) to improve actionability.
Add explicit validation checkpoints in workflows, such as 'Verify upload succeeded by checking GOOGLEDRIVE_GET_FILE_METADATA before proceeding to share' and error recovery loops (retry on 429, re-auth on 403).
Remove or consolidate the 'Known Pitfalls' section since most items are already covered under individual workflow pitfalls—this would reduce redundancy and improve conciseness.
Consider splitting Query Syntax, Export Formats, and the Quick Reference table into a separate REFERENCE.md file to improve progressive disclosure and reduce the main file's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy—the 'Known Pitfalls' section largely repeats pitfalls already listed under each workflow, and the quick reference table duplicates tool names already covered in detail. Some sections could be tightened, but overall it avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and query syntax examples, which is good. However, it lacks executable code examples or complete copy-paste-ready tool invocation examples (e.g., showing a full RUBE_SEARCH_TOOLS call with parameters). The guidance is concrete but stops short of fully executable demonstrations. | 2 / 3 |
Workflow Clarity | Each workflow has a clear numbered tool sequence with labeled steps (Prerequisite, Required, Fallback, Optional), which is helpful. However, there are no explicit validation checkpoints or feedback loops—for example, no 'verify upload succeeded before sharing' step, and no error recovery guidance beyond listing pitfalls. For operations like sharing with 'anyone' or moving files, validation steps are important but missing. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's a monolithic document (~200+ lines) with no references to supporting files. The Common Patterns, Query Syntax, and Export Formats sections could be split into separate reference files. The single external link to Composio docs is helpful but the skill itself could benefit from better content splitting. | 2 / 3 |
Total | 8 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
74c7031
- 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.