googledrive-automation
by ComposioHQgoogledrive-automation automates Google Drive file tasks through Rube MCP and Composio. It guides agents to search live tool schemas first, verify an active Drive connection, then safely find, create, update, organize, or move files.
This skill scores 66/100, which means it is acceptable for directory listing but should be presented as a lightweight MCP workflow guide rather than a full-featured automation package. Directory users get enough clarity to know it is for Google Drive automation via Rube MCP and how to start, but they should expect limited built-in examples and reliance on runtime tool discovery.
- Valid frontmatter with a clear trigger: automate Google Drive tasks through Rube MCP/Composio.
- Explicit prerequisites and setup steps identify the needed MCP server, Google Drive connection, and ACTIVE connection check.
- Strong operational instruction to call RUBE_SEARCH_TOOLS first for current schemas, reducing risk from stale tool names or inputs.
- No support files, scripts, references, or bundled examples beyond SKILL.md, so execution depends heavily on live Rube MCP tool discovery.
- The available evidence emphasizes generic discovery/setup patterns rather than concrete Google Drive task recipes, which may leave agents guessing on specific workflows.
Overview of googledrive-automation skill
What googledrive-automation is for
googledrive-automation is a Claude skill for automating Google Drive operations through Composio’s Google Drive toolkit using Rube MCP. It is built for users who want an agent to search current Google Drive tool schemas, confirm connection status, and then execute file automation tasks such as finding, creating, updating, organizing, or moving Drive content.
The key value of the googledrive-automation skill is not a long library of fixed commands. Its main pattern is safer tool discovery: call RUBE_SEARCH_TOOLS first, inspect the live schema, then run the correct Google Drive action through the active Rube connection.
Best-fit users and workflows
This skill fits users who already use Claude or another MCP-capable client and want Google Drive automation without manually wiring the Google Drive API. It is especially useful for File Automation tasks where the exact Drive operation may vary: locating files by name, checking folders before creating duplicates, updating metadata, or coordinating Drive actions with other Composio/Rube toolkits.
It is a good choice when you need agent-led Drive work but still want the model to verify tool names and input fields before acting.
Important adoption constraints
googledrive-automation depends on Rube MCP. Before the skill can do anything useful, RUBE_SEARCH_TOOLS must be available and a Google Drive connection must be active through RUBE_MANAGE_CONNECTIONS with toolkit googledrive.
The repository for this skill is intentionally compact and appears to contain only SKILL.md. That makes it easy to inspect, but it also means there are no bundled scripts, examples, rules, or test fixtures. Users should treat live tool discovery as part of normal usage, not as an optional setup step.
How to Use googledrive-automation skill
googledrive-automation install and setup path
Install the skill from the Composio skills repository:
npx skills add ComposioHQ/awesome-claude-skills --skill googledrive-automation
Then add Rube MCP as an MCP server in your client configuration using:
https://rube.app/mcp
After that, verify three things before asking for Drive automation:
RUBE_SEARCH_TOOLSresponds.RUBE_MANAGE_CONNECTIONScan check toolkitgoogledrive.- The Google Drive connection status is
ACTIVE.
If the connection is not active, follow the authentication link returned by RUBE_MANAGE_CONNECTIONS, then re-check status before running file operations.
What to read before first use
Start with composio-skills/googledrive-automation/SKILL.md. It contains the whole operational pattern: prerequisites, setup, tool discovery, connection checking, and execution flow.
Because this skill has no visible README.md, scripts/, resources/, or rules/ folder in the current tree, do not look for hidden implementation logic. The important instruction is procedural: always discover the current Rube tool schemas before choosing a Google Drive action.
Turning a rough request into a strong prompt
A weak prompt is: “Clean up my Drive.”
A stronger googledrive-automation usage prompt is:
“Use googledrive-automation. First call RUBE_SEARCH_TOOLS for Google Drive file search, folder listing, and file move operations. Confirm my Google Drive connection is active. Then find files in My Drive with names containing ‘Invoice’ created before 2024-01-01. Do not delete anything. Create a folder named Old Invoices Review if it does not already exist, move matching files there, and summarize every file moved.”
This works better because it defines the allowed operations, search criteria, destination behavior, no-delete constraint, and expected report.
Practical workflow for safer Drive automation
Use a staged workflow:
- Discover tools with
RUBE_SEARCH_TOOLSusing the specific use case. - Check Google Drive connection status.
- Ask the agent to restate the intended Drive actions before execution.
- Run read-only discovery first, such as search or list operations.
- Execute mutations only after confirming file IDs, folder IDs, and duplicate-handling rules.
- Request a final audit summary with IDs, names, and actions taken.
For sensitive Drive environments, explicitly say whether the agent may create, move, rename, update, share, or delete files. If deletion is not required, ban it in the prompt.
googledrive-automation skill FAQ
Is googledrive-automation only for developers?
No. The skill can be useful for non-developers if their AI client supports MCP and Rube is configured. However, the setup still involves adding an MCP server and authorizing Google Drive. Users who cannot configure MCP will not get value from the skill.
How is this better than an ordinary Google Drive prompt?
A normal prompt can describe an intended Drive workflow, but it may hallucinate tool names or outdated input fields. googledrive-automation instructs the agent to call RUBE_SEARCH_TOOLS first so it can retrieve current Composio/Rube tool schemas before acting. That reduces guesswork when tool names, parameters, or recommended plans change.
What should I not use this skill for?
Do not use it as a replacement for access-control review, legal retention policy, or bulk destructive cleanup without human verification. The skill can help automate Google Drive tasks, but you should provide strict constraints for deletions, sharing changes, ownership changes, or operations across large folder trees.
Does it work for File Automation beyond Google Drive?
The googledrive-automation for File Automation use case is specifically centered on Google Drive through the googledrive toolkit. If your workflow spans Gmail, Slack, Notion, or local files, you may need additional MCP tools or skills. This skill can still be one part of a broader workflow if Rube exposes the needed companion toolkits.
How to Improve googledrive-automation skill
Improve googledrive-automation prompts with exact file rules
The biggest quality gain comes from giving exact file-selection and safety rules. Include filename patterns, MIME types, date ranges, folder names, owner expectations, and whether shortcuts, shared drives, or trashed files should be included.
Instead of “organize reports,” say: “Find Google Sheets in folder Quarterly Reports modified in the last 90 days, group them by quarter in folders named 2025 Q1, 2025 Q2, and do not change sharing permissions.”
Common failure modes to prevent
The most common risks are acting on the wrong file, using stale assumptions about schemas, and applying a broad operation to too many Drive items. Prevent these by requiring tool discovery, read-only preview, ID confirmation, and a maximum action count before mutation.
For example: “Preview the first 20 matches and ask before moving anything if more than 20 files match.”
Iterate after the first output
After the first run, review the audit summary. If results are incomplete, ask the agent to refine the search query rather than immediately broadening permissions. Good follow-up instructions include: “include shared drives,” “exclude folders named Archive,” “match exact title only,” or “repeat using file IDs from the previous summary.”
Repository improvements worth adding
The skill would be stronger with a short README.md, example prompts for common Drive workflows, and a safety checklist for destructive operations. A small examples section covering search, create folder, move file, update metadata, and no-delete cleanup would make googledrive-automation easier to adopt without weakening its core requirement to search live Rube schemas first.