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.
72
58%
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
67%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 does well at listing specific capabilities and establishing a clear niche around Google Drive operations via Rube MCP. However, it lacks an explicit 'Use when...' clause which caps completeness, and the description is somewhat redundant—listing operations twice in slightly different forms. Adding trigger guidance and removing the technical tool reference from the primary description would improve selection accuracy.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to upload to Google Drive, share Google Drive files, organize Drive folders, or search for files in Google Drive.'
Include common user-facing variations like 'gdrive', 'Google Docs', 'shared drive', or 'Drive link' to improve trigger term coverage.
| 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 | Clearly answers 'what does this do' with specific operations, but lacks an 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 good keywords like 'Google Drive', 'upload', 'download', 'search', 'share', 'folders', and 'permissions', but misses common user variations like 'gdrive', 'Google Docs', 'file sharing link', or 'move files'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to appear in user requests. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Google Drive operations via a specific tool (Rube MCP/Composio), making it highly distinguishable from generic file handling or other cloud storage skills. The combination of 'Google Drive' and the specific toolchain creates a clear niche. | 3 / 3 |
Total | 10 / 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 good structural organization and useful pitfall documentation. Its main weaknesses are redundancy between sections (pitfalls repeated in both workflow-specific and consolidated sections), lack of concrete executable tool call examples, and missing explicit validation/confirmation checkpoints for risky operations like broad sharing. The content would benefit from being split across bundle files and including complete tool invocation examples.
Suggestions
Add at least one complete, concrete tool invocation example per workflow (e.g., a full GOOGLEDRIVE_UPLOAD_FILE call with all parameters filled in) to improve actionability.
Add explicit validation checkpoints and confirmation prompts for risky operations—especially sharing with type='anyone' and move operations—to improve workflow clarity.
Consolidate pitfalls into a single section or keep them only in workflow-specific sections to eliminate redundancy and improve conciseness.
Split the query syntax reference, export formats, and quick reference table into a separate REFERENCE.md bundle file to improve progressive disclosure.
| 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 information from the workflow sections. Some sections could be tightened, though most content is genuinely useful reference material rather than explaining things Claude already knows. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and query syntax examples, which is good. However, there are no complete executable examples showing actual tool invocations with full parameter objects—it's more of a reference guide with parameter lists rather than copy-paste-ready tool call sequences. The s3key upload requirement is mentioned but no concrete example of constructing the file_to_upload object is shown. | 2 / 3 |
Workflow Clarity | Each workflow has a clear numbered tool sequence with prerequisite/required/optional/fallback labels, which is helpful. However, validation checkpoints are weak—there's no explicit 'verify before proceeding' feedback loop for destructive operations like sharing with 'anyone' or moving files. The setup section has a good sequential flow, but core workflows lack error recovery steps beyond mentioning pitfalls. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's a monolithic ~200-line document with no bundle files to offload detailed reference material. The query syntax guide, export formats, and detailed pitfalls per workflow could be split into separate reference files. The single external link to Composio docs is appropriate but insufficient for the volume of content. | 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 | |
d065ead
Table of Contents
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.