$ ~/registry/skill/composiohq-composio-skills-googledrive-automation

SKILL

googledrive-automation

Name: googledrive-automation
Author: Composio

Automate Google Drive file and folder workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt/documentation-style artifact with strong community adoption, and the provided material does not show built-in secrets or local code execution, so baseline risk is low. However, its intended use relies on Rube MCP to connect to external services and operate on Google Drive, which introduces normal caution around third-party endpoints and cloud data access.

CredentialsCaution

The material states 'no API keys needed,' but it also requires an active Google Drive connection via `RUBE_MANAGE_CONNECTIONS` and an auth link flow; this still implies third-party OAuth/connection tokens, even if no environment variables are declared by the skill itself. This creates normal cloud authorization/token exposure considerations, with no additional red flags shown.

Network egressCaution

The documentation explicitly instructs adding the remote MCP endpoint `https://rube.app/mcp` and references the Composio/Google Drive toolkit; user task content, tool discovery requests, and execution arguments are likely sent to that third-party service. This is normal egress for the stated functionality, but the actual data path depends on Rube/Composio and the material does not provide deeper data-handling details.

Code executionLow risk

The system marks it as prompt-only, and the provided material contains only usage guidance and call patterns, with no bundled scripts, install commands, or local execution capability shown. Based on the supplied material, there is no direct local code-execution red flag.

Data accessCaution

Its stated purpose is automating Google Drive operations, which means it may query or modify cloud files/folders after authorization; this is inherent to the tool category and warrants attention to the scope granted to the Google Drive account and the specific tool schemas. The material does not show requests for permissions clearly beyond what Drive automation would normally need.

Supply chainLow risk

The source is a GitHub open-source repository, and the system flags it as open-source with high community adoption (64.7k stars), which are strong risk-reducing signals. The license and maintenance status are not explicit, and practical use depends on external Rube/Composio services, but the current material does not support a high-risk supply-chain finding.

Recommendations

Before connecting, verify the privacy, retention, and logging practices of `rube.app` and Composio to avoid sending unnecessary sensitive filenames or content to third parties.
When authorizing Google Drive, prefer a least-privilege account or a test folder first, and confirm the visible/writable scope matches expectations.
Review the discovered tool schemas and arguments before running `RUBE_MULTI_EXECUTE_TOOL` to avoid unintended bulk edits or deletions.
Test in a controlled environment first and periodically revoke Google Drive authorizations that are no longer needed.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "googledrive-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/googledrive-automation/SKILL.md
2. Save it as ~/.claude/skills/googledrive-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Google Drive Automation via Rube MCP

Automate Google Drive operations through Composio's Google Drive toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/googledrive

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Google Drive connection via RUBE_MANAGE_CONNECTIONS with toolkit googledrive
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit googledrive
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Google Drive operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Google Drive task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["googledrive"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Google Drive-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `googledrive`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate Google Tasks and lists with bulk task management workflows.

ComposioGet→

$ loading_