google-drivelisted

Drive Google Drive via `curl + jq`. The user's OAuth bearer token is in `$GOOGLE_DRIVE_TOKEN`; every call needs it as `Authorization: Bearer $GOOGLE_DRIVE_TOKEN`. The token carries `drive.file` plus identity scopes (`openid email profile`) and can only access files the user selected, opened, created, or shared with this app. The Drive API returns standard JSON; failures surface as `{"error": {"code": 401|403|..., "message": "..."}}` — show that error verbatim to the user. `401` means the token expired and the user must re-install the connector. `403 insufficientPermissions` means the file was not shared with this app, or the action needs a broader Drive scope that is temporarily disabled during Google review. Do not use this skill for broad Drive discovery: no "list my recent files", full-text search across Drive, shared-with-me scans, root-folder cleanup, or bulk moves based on a Drive-wide query. Ask the user to pick or paste the exact file/folder IDs first. **Before any destructive write** (renaming, moving, trashing, or bulk-mutating files) show the exact target list and ask the user to confirm. Never trash by guessing an id — always echo back the file name + path you're about to touch. **Always start with `/about?fields=user`** to confirm the connection works AND learn which Google account you're operating against. ## Optional: Google Workspace CLI (`gws`) for uploads [`gws`](https://github.com/googleworkspace/cli) is Google's official CLI (not officially supported