メニュー
Google Drive CLI access via rclone. READ-ONLY for native Google formats (Sheets, Docs, Slides). Use for downloading, listing, searching Drive files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | rclone |
| description | Google Drive CLI access via rclone. READ-ONLY for native Google formats (Sheets, Docs, Slides). Use for downloading, listing, searching Drive files. |
| user-invocable | false |
Tool: rclone (open source, MIT license, 50k+ GitHub stars)
Traffic: Direct PC ↔ Google API, no third-party middleman
Config: ~\AppData\Roaming\rclone\rclone.conf
Remote name: gdrive:
rclone is READ-ONLY for native Google formats:
For creating Google Sheets: Use Chrome automation to create/duplicate, then MCP for cell manipulation.
# List folders at root
rclone lsd gdrive:
# List files in a folder
rclone ls gdrive:"YourCompany (Root)"
# Upload file
rclone copy file.txt gdrive:folder/
# Download file
rclone copy gdrive:file.txt ./
# Create folder
rclone mkdir gdrive:"New Folder"
# Move file
rclone move gdrive:file.txt gdrive:dest/
# Download Google Sheet as Excel
rclone copy gdrive:"path/to/sheet.xlsx" ./
# Sync local folder to Drive
rclone sync ./local-folder gdrive:remote-folder
# List with details (size, date)
rclone lsl gdrive:folder/
# Check what would be copied (dry run)
rclone copy --dry-run source dest
Clarification: Google Sheets ARE Google Drive files (native format). rclone handles them by exporting on download:
Use case: Reading Sheet data without browser automation. Download as xlsx, then parse locally.
# Download sheet and search contents
rclone copy gdrive:"path/to/MySheet" /tmp/
unzip -p /tmp/MySheet.xlsx xl/sharedStrings.xml | tr '<' '\n' | grep -i "searchterm"
This is faster and more reliable than browser automation for data extraction.
Auth expired: Re-run rclone config and re-authenticate the gdrive remote.
Quota errors: Google Drive API has rate limits. Add --drive-pacer-min-sleep 100ms for heavy operations.
Path with spaces: Always quote paths containing spaces: gdrive:"Folder Name/file.txt"
Google Apps Script development best practices learned from production. Use when building Apps Script automation, payment API integrations, Google Sheets menu functions, modal dialogs, Poka Yoke quality gates, or running Apps Script functions from CLI. Covers UI dialog philosophy, API field discovery, submission architecture (source_amount vs transfer_amount), clasp CLI logging, run-appscript.sh function execution, and gate flow design.
Orchestration overview for the autonomous issue dispatch system. Handles bugs AND features from ANY entry point. References the component skills (dispatcher, handler) and per-project skills (bug-intake, qa-submission). Use when user says "dispatch", "fix these issues", "batch implement", "implement this", "build this", "develop this", "here's a plan", or any implementation/feature/fix request — including direct conversational requests to Claude Code.
Generalized Slack bug intake. Scans bug-report channels, auto-fixes small bugs, dispatches big work with clear specs, defers only genuinely ambiguous items to owner. Uses emoji reactions to track state. Each repo provides workspace config via local bug-intake skill. Supports shared channels where multiple repos receive bugs from one Slack channel via semantic routing.
PreToolUse hooks that block direct production database access and raw SQL write operations. Prevents bypass scripts that skip Drizzle ORM migration tracking, and HARD BLOCKS raw psql writes with no bypass — all writes must go through Admin API.
Standard development SOP for ALL code changes — bug fixes, features, refactors, any implementation. Defines the universal pipeline (investigate → fix → test → deploy → QA) and scope-based decision matrix. Also provides continuous scanning mode for autonomous operation. Use when implementing ANY code change, fixing bugs, building features, or when user says "start dev loop", "cowork", "fix this", "implement this", "build this". Each workspace can override with local skill.
Knowledge management for Claude Code projects. Use when: creating skills or agents, deciding where to put new knowledge (skill vs CLAUDE.md vs reference-data vs memory vs agent), routing information, CLAUDE.md hygiene, editing/modifying CLAUDE.md or skills or agents or memory files, extracting content from bloated files, or any discussion about knowledge architecture, documentation structure, or SOP placement. MUST be invoked BEFORE proposing any edits to CLAUDE.md, skills, agents, or memory - no exceptions.