Googledrive Automation
ComposioHQ/awesome-claude-skills
Automate Google Drive tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio).
Install Google Drive Automation
$ npx skills add davepoon/buildwithclaude --skill google-drive-automation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install davepoon/buildwithclaude google-drive-automation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/all-skills/skills/google-drive-automation .claude/skills/google-drive-automation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "google-drive-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/google-drive-automation into .claude/skills/google-drive-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-drive-automation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/google-drive-automationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add davepoon/buildwithclaude --skill google-drive-automation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install davepoon/buildwithclaude google-drive-automation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/all-skills/skills/google-drive-automation .agents/skills/google-drive-automation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "google-drive-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/google-drive-automation into .agents/skills/google-drive-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-drive-automation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davepoon/buildwithclaude --skill google-drive-automation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install davepoon/buildwithclaude google-drive-automation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/all-skills/skills/google-drive-automation .cursor/skills/google-drive-automation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "google-drive-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/google-drive-automation into .cursor/skills/google-drive-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-drive-automation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/davepoon/buildwithclaude.git --path plugins/all-skills/skills/google-drive-automation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add davepoon/buildwithclaude --skill google-drive-automation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install davepoon/buildwithclaude google-drive-automation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/all-skills/skills/google-drive-automation .gemini/skills/google-drive-automation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "google-drive-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/google-drive-automation into .gemini/skills/google-drive-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-drive-automation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install davepoon/buildwithclaude google-drive-automationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add davepoon/buildwithclaude --skill google-drive-automation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/all-skills/skills/google-drive-automation .github/skills/google-drive-automation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "google-drive-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/google-drive-automation into .github/skills/google-drive-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-drive-automation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davepoon/buildwithclaude --skill google-drive-automation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install davepoon/buildwithclaude google-drive-automation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/all-skills/skills/google-drive-automation .opencode/skills/google-drive-automation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "google-drive-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/google-drive-automation into .opencode/skills/google-drive-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-drive-automation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
google-drive-automation- GitHub stars
- 3.6k
- Used in
- 3 other repos
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,053 words
- Files
- 1
- Skills in repo
- 247
- Repo updated
- First seen
- Licence
- MIT
At a glance
Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio).
- Works in 4 steps: Upload and Download Files → Search and List Files → Share Files and Manage Permissions → …
- Tasks that involve App automation through connectors
- SKILL.md covers Prerequisites, Setup, Core Workflows and Common Patterns, plus 2 more sections
- Reaches rube.app
What it does
Google Drive Automation is an agent skill from davepoon/buildwithclaude. 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.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering App automation through connectors. It works with Google Drive and Composio. The repository describes itself as: A single hub to find Claude Skills, Agents, Commands, Hooks, Plugins, and Marketplace collections to extend Claude Code, Claude Desktop, Agent SDK and OpenClaw. The licence is MIT.
When your agent uses it
- Tasks that involve App automation through connectors
Example prompts
- “/google-drive-automation”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 616deb5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
rube.app
Also links to:
composio.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Google Drive Automation loads about 2.5k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 1,053 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from davepoon/buildwithclaude at commit 616deb5, republished under its MIT licence (© davepoon). 1,053 words, ~2,526 tokens.
Download SKILL.mdSave it as
.claude/skills/google-drive-automation/SKILL.md (or your agent's skills folder).- name
- google-drive-automation
- description
- 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.
- requires.mcp
- rube
- category
- storage-docs
Google Drive Automation via Rube MCP
Automate Google Drive workflows including file upload/download, search, folder management, sharing/permissions, and organization through Composio's Google Drive toolkit.
Toolkit docs: composio.dev/toolkits/googledrive
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Google Drive connection via
RUBE_MANAGE_CONNECTIONSwith toolkitgoogledrive - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitgoogledrive - If connection is not ACTIVE, follow the returned auth link to complete Google OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Upload and Download Files
When to use: User wants to upload files to or download files from Google Drive
Tool sequence:
GOOGLEDRIVE_FIND_FILE- Locate target folder for upload [Prerequisite]GOOGLEDRIVE_UPLOAD_FILE- Upload a file (max 5MB) [Required]GOOGLEDRIVE_RESUMABLE_UPLOAD- Upload large files [Fallback]GOOGLEDRIVE_DOWNLOAD_FILE- Download a file by ID [Required]GOOGLEDRIVE_DOWNLOAD_FILE_OPERATION- Track long-running downloads [Fallback]GOOGLEDRIVE_GET_FILE_METADATA- Verify file after upload/download [Optional]
Key parameters:
file_to_upload: Object withname,mimetype, ands3key(file must be in internal storage)folder_to_upload_to: Target folder ID (optional; uploads to root if omitted)file_id: ID of file to downloadmime_type: Export format for Google Workspace files only (omit for native files)
Pitfalls:
GOOGLEDRIVE_UPLOAD_FILErequiresfile_to_upload.s3key; files must already be in internal storage- For non-Google formats (Excel, PDF), do NOT set
mime_type; it causes errors for native files - Download responses provide a temporary URL at
data.downloaded_file_content.s3url, not inline bytes - Use
GOOGLEDRIVE_RESUMABLE_UPLOADfor files >5MB or when basic uploads fail
2. Search and List Files
When to use: User wants to find specific files or browse Drive contents
Tool sequence:
GOOGLEDRIVE_FIND_FILE- Search by name, content, type, date, or folder [Required]GOOGLEDRIVE_LIST_FILES- Browse files with folder scoping [Alternative]GOOGLEDRIVE_LIST_SHARED_DRIVES- Enumerate shared drives [Optional]GOOGLEDRIVE_GET_FILE_METADATA- Get detailed file info [Optional]GOOGLEDRIVE_GET_ABOUT- Check storage quota and supported formats [Optional]
Key parameters:
q: Drive query string (e.g., "name contains 'report'", "mimeType = 'application/pdf'")corpora: Search scope ('user', 'domain', 'drive', 'allDrives')fields: Response fields to include (e.g., 'files(id,name,mimeType)')orderBy: Sort key ('modifiedTime desc', 'name', 'quotaBytesUsed desc')pageSize: Results per page (max 1000)pageToken: Pagination cursor fromnextPageTokenfolder_id: Scope search to a specific folder
Pitfalls:
- 403 PERMISSION_DENIED if OAuth scopes insufficient for shared drives
- Pagination required; files are in
response.data.files; follownextPageTokenuntil exhausted corpora="domain"may trigger 400; try"allDrives"withincludeItemsFromAllDrives=true- Query complexity limits: >5-10 OR clauses may error "The query is too complex"
- Wildcards (*) NOT supported in
name; usecontainsfor partial matching - 'My Drive' is NOT searchable by name; use
folder_id='root'for root folder - User email searches: use
'user@example.com' in owners(NOTowner:user@example.com)
3. Share Files and Manage Permissions
When to use: User wants to share files or manage access permissions
Tool sequence:
GOOGLEDRIVE_FIND_FILE- Locate the file to share [Prerequisite]GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE- Set sharing permission [Required]GOOGLEDRIVE_LIST_PERMISSIONS- View current permissions [Optional]GOOGLEDRIVE_GET_PERMISSION- Inspect a specific permission [Optional]GOOGLEDRIVE_UPDATE_PERMISSION- Modify existing permission [Optional]GOOGLEDRIVE_DELETE_PERMISSION- Revoke access [Optional]
Key parameters:
file_id: ID of file to sharetype: 'user', 'group', 'domain', or 'anyone'role: 'owner', 'organizer', 'fileOrganizer', 'writer', 'commenter', 'reader'email_address: Required for type='user' or 'group'domain: Required for type='domain'transfer_ownership: Required when role='owner'
Pitfalls:
- Invalid type/email combinations trigger 4xx errors
- Using
type='anyone'or powerful roles is risky; get explicit user confirmation - Org policies may block certain sharing types, causing 403
- Permission changes may take time to propagate
- Use
GMAIL_SEARCH_PEOPLEto resolve contact names to emails before sharing
Show full SKILL.md (455 more words)Show less
4. Create and Organize Folders
When to use: User wants to create folder structures or move files between folders
Tool sequence:
GOOGLEDRIVE_FIND_FILE- Check if folder already exists [Prerequisite]GOOGLEDRIVE_CREATE_FOLDER- Create a new folder [Required]GOOGLEDRIVE_GET_FILE_METADATA- Verify created folder [Optional]GOOGLEDRIVE_MOVE_FILE- Move files between folders [Optional]GOOGLEDRIVE_UPDATE_FILE_PUT- Update file metadata/parents [Alternative]
Key parameters:
name: Folder nameparent_id: Parent folder ID (NOT name); omit for rootfile_id: File to moveadd_parents: Destination folder ID for moveremove_parents: Source folder ID to remove from
Pitfalls:
GOOGLEDRIVE_CREATE_FOLDERrequiresparent_idas an ID, not a folder name- Using
parent_id="root"creates at top level; for nested paths, chain folder IDs GOOGLEDRIVE_FIND_FILEreturns ~100 items/page; follownextPageTokenfor large drives- Move operations can leave items with multiple parents; use
remove_parentsfor true moves - Always verify parent folder exists before creating children
Common Patterns
ID Resolution
- File/folder name -> ID:
GOOGLEDRIVE_FIND_FILEwithqparameter - Root folder: Use
folder_id='root'or'root' in parents - Shared drive -> driveId:
GOOGLEDRIVE_LIST_SHARED_DRIVES - Contact name -> email:
GMAIL_SEARCH_PEOPLE(for sharing)
Query Syntax
Google Drive uses a specific query language:
- Name search:
"name contains 'report'"or"name = 'exact.pdf'" - Type filter:
"mimeType = 'application/pdf'"or"mimeType = 'application/vnd.google-apps.folder'" - Folder scoping:
"'FOLDER_ID' in parents" - Date filter:
"modifiedTime > '2024-01-01T00:00:00'" - Combine with
and/or/not:"name contains 'report' and trashed = false" - Boolean filters:
"sharedWithMe = true","starred = true","trashed = false"
Pagination
- Follow
nextPageTokenuntil absent for complete results - Set
pageSizeexplicitly (default 100, max 1000) - De-duplicate results if running multiple searches
Export Formats
For Google Workspace files, set mime_type to export:
- Docs:
application/pdf,text/plain,text/html,application/vnd.openxmlformats-officedocument.wordprocessingml.document - Sheets:
text/csv,application/vnd.openxmlformats-officedocument.spreadsheetml.sheet - Slides:
application/pdf,application/vnd.openxmlformats-officedocument.presentationml.presentation
Known Pitfalls
- Internal storage required: Upload requires files in internal S3 storage (s3key)
- Export vs download: Set
mime_typeONLY for Google Workspace files; omit for native files - Temporary URLs: Downloaded content via
s3urlis temporary; fetch promptly - Query complexity: >5-10 OR clauses may error; split complex searches into multiple queries
- Shared drive scoping: Missing drive permissions yield empty results; verify access first
- No wildcards: Use
containsoperator instead of*for partial name matching - Folder creation chains: Always pass folder IDs (not names) as
parent_id - Multiple parents: Move operations may leave items with multiple parents; use
remove_parents - Rate limits: Heavy searches/exports can trigger 403/429; implement backoff
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| Search files | GOOGLEDRIVE_FIND_FILE | q, corpora, pageSize |
| List files | GOOGLEDRIVE_LIST_FILES | folderId, q, orderBy |
| Upload file | GOOGLEDRIVE_UPLOAD_FILE | file_to_upload, folder_to_upload_to |
| Resumable upload | GOOGLEDRIVE_RESUMABLE_UPLOAD | file data |
| Download file | GOOGLEDRIVE_DOWNLOAD_FILE | file_id, mime_type (Workspace only) |
| File metadata | GOOGLEDRIVE_GET_FILE_METADATA | fileId, fields |
| Create folder | GOOGLEDRIVE_CREATE_FOLDER | name, parent_id |
| Move file | GOOGLEDRIVE_MOVE_FILE | file_id, add_parents, remove_parents |
| Share file | GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE | file_id, role, type, email_address |
| List permissions | GOOGLEDRIVE_LIST_PERMISSIONS | fileId |
| Update permission | GOOGLEDRIVE_UPDATE_PERMISSION | file_id, permission_id |
| Delete permission | GOOGLEDRIVE_DELETE_PERMISSION | file_id, permission_id |
| List shared drives | GOOGLEDRIVE_LIST_SHARED_DRIVES | pageSize |
| Drive info | GOOGLEDRIVE_GET_ABOUT | (none) |
| Create shortcut | GOOGLEDRIVE_CREATE_SHORTCUT_TO_FILE | target file_id |
Powered by Composio
© davepoon, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/all-skills/skills/google-drive-automation of davepoon/buildwithclaude.
Open the folder on GitHubat commit 616deb5
Used in 3 other repositories
We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in davepoon/buildwithclaude, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Google Drive Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Google Drive Automation this skilldavepoon/buildwithclaude | 3.6k | 3 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Googledrive AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~747 | Automated safety check: Pass | None | |
| Composioyc-software/qm | 15k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None | |
| Abuselpdb AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~738 | Automated safety check: Pass | None | |
| Accredible Certificates AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~790 | Automated safety check: Pass | None |
Similar skills
Composio
yc-software/qm
Show the app connection picker or setup widget when users ask to connect apps, reopen setup, or need an app that isn't connected yet.
Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
Abuselpdb Automation
ComposioHQ/awesome-claude-skills
Automate Abuselpdb tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Accredible Certificates Automation
ComposioHQ/awesome-claude-skills
Automate Accredible Certificates tasks via Rube MCP (Composio).
Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
More from davepoon/buildwithclaude
All 247 skills in this repoiOS Hig Design Guide
davepoon/buildwithclaude
Build, update, and apply iOS design specifications using Apple Human Interface Guidelines (HIG) source data.
Video Downloader
davepoon/buildwithclaude
Download YouTube videos with customizable quality and format options.
Qwen Vision
davepoon/buildwithclaude
A skill your agent uses when the user asks to "analyze video", "watch this video", "what happens in this video", "describe this clip", "review this footage", "classify these videos", "compare…
Atlas Cloud Media
davepoon/buildwithclaude
Discover Atlas Cloud image and video models, inspect their live schemas, and submit one confirmed media generation request with bounded GET polling.
Browser Extension Launch
davepoon/buildwithclaude
面向没有编程经验的用户，把想法做成可试用的浏览器插件，并完成检查、商店材料、审核提交和上线验证；也用于继续已有插件、排错和发布新版。用户说“帮我做个插件”“把插件上架”“继续我的插件”时使用。普通网站开发、仅查询插件知识不触发。
Slack Gif Creator
davepoon/buildwithclaude
Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives.
Related
Works with
Categories
Questions about Google Drive Automation
What does Google Drive Automation do?
Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Google Drive Automation is an agent skill from davepoon/buildwithclaude. Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio).
When should I use Google Drive Automation?
Google Drive Automation fits situations like: tasks that involve App automation through connectors.
How do I install Google Drive Automation in Claude Code?
Run `npx skills add davepoon/buildwithclaude --skill google-drive-automation -a claude-code`. Or copy the skill folder (plugins/all-skills/skills/google-drive-automation in davepoon/buildwithclaude) into .claude/skills/google-drive-automation in your project. Claude Code loads it when a task matches its description.
How do I install Google Drive Automation in Codex?
Run `npx skills add davepoon/buildwithclaude --skill google-drive-automation -a codex`. Or copy the skill folder (plugins/all-skills/skills/google-drive-automation in davepoon/buildwithclaude) into .agents/skills/google-drive-automation in your project. Codex loads it when a task matches its description.
Can I use Google Drive Automation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davepoon/buildwithclaude --skill google-drive-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-drive-automation, .gemini/skills/google-drive-automation, .github/skills/google-drive-automation and .opencode/skills/google-drive-automation in your project.
What does Google Drive Automation need to run?
SKILL.md names no scripts, command-line tools or credentials: Google Drive Automation is instructions for the agent only.
Does Google Drive Automation access the network?
SKILL.md names 2 domains. In commands or code: rube.app; the agent is likely to contact it when it follows the instructions. As links in the text: composio.dev. This is read from the text; nothing was executed.
Is Google Drive Automation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Google Drive Automation use?
Google Drive Automation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Google Drive Automation use?
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Google Drive Automation?
Skills that share tags, products or a category with Google Drive Automation: Googledrive Automation (ComposioHQ/awesome-claude-skills, 77k stars), Composio (yc-software/qm, 15k stars), Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars) and Abuselpdb Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Google Drive Automation?
davepoon (a GitHub user) maintains it in davepoon/buildwithclaude, which has 3,610 GitHub stars. The repository holds 247 skills in this directory. The repository was last updated on October 9, 2026.
Source: davepoon/buildwithclaude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.