google-drive-automation – Agents & Automation skill for AI agents
Lightweight Google Drive integration with standalone OAuth authentication. No MCP server required. Full read/write access.
Install the google-drive-automation skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/google-drive-automation-59db3.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /google-drive-automation – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/google-drive-automation-59db3.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $google-drive-automation – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/google-drive-automation-59db3.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /google-drive-automation – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/google-drive-automation-59db3.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /google-drive-automation – then describe the task you want done.
SKILL.md content
Supporting material availability
This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files:
<support-root>/scripts/auth.py<support-root>/scripts/drive.py
Ask for the original supporting material or an existing installation before using a step that depends on these paths; this catalog does not identify a verified download source for them. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable.
Google Drive
Lightweight Google Drive integration with standalone OAuth authentication. No MCP server required. Full read/write access.
> Account support and OAuth scopes depend on the missing upstream scripts; verify the actual OAuth application before login. This entry does not establish a general restriction on personal Google accounts.
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.
First-Time Setup
Authenticate with Google (opens browser):
python scripts/auth.py loginCheck authentication status:
python scripts/auth.py statusLogout when needed:
python scripts/auth.py logoutRead Commands
All operations via scripts/drive.py. Auto-authenticates on first use if not logged in.
# Search for files (full-text search)
python scripts/drive.py search "quarterly report"
# Search by title only
python scripts/drive.py search "title:budget"
# Search using Google Drive URL (extracts ID automatically)
python scripts/drive.py search "https://drive.google.com/drive/folders/1ABC123..."
# Search files shared with you
python scripts/drive.py search --shared-with-me
# Search with pagination
python scripts/drive.py search "report" --limit 5 --page-token "..."
# Find a folder by exact name
python scripts/drive.py find-folder "Project Documents"
# List files in root Drive
python scripts/drive.py list
# List files in a specific folder
python scripts/drive.py list 1ABC123xyz --limit 20
# Download a file
python scripts/drive.py download 1ABC123xyz ./downloads/report.pdfResolve scripts relative to the reviewed <support-root>, not an unrelated repository scripts/ folder. Before writes, confirm exact file/folder IDs, destination and permissions; moving/trashing content may affect collaborators. A read request does not authorize changes, sharing or broader OAuth scopes.
Write Commands
# Upload a file to Drive root
python scripts/drive.py upload ~/Documents/report.pdf
# Upload to a specific folder
python scripts/drive.py upload ~/Documents/report.pdf --folder 1ABC123xyz
# Upload with a custom name
python scripts/drive.py upload ~/Documents/report.pdf --name "Q4 Report.pdf"
# Create a new folder
python scripts/drive.py create-folder "Project Documents"
# Create a folder inside another folder
python scripts/drive.py create-folder "Attachments" --parent 1ABC123xyz
# Move a file to a different folder
python scripts/drive.py move FILE_ID DESTINATION_FOLDER_ID
# Copy a file
python scripts/drive.py copy FILE_ID
python scripts/drive.py copy FILE_ID --name "Report Copy" --folder 1ABC123xyz
# Rename a file or folder
python scripts/drive.py rename FILE_ID "New Name.pdf"
# Move a file to trash
python scripts/drive.py trash FILE_IDSearch Query Formats
The search command supports multiple query formats:
| Format | Example | Description |
|--------|---------|-------------|
| Full-text | "quarterly report" | Searches file contents and names |
| Title | "title:budget" | Searches file names only |
| URL | https://drive.google.com/... | Extracts and uses file/folder ID |
| Folder ID | 1ABC123... | Lists folder contents (25+ char IDs) |
| Native query | mimeType='application/pdf' | Pass-through Drive query syntax |
File ID Format
Google Drive uses long IDs like 1ABC123xyz_-abc123. Get IDs from:
searchresultsfind-folderresultslistresults- Google Drive URLs
Download Limitations
- Regular files (PDFs, images, etc.) download directly
- Google Docs/Sheets/Slides cannot be downloaded via this tool
- For Google Workspace files, use export or dedicated tools
Token Management
Upstream describes token storage using the system keyring; verify actual implementation and fallback behavior before relying on it:
- macOS: Keychain
- Windows: Windows Credential Locker
- Linux: Secret Service API (GNOME Keyring, KDE Wallet, etc.)
Service name: google-drive-skill-oauth
The upstream integration describes a cloud-function refresh flow. Verify its operator, destination, scopes and token handling from the actual scripts before transmitting tokens; do not assume Google operates an endpoint because it is hosted on its infrastructure.
Limitations
- 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.
Related skills
- google-sheets-automation – Read and edit Google Sheets through an available authenticated connector or reviewed API…
- googlesheets-automation – Automate Google Sheets operations (read, write, format, filter, manage spreadsheets) via…
- setup – Set up a new autoresearch experiment interactively. Collects domain, target file, eval…
- grok-build – Delegate well-specified implementation tasks to xAI's Grok Build CLI running headlessly…
- helium-mcp – Connect to Helium's MCP server for news research, media bias analysis, balanced…
- helpdesk-automation – Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned…
- hf-mcp – Use Hugging Face Hub via MCP server tools. Search models, datasets, Spaces, papers. Get…
- hf-mem – Hugging Face CLI to estimate the required memory to load Safetensors or GGUF model…