domains / families / documents / google-drive-automation

google-drive-automation

combined

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. Lightweight Google Drive integration with standalone OAuth authentication. No MCP server required. Full read/write access.

When to use

• You need to search, list, upload, download, move, or organize Google Drive files and folders.
• The task requires direct Drive read/write automation through local scripts in a Workspace account.
• You want file-level Drive operations without introducing an MCP server dependency.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies implement the same high-level task (Google Drive file operations) through fundamentally different mechanisms. The davepoon copy is an MCP-based procedure that requires the Rube MCP server, Composio's Google Drive toolkit, and specific RUBE_* and GOOGLEDRIVE_* tool calls. The sickn33 copy is a standalone, script-based procedure that uses local Python scripts (auth.py, drive.py) with OAuth and explicitly states that no MCP server is required. Because each copy contains material steps and constraints the other lacks (MCP tool sequences vs. local CLI commands), crowning one would hide a real alternative implementation.