Menu
Google Drive: List, search, inspect, download, and export files with alias-first `gws-account` flows for `work`, `personal`, and `columbia`.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Start a detached zellij session for a tracker-linked or natural-language task, and launch Codex or Claude as the default shell with an initial `$start-new-task ...` handoff prompt.
Initialize a new task folder with status.md, user_inputs/initial.md, user_inputs/input_artifacts/, task-progress-artifacts/, and task-progress-artifacts/scratchpad/. Supports GitHub issue URL inputs, Linear issue URL inputs, default Linear issue creation for trackerless starts, tracker-informed slugs, and machine/zellij metadata capture with optional live-session issue block sync.
Initialize a new task folder with status.md, user_inputs/initial.md, user_inputs/input_artifacts/, task-progress-artifacts/, and task-progress-artifacts/scratchpad/. Supports GitHub issue URL inputs, Linear issue URL inputs, default Linear issue creation for trackerless starts, tracker-informed slugs, and machine/zellij metadata capture with optional live-session issue block sync.
Rename Codex app thread labels and titles in local Codex state. Use when a user asks to rename, retitle, relabel, or make a Codex chat/thread easier to find in the Codex app sidebar or thread list, especially when the visible label still shows the first prompt such as "$start-new-task ZON-218".
Create compact Codex `/goal` plan files that require an implementation loop with Oracle GPT-5.5 Pro review between iterations. Use when the user wants a goal plan that explicitly sequences implementation, strongest-model Oracle review, rework from Oracle findings, repeated review until no material changes remain, and final verification.
Create a Linear ticket and immediately launch a detached zellij/Codex worker session for it. Use when the user asks to "create a ticket and start a session", "make a Linear task and $start-zellij-session-for-task", spin up a side worker for a new task, or repeat the common parent-orchestrator flow of drafting a scoped issue, linking it to a parent lane, and starting `$start-new-task ISSUE-ID`.
| name | gws-drive |
| description | Google Drive: List, search, inspect, download, and export files with alias-first `gws-account` flows for `work`, `personal`, and `columbia`. |
| metadata | {"openclaw":{"category":"productivity","requires":{"bins":["gws"]},"cliHelp":"gws drive --help"}} |
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, alias selection, global flags, and security rules. If missing, rungws generate-skillsto create it.
Use this skill when the user wants read-only Google Drive access from a specific saved account on this machine. Prefer gws-account <alias> ... over bare gws ....
gws-account work drive files list --params '{"pageSize": 10, "orderBy": "modifiedTime desc", "q": "trashed=false"}' --format json
gws-account personal drive files list --params "{\"pageSize\": 10, \"q\": \"name contains 'tax' and trashed=false\"}" --format json
gws-account columbia drive files list --params "{\"pageSize\": 10, \"q\": \"mimeType='application/vnd.google-apps.document' and trashed=false\"}" --format json
gws-account work drive files get --params '{"fileId": "<FILE_ID>", "fields": "id,name,mimeType,owners,webViewLink"}' --format json
gws-account personal drive files download --params '{"fileId": "<FILE_ID>"}' -o ./downloaded-file.bin
gws-account columbia drive files export --params '{"fileId": "<FILE_ID>", "mimeType": "text/plain"}' -o ./exported-doc.txt
Use download for uploaded/binary files and export for native Google Docs, Sheets, or Slides files.
For shared drives, set both supportsAllDrives and includeItemsFromAllDrives. Narrow to one shared drive with corpora=drive plus driveId:
gws-account work drive files list --params '{"corpora": "drive", "driveId": "<DRIVE_ID>", "includeItemsFromAllDrives": true, "supportsAllDrives": true, "pageSize": 10, "q": "trashed=false"}' --format json
gws-account work drive drives list --format json
Before calling an unfamiliar method, inspect it:
gws-account work drive --help
gws-account work drive files --help
gws-account work schema drive.files.list
Use gws-account <alias> schema drive.<resource>.<method> to inspect parameters, supported scopes, and response structure before building a command.
files.list, files.get, files.download, files.export, and drives.list unless the user explicitly asks for write access.fields when you only need specific metadata so responses stay small and readable.