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.
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 is clearly scoped to Google Drive via a particular integration, making it distinctive. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. There is also some redundancy between the two sentences that could be tightened.
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.'
Include common user-facing trigger variations such as 'gdrive', 'Google Docs', 'Google Sheets', or 'cloud storage' to improve matching on natural language queries.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: upload, download, search, share, organize, manage folders, share with permissions, and search across drives programmatically. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific operations, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, capping this at 2 per the rubric guidelines. | 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', 'move files', or file type mentions. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by most users. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Google Drive operations via a specific integration (Rube MCP/Composio), making it highly distinct and unlikely to conflict with generic file management or other cloud storage skills. | 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 structure and specific tool/parameter details. Its main weaknesses are the lack of concrete executable examples (no actual tool invocation snippets), redundancy between per-workflow pitfalls and the consolidated pitfalls section, and missing validation/feedback loops in workflows involving destructive operations like sharing and file moves.
Suggestions
Add concrete, copy-paste-ready tool invocation examples for at least the most common workflows (e.g., a complete search-then-download sequence with actual parameter values)
Add explicit validation checkpoints and error-recovery feedback loops to workflows, especially for sharing (confirm permissions applied) and move operations (verify single parent after move)
Consolidate pitfalls into one section or keep them only per-workflow to eliminate redundancy and reduce token count
Consider splitting Common Patterns, Query Syntax, and Quick Reference into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy — the 'Known Pitfalls' section repeats many pitfalls already listed in individual workflow sections. The Quick Reference table also partially duplicates information from the workflows. However, it generally 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, there are no executable code examples or copy-paste-ready command sequences — everything is described at the tool-slug level with parameter lists rather than showing concrete invocation examples with actual arguments. | 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 error recovery — for operations like sharing (which can be destructive/irreversible) and file moves (which can create multiple parents), the skill mentions pitfalls but doesn't build verify-then-fix loops into the workflow steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's quite long (~200+ lines) with all content inline. The Common Patterns, Known Pitfalls, and Quick Reference sections could be split into separate reference files, with SKILL.md serving as a concise overview pointing to them. | 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
7cc63f3
- 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.