google-drive

name	google-drive
description	Use Mail Pounder as the unified entrypoint for Google Drive, Docs, Sheets, and Slides. Use when Codex must find, fetch, organize, share, export, copy, move, upload, or delete files, or route a file-specific task to the Docs, Sheets, Slides, or Drive comments skill across one or more linked Google accounts.

Google Drive

Use Mail Pounder as one Google Workspace surface. Search spans every linked account and returns account provenance. Reads and mutations targeting an existing file resolve its owning account automatically. New files and uploads use the active account.

Account routing

1. Call google_workspace_list_accounts when the user asks which accounts are connected or the destination account matters.
2. Call google_workspace_select_account before creating a file, folder, upload, or outbound artifact in a non-active account.
3. Do not ask the user to reconnect merely because a search result belongs to another linked account.

Workflow

1. Ground the file with google_drive_search, google_drive_recent_documents, google_drive_list_folder, or google_drive_get_file_metadata unless the user supplied an exact URL or ID.
2. Use Drive tools for file lifecycle work: fetch, copy, folders, sharing, moves, uploads, imports, exports, revisions, and deletion.
3. Route content work to the narrowest sibling skill:
   • Comments: google-drive-comments
   • Docs: google-docs
   • Sheets: google-sheets
   • Slides: google-slides
4. Verify every write with metadata or content readback before returning a URL.

File handling

• Read metadata before export. Use google_drive_export_file only for native Docs, Sheets, or Slides. Use google_drive_fetch for PDFs, images, archives, Office files, audio, video, and other non-native files.
• For revision comparisons, call google_drive_list_file_revisions, fetch the requested revision with google_drive_fetch_file_revision, and compare it with the current file.
• For moves, inspect current parents first, then use google_drive_update_file with only the verified addParents and removeParents values.
• Preserve organization, sharing state, and unrelated parents unless the user explicitly requests changes.
• Treat permanent deletion and broad sharing as destructive. Confirm the exact file and clear user intent before acting.