{"id":"c0a32332-241a-4b5b-82c2-f1da12af7222","entityType":"agent","slug":"clawhub-oomol-oo-googledrive","name":"Google Drive","canonicalUrl":"https://www.xpersona.co/agent/clawhub-oomol-oo-googledrive","canonicalPath":"/agent/clawhub-oomol-oo-googledrive","generatedAt":"2026-10-11T07:40:50.395Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:14:34.174Z","emptyReason":null},"description":"Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-googledrive","sourceUrl":"https://clawhub.ai/oomol/oo-googledrive","homepage":"https://clawhub.ai/oomol/skills/oo-googledrive","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/oomol/oo-googledrive","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/oomol/skills/oo-googledrive","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Google Drive technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:14:34.174Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:14:34.174Z","emptyReason":null},"stars":null,"forks":null,"downloads":1163,"packageName":null,"latestVersion":"1.0.7","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:14:34.111Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T04:14:34.174Z","lastCrawledAt":"2026-10-11T04:14:34.111Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T04:14:34.111Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.7","createdAt":"2026-09-20T03:19:14.808Z","changelog":"- Adds Google Drive support through the OOMOL-connected `googledrive` connector and `oo` CLI. - Supports Drive account, quota, app metadata, shared drive, file, permission, label, revision, change, approval, and access proposal workflows. - Enables file creation, copying, upload/update, export, download, listing, deletion, trash management, and ID generation. - Includes collaboration actions for comments and replies, including create, list, update, and delete operations. - Documents safety expectations for read, write, and destructive actions, with schema inspection before running connector payloads. Source: `oomol-lab/skills@792ad44`","fileCount":3,"zipByteSize":4168},{"version":"1.0.6","createdAt":"2026-09-15T05:09:58.136Z","changelog":"- Operate Google Drive through the OOMOL-connected `oo` CLI. - Read, create, update, copy, export, download, and delete Drive files and folders. - Manage shared drives, permissions, comments, replies, labels, revisions, and change tracking. - Inspect live action schemas before submitting JSON payloads. - Require confirmation for state-changing or destructive actions and provide first-time setup guidance for authentication and connections. Source: `oomol-lab/skills@75bac03`","fileCount":3,"zipByteSize":4165},{"version":"1.0.4","createdAt":"2026-08-25T04:45:12.472Z","changelog":"- Enables Google Drive operations through the OOMOL-connected `googledrive` connector and `oo` CLI. - Supports Drive account, file, shared drive, app, change, approval, and access proposal read workflows. - Provides file creation, copy, update, export, download, label, trash, and permission management actions. - Includes collaboration actions for comments, replies, approvals, permissions, and revisions. - Documents safety expectations for read, write, and destructive actions, including confirmation before state-changing operations. Source: `oomol-lab/skills@3e4b3ff`","fileCount":3,"zipByteSize":4316},{"version":"1.0.3","createdAt":"2026-06-09T10:18:08.305Z","changelog":"- Operates Google Drive through the OOMOL `googledrive` connector and `oo` CLI using server-managed credentials. - Provides read access for account details, files, shared drives, permissions, comments, replies, revisions, labels, apps, approvals, and Drive changes. - Supports file and shared drive workflows including create, copy, update, export, generate IDs, hide/unhide drives, and trash management. - Manages collaboration features such as comments, replies, permissions, access proposals, and approval listings. - Includes explicit safety guidance for write and destructive actions, requiring schema inspection and user confirmation before state-changing operations. Source: `oomol-lab/skills@146ef20`","fileCount":3,"zipByteSize":4271},{"version":"1.0.2","createdAt":"2026-06-09T03:51:36.064Z","changelog":"- Provides OOMOL `oo` CLI access to Google Drive through the `googledrive` connector. - Supports file workflows including list, get, create, copy, update, delete, export, trash emptying, generated IDs, and label operations. - Covers shared drive management: create, list, get, update, hide, unhide, and delete shared drives. - Includes collaboration actions for comments, replies, approvals, access proposals, permissions, and revisions. - Documents safe usage rules, live schema inspection, JSON execution format, and first-time setup/auth troubleshooting. Source: `oomol-lab/skills@e3717ff`","fileCount":46,"zipByteSize":28176},{"version":"1.0.1","createdAt":"2026-06-05T05:13:08.610Z","changelog":"- Operates Google Drive through the OOMOL `googledrive` connector using the `oo` CLI and server-side injected credentials. - Supports full file and folder workflows: search, metadata lookup, create, upload, download, export, copy, move, rename, edit, trash, restore, and delete. - Manages sharing and access with permission create, list, get, patch, update, delete, and email-to-permission ID lookup actions. - Covers collaboration features including comments, replies, approvals, access proposals, revisions, and Drive labels. - Includes shared drive management for listing, creating, updating, hiding, unhiding, and deleting shared drives, with legacy Team Drive aliases. Source: `oomol-lab/skills@281c392`","fileCount":70,"zipByteSize":43452},{"version":"1.0.0","createdAt":"2026-06-03T14:32:13.644Z","changelog":"- Initial release of `oo-googledrive`, an OOMOL skill for operating Google Drive through the `googledrive` connector and `oo` CLI. - Supports core file and folder workflows: search, create, upload, download, export, copy, move, rename, trash, restore, and delete. - Provides metadata and revision operations, including file metadata reads, patch/update flows, revision listing, revision lookup, and revision metadata updates. - Includes sharing and access management actions for permissions, permission lookup, permission updates, access proposals, and shared drive access. - Covers collaboration features such as Drive comments, replies, approvals, labels, and change-listing for incremental sync workflows. - Adds shared drive support, including listing, creating, updating, hiding, unhiding, and deleting shared drives, with Team Drive compatibility aliases.","fileCount":69,"zipByteSize":42710}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-googledrive","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-googledrive` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/oomol/oo-googledrive before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-googledrive/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-googledrive/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-googledrive/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-googledrive/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-googledrive/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-googledrive/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T07:40:50.392Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-googledrive/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-googledrive/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-googledrive/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-googledrive/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:14:34.174Z","emptyReason":null},"readme":"Skill: Google Drive\n\nOwner: oomol\n\nSummary: Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly.\n\nTags: latest:1.0.7\n\nVersion history:\n\nv1.0.7 | 2026-09-20T03:19:14.808Z | user\n\n- Adds Google Drive support through the OOMOL-connected `googledrive` connector and `oo` CLI.\n- Supports Drive account, quota, app metadata, shared drive, file, permission, label, revision, change, approval, and access proposal workflows.\n- Enables file creation, copying, upload/update, export, download, listing, deletion, trash management, and ID generation.\n- Includes collaboration actions for comments and replies, including create, list, update, and delete operations.\n- Documents safety expectations for read, write, and destructive actions, with schema inspection before running connector payloads.\n\nSource: `oomol-lab/skills@792ad44`\n\nv1.0.6 | 2026-09-15T05:09:58.136Z | user\n\n- Operate Google Drive through the OOMOL-connected `oo` CLI.\n- Read, create, update, copy, export, download, and delete Drive files and folders.\n- Manage shared drives, permissions, comments, replies, labels, revisions, and change tracking.\n- Inspect live action schemas before submitting JSON payloads.\n- Require confirmation for state-changing or destructive actions and provide first-time setup guidance for authentication and connections.\n\nSource: `oomol-lab/skills@75bac03`\n\nv1.0.4 | 2026-08-25T04:45:12.472Z | user\n\n- Enables Google Drive operations through the OOMOL-connected `googledrive` connector and `oo` CLI.\n- Supports Drive account, file, shared drive, app, change, approval, and access proposal read workflows.\n- Provides file creation, copy, update, export, download, label, trash, and permission management actions.\n- Includes collaboration actions for comments, replies, approvals, permissions, and revisions.\n- Documents safety expectations for read, write, and destructive actions, including confirmation before state-changing operations.\n\nSource: `oomol-lab/skills@3e4b3ff`\n\nv1.0.3 | 2026-06-09T10:18:08.305Z | user\n\n- Operates Google Drive through the OOMOL `googledrive` connector and `oo` CLI using server-managed credentials.\n- Provides read access for account details, files, shared drives, permissions, comments, replies, revisions, labels, apps, approvals, and Drive changes.\n- Supports file and shared drive workflows including create, copy, update, export, generate IDs, hide/unhide drives, and trash management.\n- Manages collaboration features such as comments, replies, permissions, access proposals, and approval listings.\n- Includes explicit safety guidance for write and destructive actions, requiring schema inspection and user confirmation before state-changing operations.\n\nSource: `oomol-lab/skills@146ef20`\n\nv1.0.2 | 2026-06-09T03:51:36.064Z | user\n\n- Provides OOMOL `oo` CLI access to Google Drive through the `googledrive` connector.\n- Supports file workflows including list, get, create, copy, update, delete, export, trash emptying, generated IDs, and label operations.\n- Covers shared drive management: create, list, get, update, hide, unhide, and delete shared drives.\n- Includes collaboration actions for comments, replies, approvals, access proposals, permissions, and revisions.\n- Documents safe usage rules, live schema inspection, JSON execution format, and first-time setup/auth troubleshooting.\n\nSource: `oomol-lab/skills@e3717ff`\n\nv1.0.1 | 2026-06-05T05:13:08.610Z | user\n\n- Operates Google Drive through the OOMOL `googledrive` connector using the `oo` CLI and server-side injected credentials.\n- Supports full file and folder workflows: search, metadata lookup, create, upload, download, export, copy, move, rename, edit, trash, restore, and delete.\n- Manages sharing and access with permission create, list, get, patch, update, delete, and email-to-permission ID lookup actions.\n- Covers collaboration features including comments, replies, approvals, access proposals, revisions, and Drive labels.\n- Includes shared drive management for listing, creating, updating, hiding, unhiding, and deleting shared drives, with legacy Team Drive aliases.\n\nSource: `oomol-lab/skills@281c392`\n\nv1.0.0 | 2026-06-03T14:32:13.644Z | user\n\n- Initial release of `oo-googledrive`, an OOMOL skill for operating Google Drive through the `googledrive` connector and `oo` CLI.\n- Supports core file and folder workflows: search, create, upload, download, export, copy, move, rename, trash, restore, and delete.\n- Provides metadata and revision operations, including file metadata reads, patch/update flows, revision listing, revision lookup, and revision metadata updates.\n- Includes sharing and access management actions for permissions, permission lookup, permission updates, access proposals, and shared drive access.\n- Covers collaboration features such as Drive comments, replies, approvals, labels, and change-listing for incremental sync workflows.\n- Adds shared drive support, including listing, creating, updating, hiding, unhiding, and deleting shared drives, with Team Drive compatibility aliases.\n\nArchive index:\n\nArchive v1.0.7: 3 files, 4168 bytes\n\nFiles: skill-card.md (2080b), SKILL.md (7135b), _meta.json (133b)\n\nFile v1.0.7:SKILL.md\n\n---\nname: oo-googledrive\ndescription: \"Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Google Drive\"\n author: \"OOMOL\"\n version: \"1.0.7\"\n services: [\"googledrive\"]\n icon: \"https://static.oomol.com/logo/third-party/Google%20Drive.svg\"\n---\n\n# Google Drive\n\nOperate **Google Drive** through your OOMOL-connected account. This skill calls the `googledrive` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Google Drive. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"googledrive\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"googledrive\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `about.get` — Get Drive account information such as user details, quota, and supported capabilities.\n- `accessproposals.list` — List pending access proposals for a specific Drive file.\n- `approvals.list` — List approvals associated with a specific Drive file.\n- `apps.get` — Get metadata for a specific Google Drive app by app ID.\n- `changes.getStartPageToken` — Get the page token for monitoring future Drive changes.\n- `changes.list` — List file and drive changes for incremental sync workflows.\n- `comments.create` — Create a comment on a Drive file, optionally with anchor or quoted file content. [write]\n- `comments.delete` — Permanently delete a comment thread from a Drive file. [destructive]\n- `comments.get` — Get a specific comment on a Drive file by comment ID.\n- `comments.list` — List comments on a Drive file with pagination.\n- `comments.update` — Update the content of an existing Drive file comment. [write]\n- `drives.create` — Create a new shared drive. [write]\n- `drives.delete` — Permanently delete a shared drive. [destructive]\n- `drives.get` — Get a shared drive by drive ID.\n- `drives.hide` — Hide a shared drive from the default Drive view. [destructive]\n- `drives.list` — List shared drives accessible to the connected account.\n- `drives.unhide` — Unhide a shared drive and restore it to the default Drive view. [write]\n- `drives.update` — Update metadata or restrictions on a shared drive. [write]\n- `files.copy` — Copy a Drive file and optionally override official File metadata. [write]\n- `files.create` — Create a Drive file with official File metadata and optional connector media upload content. [write]\n- `files.delete` — Permanently delete a Drive file or folder by ID. [destructive]\n- `files.emptyTrash` — Permanently empty the user's trash or a shared drive's trash. [destructive]\n- `files.export` — Export a Google Workspace file to the requested MIME type and return a transit URL for the exported content.\n- `files.generateIds` — Generate one or more Drive file IDs for later create or copy requests. [write]\n- `files.get` — Get metadata for a Drive file by ID, or download stored file content with alt=media.\n- `files.list` — List Google Drive files using the official Drive query and pagination parameters.\n- `files.listLabels` — List the Drive labels currently applied to a file.\n- `files.modifyLabels` — Add, update, or remove Drive labels on a file. [destructive]\n- `files.update` — Patch a Drive file with official metadata, parent query parameters, and optional connector media upload content. [destructive]\n- `permissions.create` — Create a permission on a Drive file or shared drive. [write]\n- `permissions.delete` — Delete a permission from a Drive file or shared drive. [destructive]\n- `permissions.get` — Get a specific permission on a Drive file or shared drive by permission ID.\n- `permissions.list` — List permissions on a Drive file or shared drive.\n- `permissions.update` — Update an existing Drive permission using Google Drive v3 patch semantics. [write]\n- `replies.create` — Create a reply under an existing Drive file comment. [write]\n- `replies.delete` — Permanently delete a specific reply from a Drive file comment thread. [destructive]\n- `replies.get` — Get a specific reply under a Drive file comment.\n- `replies.list` — List replies under a Drive file comment with pagination.\n- `replies.update` — Update the content of an existing reply on a Drive file comment. [write]\n- `revisions.delete` — Permanently delete a specific revision from a Drive file. [destructive]\n- `revisions.get` — Get metadata for a specific Drive file revision.\n- `revisions.list` — List revision metadata for a Drive file.\n- `revisions.update` — Update revision metadata flags on a specific Drive file revision. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Google Drive state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Google Drive is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=googledrive\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Google Drive homepage: https://workspace.google.com/products/drive/\n\nFile v1.0.7:_meta.json\n\n{\n \"ownerId\": \"kn7frdsfy65xpg3b4vyrdjq6pd87yahh\",\n \"slug\": \"oo-googledrive\",\n \"version\": \"1.0.7\",\n \"publishedAt\": 1789874354808\n}\n\nFile v1.0.7:skill-card.md\n\n## Description:\n\nProvides agent guidance for reading, creating, updating, sharing, exporting, and deleting Google Drive content through an OOMOL-connected Google Drive account.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and developers use this skill to let an agent operate Google Drive files, shared drives, permissions, labels, revisions, comments, replies, changes, approvals, and access proposals through the OOMOL connector.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: First-time setup recommends running remote oo CLI installation scripts directly in a shell.\n\nMitigation: Review the oo CLI installation path before installing and prefer a verified package or documented manual installation method.\n\nRisk: The skill can guide write or destructive Google Drive actions that modify, delete, overwrite, or expose Drive content.\n\nMitigation: Confirm the exact target, payload, and expected effect with the user before any write or destructive action.\n\n## Reference(s):\n\n- [ClawHub Google Drive Skill](https://clawhub.ai/oomol/skills/oo-googledrive)\n- [Google Drive](https://workspace.google.com/products/drive/)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI Install Guide](https://cli.oomol.com/install-guide.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON payload guidance]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces connector schema inspection and action-running guidance for the oo CLI.]\n\n## Skill Version(s):\n\n1.0.7 (source: release evidence and SKILL.md frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.6: 3 files, 4165 bytes\n\nFiles: skill-card.md (2118b), SKILL.md (7111b), _meta.json (133b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: oo-googledrive\ndescription: \"Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Google Drive\"\n author: \"OOMOL\"\n version: \"1.0.6\"\n services: [\"googledrive\"]\n icon: \"https://static.oomol.com/logo/third-party/Google%20Drive.svg\"\n---\n\n# Google Drive\n\nOperate **Google Drive** through your OOMOL-connected account. This skill calls the `googledrive` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Google Drive. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"googledrive\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"googledrive\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `about.get` — Get Drive account information such as user details, quota, and supported capabilities.\n- `accessproposals.list` — List pending access proposals for a specific Drive file.\n- `approvals.list` — List approvals associated with a specific Drive file.\n- `apps.get` — Get metadata for a specific Google Drive app by app ID.\n- `changes.getStartPageToken` — Get the page token for monitoring future Drive changes.\n- `changes.list` — List file and drive changes for incremental sync workflows.\n- `comments.create` — Create a comment on a Drive file, optionally with anchor or quoted file content. [write]\n- `comments.delete` — Permanently delete a comment thread from a Drive file. [destructive]\n- `comments.get` — Get a specific comment on a Drive file by comment ID.\n- `comments.list` — List comments on a Drive file with pagination.\n- `comments.update` — Update the content of an existing Drive file comment. [write]\n- `drives.create` — Create a new shared drive. [write]\n- `drives.delete` — Permanently delete a shared drive. [destructive]\n- `drives.get` — Get a shared drive by drive ID.\n- `drives.hide` — Hide a shared drive from the default Drive view. [write]\n- `drives.list` — List shared drives accessible to the connected account.\n- `drives.unhide` — Unhide a shared drive and restore it to the default Drive view. [write]\n- `drives.update` — Update metadata or restrictions on a shared drive. [write]\n- `files.copy` — Copy a Drive file and optionally override official File metadata. [write]\n- `files.create` — Create a Drive file with official File metadata and optional connector media upload content. [write]\n- `files.delete` — Permanently delete a Drive file or folder by ID. [destructive]\n- `files.emptyTrash` — Permanently empty the user's trash or a shared drive's trash. [write]\n- `files.export` — Export a Google Workspace file to the requested MIME type and return a transit URL for the exported content.\n- `files.generateIds` — Generate one or more Drive file IDs for later create or copy requests. [write]\n- `files.get` — Get metadata for a Drive file by ID, or download stored file content with alt=media.\n- `files.list` — List Google Drive files using the official Drive query and pagination parameters.\n- `files.listLabels` — List the Drive labels currently applied to a file.\n- `files.modifyLabels` — Add, update, or remove Drive labels on a file. [write]\n- `files.update` — Patch a Drive file with official metadata, parent query parameters, and optional connector media upload content. [write]\n- `permissions.create` — Create a permission on a Drive file or shared drive. [write]\n- `permissions.delete` — Delete a permission from a Drive file or shared drive. [destructive]\n- `permissions.get` — Get a specific permission on a Drive file or shared drive by permission ID.\n- `permissions.list` — List permissions on a Drive file or shared drive.\n- `permissions.update` — Update an existing Drive permission using Google Drive v3 patch semantics. [write]\n- `replies.create` — Create a reply under an existing Drive file comment. [write]\n- `replies.delete` — Permanently delete a specific reply from a Drive file comment thread. [destructive]\n- `replies.get` — Get a specific reply under a Drive file comment.\n- `replies.list` — List replies under a Drive file comment with pagination.\n- `replies.update` — Update the content of an existing reply on a Drive file comment. [write]\n- `revisions.delete` — Permanently delete a specific revision from a Drive file. [destructive]\n- `revisions.get` — Get metadata for a specific Drive file revision.\n- `revisions.list` — List revision metadata for a Drive file.\n- `revisions.update` — Update revision metadata flags on a specific Drive file revision. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Google Drive state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Google Drive is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=googledrive\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Google Drive homepage: https://workspace.google.com/products/drive/\n\nFile v1.0.6:_meta.json\n\n{\n \"ownerId\": \"kn7frdsfy65xpg3b4vyrdjq6pd87yahh\",\n \"slug\": \"oo-googledrive\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1789448998136\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nGoogle Drive (workspace.google.com) skill for reading, creating, updating, and deleting Google Drive data through an OOMOL-connected account.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, external users, developers, and agent operators use this skill to inspect and manage Google Drive files, folders, shared drives, permissions, comments, replies, labels, revisions, and change tracking through the OOMOL oo CLI connector.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The setup guidance includes remote installer commands that execute code from an installer endpoint.\n\nMitigation: Use a trusted, pinned, signed, or checksum-verified installer before running setup commands.\n\nRisk: Google Drive write and destructive actions can change or remove Drive data.\n\nMitigation: Confirm the exact target, payload, and expected effect with the user before running write or destructive actions.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/oomol/skills/oo-googledrive)\n- [OOMOL Publisher Profile](https://clawhub.ai/user/oomol)\n- [Google Drive Homepage](https://workspace.google.com/products/drive/)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI Install Guide](https://cli.oomol.com/install-guide.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, shell commands, configuration, guidance, JSON]\n\n**Output Format:** [Markdown with inline shell commands and JSON connector responses]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Connector responses include data and meta.executionId; state-changing and destructive actions require user confirmation.]\n\n## Skill Version(s):\n\n1.0.6 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 3 files, 4316 bytes\n\nFiles: skill-card.md (2506b), SKILL.md (7111b), _meta.json (133b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: oo-googledrive\ndescription: \"Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Google Drive\"\n author: \"OOMOL\"\n version: \"1.0.4\"\n services: [\"googledrive\"]\n icon: \"https://static.oomol.com/logo/third-party/Google%20Drive.svg\"\n---\n\n# Google Drive\n\nOperate **Google Drive** through your OOMOL-connected account. This skill calls the `googledrive` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Google Drive. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"googledrive\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"googledrive\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `about.get` — Get Drive account information such as user details, quota, and supported capabilities.\n- `accessproposals.list` — List pending access proposals for a specific Drive file.\n- `approvals.list` — List approvals associated with a specific Drive file.\n- `apps.get` — Get metadata for a specific Google Drive app by app ID.\n- `changes.getStartPageToken` — Get the page token for monitoring future Drive changes.\n- `changes.list` — List file and drive changes for incremental sync workflows.\n- `comments.create` — Create a comment on a Drive file, optionally with anchor or quoted file content. [write]\n- `comments.delete` — Permanently delete a comment thread from a Drive file. [destructive]\n- `comments.get` — Get a specific comment on a Drive file by comment ID.\n- `comments.list` — List comments on a Drive file with pagination.\n- `comments.update` — Update the content of an existing Drive file comment. [write]\n- `drives.create` — Create a new shared drive. [write]\n- `drives.delete` — Permanently delete a shared drive. [destructive]\n- `drives.get` — Get a shared drive by drive ID.\n- `drives.hide` — Hide a shared drive from the default Drive view. [write]\n- `drives.list` — List shared drives accessible to the connected account.\n- `drives.unhide` — Unhide a shared drive and restore it to the default Drive view. [write]\n- `drives.update` — Update metadata or restrictions on a shared drive. [write]\n- `files.copy` — Copy a Drive file and optionally override official File metadata. [write]\n- `files.create` — Create a Drive file with official File metadata and optional connector media upload content. [write]\n- `files.delete` — Permanently delete a Drive file or folder by ID. [destructive]\n- `files.emptyTrash` — Permanently empty the user's trash or a shared drive's trash. [write]\n- `files.export` — Export a Google Workspace file to the requested MIME type and return a transit URL for the exported content.\n- `files.generateIds` — Generate one or more Drive file IDs for later create or copy requests. [write]\n- `files.get` — Get metadata for a Drive file by ID, or download stored file content with alt=media.\n- `files.list` — List Google Drive files using the official Drive query and pagination parameters.\n- `files.listLabels` — List the Drive labels currently applied to a file.\n- `files.modifyLabels` — Add, update, or remove Drive labels on a file. [write]\n- `files.update` — Patch a Drive file with official metadata, parent query parameters, and optional connector media upload content. [write]\n- `permissions.create` — Create a permission on a Drive file or shared drive. [write]\n- `permissions.delete` — Delete a permission from a Drive file or shared drive. [destructive]\n- `permissions.get` — Get a specific permission on a Drive file or shared drive by permission ID.\n- `permissions.list` — List permissions on a Drive file or shared drive.\n- `permissions.update` — Update an existing Drive permission using Google Drive v3 patch semantics. [write]\n- `replies.create` — Create a reply under an existing Drive file comment. [write]\n- `replies.delete` — Permanently delete a specific reply from a Drive file comment thread. [destructive]\n- `replies.get` — Get a specific reply under a Drive file comment.\n- `replies.list` — List replies under a Drive file comment with pagination.\n- `replies.update` — Update the content of an existing reply on a Drive file comment. [write]\n- `revisions.delete` — Permanently delete a specific revision from a Drive file. [destructive]\n- `revisions.get` — Get metadata for a specific Drive file revision.\n- `revisions.list` — List revision metadata for a Drive file.\n- `revisions.update` — Update revision metadata flags on a specific Drive file revision. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Google Drive state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Google Drive is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=googledrive\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Google Drive homepage: https://workspace.google.com/products/drive/\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn7frdsfy65xpg3b4vyrdjq6pd87yahh\",\n \"slug\": \"oo-googledrive\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1787633112472\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:\n\nEnables agents to operate Google Drive through the OOMOL `googledrive` connector and `oo` CLI for reading, creating, updating, and deleting Drive data.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and external agent users use this skill when they need an agent to inspect Google Drive metadata, list or retrieve files, manage collaboration objects, or perform confirmed state-changing Drive actions through an already connected OOMOL account.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can change Google Drive state, including files, shared drives, comments, replies, labels, permissions, revisions, and trash.\n\nMitigation: Confirm the exact payload and effect with the user before running write actions, and inspect the live connector schema before constructing the payload.\n\nRisk: Destructive actions can permanently delete Drive content, comments, replies, revisions, permissions, shared drives, or trash contents.\n\nMitigation: Get explicit user approval for the target and operation before any destructive action, and use read/list actions first when needed to verify the target.\n\nRisk: The connector acts on the user's connected Google Drive account.\n\nMitigation: Install and use the skill only when the user accepts this account-level access, and review prompts carefully before approving uploads, deletions, permission changes, or other state-changing actions.\n\n## Reference(s):\n\n- [Google Drive product page](https://workspace.google.com/products/drive/)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [Google Drive skill on ClawHub](https://clawhub.ai/oomol/skills/oo-googledrive)\n\n## Skill Output:\n\n**Output Type(s):** [Shell commands, JSON, Guidance]\n\n**Output Format:** [Markdown guidance with inline shell commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Connector responses use JSON with `data` and `meta.executionId`; write and destructive actions require user confirmation before execution.]\n\n## Skill Version(s):\n\n1.0.4 (source: server release metadata and skill frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.3: 3 files, 4271 bytes\n\nFiles: skill-card.md (2547b), SKILL.md (7063b), _meta.json (133b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: oo-googledrive\ndescription: \"Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Google Drive\"\n author: \"OOMOL\"\n version: \"1.0.3\"\n services: [\"googledrive\"]\n icon: \"https://static.oomol.com/logo/third-party/Google%20Drive.svg\"\n---\n\n# Google Drive\n\nOperate **Google Drive** through your OOMOL-connected account. This skill calls the `googledrive` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Google Drive. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"googledrive\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"googledrive\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `about.get` — Get Drive account information such as user details, quota, and supported capabilities.\n- `accessproposals.list` — List pending access proposals for a specific Drive file.\n- `approvals.list` — List approvals associated with a specific Drive file.\n- `apps.get` — Get metadata for a specific Google Drive app by app ID.\n- `changes.getStartPageToken` — Get the page token for monitoring future Drive changes.\n- `changes.list` — List file and drive changes for incremental sync workflows.\n- `comments.create` — Create a comment on a Drive file, optionally with anchor or quoted file content. [write]\n- `comments.delete` — Permanently delete a comment thread from a Drive file. [destructive]\n- `comments.get` — Get a specific comment on a Drive file by comment ID.\n- `comments.list` — List comments on a Drive file with pagination.\n- `comments.update` — Update the content of an existing Drive file comment. [write]\n- `drives.create` — Create a new shared drive. [write]\n- `drives.delete` — Permanently delete a shared drive. [destructive]\n- `drives.get` — Get a shared drive by drive ID.\n- `drives.hide` — Hide a shared drive from the default Drive view. [write]\n- `drives.list` — List shared drives accessible to the connected account.\n- `drives.unhide` — Unhide a shared drive and restore it to the default Drive view. [write]\n- `drives.update` — Update metadata or restrictions on a shared drive. [write]\n- `files.copy` — Copy a Drive file and optionally override official File metadata. [write]\n- `files.create` — Create a Drive file with official File metadata and optional connector media upload content. [write]\n- `files.delete` — Permanently delete a Drive file or folder by ID. [destructive]\n- `files.emptyTrash` — Permanently empty the user's trash or a shared drive's trash. [write]\n- `files.export` — Export a Google Workspace file to the requested MIME type and return a transit URL for the exported content.\n- `files.generateIds` — Generate one or more Drive file IDs for later create or copy requests. [write]\n- `files.get` — Get metadata for a Drive file by ID.\n- `files.list` — List Google Drive files using the official Drive query and pagination parameters.\n- `files.listLabels` — List the Drive labels currently applied to a file.\n- `files.modifyLabels` — Add, update, or remove Drive labels on a file. [write]\n- `files.update` — Patch a Drive file with official metadata, parent query parameters, and optional connector media upload content. [write]\n- `permissions.create` — Create a permission on a Drive file or shared drive. [write]\n- `permissions.delete` — Delete a permission from a Drive file or shared drive. [destructive]\n- `permissions.get` — Get a specific permission on a Drive file or shared drive by permission ID.\n- `permissions.list` — List permissions on a Drive file or shared drive.\n- `permissions.update` — Update an existing Drive permission using Google Drive v3 patch semantics. [write]\n- `replies.create` — Create a reply under an existing Drive file comment. [write]\n- `replies.delete` — Permanently delete a specific reply from a Drive file comment thread. [destructive]\n- `replies.get` — Get a specific reply under a Drive file comment.\n- `replies.list` — List replies under a Drive file comment with pagination.\n- `replies.update` — Update the content of an existing reply on a Drive file comment. [write]\n- `revisions.delete` — Permanently delete a specific revision from a Drive file. [destructive]\n- `revisions.get` — Get metadata for a specific Drive file revision.\n- `revisions.list` — List revision metadata for a Drive file.\n- `revisions.update` — Update revision metadata flags on a specific Drive file revision. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Google Drive state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Google Drive is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=googledrive\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Google Drive homepage: https://workspace.google.com/products/drive/\n\nFile v1.0.3:_meta.json\n\n{\n \"ownerId\": \"kn7frdsfy65xpg3b4vyrdjq6pd87yahh\",\n \"slug\": \"oo-googledrive\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1781000288305\n}\n\nFile v1.0.3:skill-card.md\n\n## Description:
\nGoogle Drive (workspace.google.com). Use this skill for Google Drive requests, including reading, creating, updating, and deleting Drive data through an OOMOL-connected account.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[oomol](https://clawhub.ai/user/oomol)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nEmployees, external users, and developers use this skill to let an agent inspect Google Drive content and perform file, shared drive, permission, comment, reply, revision, label, approval, and change workflows through OOMOL.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Read actions can expose private Google Drive files, permissions, metadata, comments, labels, revisions, and change history to the agent.
\nMitigation: Install only for users who want an agent to access their OOMOL-connected Google Drive, and treat read results as sensitive.
\nRisk: Write and destructive actions can change permissions, comments, labels, files, folders, shared drives, replies, revisions, or trash state.
\nMitigation: Inspect the live action schema, review the exact payload and effect, and require explicit user confirmation before state-changing or destructive operations.
\nRisk: First-time setup may require installing or authenticating the oo CLI.
\nMitigation: Verify the oo CLI installer source before setup and only run authentication or connection steps after a relevant command fails.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/oomol/oo-googledrive)
\n- [Publisher profile](https://clawhub.ai/user/oomol)
\n- [Google Drive](https://workspace.google.com/products/drive/)
\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON payload examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May return Google Drive connector responses as JSON when actions are executed.]
\n\n## Skill Version(s):
\n1.0.3 (source: frontmatter and server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.2: 46 files, 28176 bytes\n\nFiles: actions/about-get.md (694b), actions/accessproposals-list.md (719b), actions/approvals-list.md (686b), actions/apps-get.md (658b), actions/changes-getstartpagetoken.md (743b), actions/changes-list.md (682b), actions/comments-create.md (849b), actions/comments-delete.md (839b), actions/comments-get.md (676b), actions/comments-list.md (674b), actions/comments-update.md (822b), actions/drives-create.md (785b), actions/drives-delete.md (809b), actions/drives-get.md (644b), actions/drives-hide.md (667b), actions/drives-list.md (673b), actions/drives-unhide.md (692b), actions/drives-update.md (809b), actions/files-copy.md (809b), actions/files-create.md (846b), actions/files-delete.md (818b), actions/files-emptytrash.md (705b), actions/files-export.md (731b), actions/files-generateids.md (719b), actions/files-get.md (644b), actions/files-list.md (694b), actions/files-listlabels.md (693b), actions/files-modifylabels.md (700b), actions/files-update.md (866b), actions/permissions-create.md (836b), actions/permissions-delete.md (854b), actions/permissions-get.md (713b), actions/permissions-list.md (692b), actions/permissions-update.md (858b), actions/replies-create.md (816b), actions/replies-delete.md (849b), actions/replies-get.md (666b), actions/replies-list.md (679b), actions/replies-update.md (828b), actions/revisions-delete.md (847b), actions/revisions-get.md (676b), actions/revisions-list.md (673b), actions/revisions-update.md (839b), skill-card.md (2406b), SKILL.md (8152b), _meta.json (133b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: oo-googledrive\ndescription: \"Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Google Drive\"\n author: \"OOMOL\"\n version: \"1.0.2\"\n service: \"googledrive\"\n categories: \"Storage, Productivity\"\n homepage: \"https://workspace.google.com/products/drive/\"\n icon: \"https://static.oomol.com/logo/third-party/Google%20Drive.svg\"\n---\n\n# Google Drive\n\nOperate **Google Drive** through your OOMOL-connected account. This skill calls the `googledrive` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\nCategory: Storage, Productivity. Exposes 43 action(s).\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Google Drive. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"googledrive\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"googledrive\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with `oo connector schema` before constructing `--data`.\n\n## Available actions\n\n- [`about.get`](actions/about-get.md) — Get Drive account information such as user details, quota, and supported capabilities.\n- [`accessproposals.list`](actions/accessproposals-list.md) — List pending access proposals for a specific Drive file.\n- [`approvals.list`](actions/approvals-list.md) — List approvals associated with a specific Drive file.\n- [`apps.get`](actions/apps-get.md) — Get metadata for a specific Google Drive app by app ID.\n- [`changes.getStartPageToken`](actions/changes-getstartpagetoken.md) — Get the page token for monitoring future Drive changes.\n- [`changes.list`](actions/changes-list.md) — List file and drive changes for incremental sync workflows.\n- [`comments.create`](actions/comments-create.md) — Create a comment on a Drive file, optionally with anchor or quoted file content.\n- [`comments.delete`](actions/comments-delete.md) — Permanently delete a comment thread from a Drive file.\n- [`comments.get`](actions/comments-get.md) — Get a specific comment on a Drive file by comment ID.\n- [`comments.list`](actions/comments-list.md) — List comments on a Drive file with pagination.\n- [`comments.update`](actions/comments-update.md) — Update the content of an existing Drive file comment.\n- [`drives.create`](actions/drives-create.md) — Create a new shared drive.\n- [`drives.delete`](actions/drives-delete.md) — Permanently delete a shared drive.\n- [`drives.get`](actions/drives-get.md) — Get a shared drive by drive ID.\n- [`drives.hide`](actions/drives-hide.md) — Hide a shared drive from the default Drive view.\n- [`drives.list`](actions/drives-list.md) — List shared drives accessible to the connected account.\n- [`drives.unhide`](actions/drives-unhide.md) — Unhide a shared drive and restore it to the default Drive view.\n- [`drives.update`](actions/drives-update.md) — Update metadata or restrictions on a shared drive.\n- [`files.copy`](actions/files-copy.md) — Copy a Drive file and optionally override official File metadata.\n- [`files.create`](actions/files-create.md) — Create a Drive file with official File metadata and optional connector media upload content.\n- [`files.delete`](actions/files-delete.md) — Permanently delete a Drive file or folder by ID.\n- [`files.emptyTrash`](actions/files-emptytrash.md) — Permanently empty the user's trash or a shared drive's trash.\n- [`files.export`](actions/files-export.md) — Export a Google Workspace file to the requested MIME type and return a transit URL for the exported content.\n- [`files.generateIds`](actions/files-generateids.md) — Generate one or more Drive file IDs for later create or copy requests.\n- [`files.get`](actions/files-get.md) — Get metadata for a Drive file by ID.\n- [`files.list`](actions/files-list.md) — List Google Drive files using the official Drive query and pagination parameters.\n- [`files.listLabels`](actions/files-listlabels.md) — List the Drive labels currently applied to a file.\n- [`files.modifyLabels`](actions/files-modifylabels.md) — Add, update, or remove Drive labels on a file.\n- [`files.update`](actions/files-update.md) — Patch a Drive file with official metadata, parent query parameters, and optional connector media upload content.\n- [`permissions.create`](actions/permissions-create.md) — Create a permission on a Drive file or shared drive.\n- [`permissions.delete`](actions/permissions-delete.md) — Delete a permission from a Drive file or shared drive.\n- [`permissions.get`](actions/permissions-get.md) — Get a specific permission on a Drive file or shared drive by permission ID.\n- [`permissions.list`](actions/permissions-list.md) — List permissions on a Drive file or shared drive.\n- [`permissions.update`](actions/permissions-update.md) — Update an existing Drive permission using Google Drive v3 patch semantics.\n- [`replies.create`](actions/replies-create.md) — Create a reply under an existing Drive file comment.\n- [`replies.delete`](actions/replies-delete.md) — Permanently delete a specific reply from a Drive file comment thread.\n- [`replies.get`](actions/replies-get.md) — Get a specific reply under a Drive file comment.\n- [`replies.list`](actions/replies-list.md) — List replies under a Drive file comment with pagination.\n- [`replies.update`](actions/replies-update.md) — Update the content of an existing reply on a Drive file comment.\n- [`revisions.delete`](actions/revisions-delete.md) — Permanently delete a specific revision from a Drive file.\n- [`revisions.get`](actions/revisions-get.md) — Get metadata for a specific Drive file revision.\n- [`revisions.list`](actions/revisions-list.md) — List revision metadata for a Drive file.\n- [`revisions.update`](actions/revisions-update.md) — Update revision metadata flags on a specific Drive file revision.\n\n## Safety\n\n- Read actions (get / list / search) are safe to run directly.\n- **Create, update, send, or post actions change Google Drive state — confirm the exact payload and effect with the user before running.**\n- **Delete or remove actions are destructive — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Google Drive is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=googledrive\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Google Drive homepage: https://workspace.google.com/products/drive/\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn7frdsfy65xpg3b4vyrdjq6pd87yahh\",\n \"slug\": \"oo-googledrive\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1780977096064\n}\n\nFile v1.0.2:actions/about-get.md\n\n# Google Drive · `about.get`\n\nGet Drive account information such as user details, quota, and supported capabilities.\n\n- **Service**: `googledrive`\n- **Action**: `about.get`\n- **Action id**: `googledrive.about.get`\n- **Required scopes**: googledrive.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"about.get\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"about.get\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.2:actions/accessproposals-list.md\n\n# Google Drive · `accessproposals.list`\n\nList pending access proposals for a specific Drive file.\n\n- **Service**: `googledrive`\n- **Action**: `accessproposals.list`\n- **Action id**: `googledrive.accessproposals.list`\n- **Required scopes**: googledrive.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"accessproposals.list\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"accessproposals.list\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.2:actions/approvals-list.md\n\n# Google Drive · `approvals.list`\n\nList approvals associated with a specific Drive file.\n\n- **Service**: `googledrive`\n- **Action**: `approvals.list`\n- **Action id**: `googledrive.approvals.list`\n- **Required scopes**: googledrive.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"approvals.list\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"approvals.list\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.2:actions/apps-get.md\n\n# Google Drive · `apps.get`\n\nGet metadata for a specific Google Drive app by app ID.\n\n- **Service**: `googledrive`\n- **Action**: `apps.get`\n- **Action id**: `googledrive.apps.get`\n- **Required scopes**: googledrive.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"apps.get\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"apps.get\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.2:actions/changes-getstartpagetoken.md\n\n# Google Drive · `changes.getStartPageToken`\n\nGet the page token for monitoring future Drive changes.\n\n- **Service**: `googledrive`\n- **Action**: `changes.getStartPageToken`\n- **Action id**: `googledrive.changes.getStartPageToken`\n- **Required scopes**: googledrive.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"changes.getStartPageToken\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"changes.getStartPageToken\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.2:actions/changes-list.md\n\n# Google Drive · `changes.list`\n\nList file and drive changes for incremental sync workflows.\n\n- **Service**: `googledrive`\n- **Action**: `changes.list`\n- **Action id**: `googledrive.changes.list`\n- **Required scopes**: googledrive.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"changes.list\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"changes.list\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.2:actions/comments-create.md\n\n# Google Drive · `comments.create`\n\nCreate a comment on a Drive file, optionally with anchor or quoted file content.\n\n- **Service**: `googledrive`\n- **Action**: `comments.create`\n- **Action id**: `googledrive.comments.create`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"comments.create\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"comments.create\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.2:actions/comments-delete.md\n\n# Google Drive · `comments.delete`\n\nPermanently delete a comment thread from a Drive file.\n\n- **Service**: `googledrive`\n- **Action**: `comments.delete`\n- **Action id**: `googledrive.comments.delete`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"comments.delete\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"comments.delete\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Destructive action.** This removes or overwrites Google Drive data. Always confirm the target and get explicit user approval before running.\n\nFile v1.0.2:actions/comments-get.md\n\n# Google Drive · `comments.get`\n\nGet a specific comment on a Drive file by comment ID.\n\n- **Service**: `googledrive`\n- **Action**: `comments.get`\n- **Action id**: `googledrive.comments.get`\n- **Required scopes**: googledrive.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"comments.get\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"comments.get\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.2:actions/comments-list.md\n\n# Google Drive · `comments.list`\n\nList comments on a Drive file with pagination.\n\n- **Service**: `googledrive`\n- **Action**: `comments.list`\n- **Action id**: `googledrive.comments.list`\n- **Required scopes**: googledrive.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"comments.list\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"comments.list\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nArchive v1.0.1: 70 files, 43452 bytes\n\nFiles: actions/copy_file_advanced.md (885b), actions/copy_file.md (820b), actions/create_comment.md (844b), actions/create_drive.md (780b), actions/create_file_from_text.md (863b), actions/create_file.md (866b), actions/create_folder.md (833b), actions/create_permission.md (882b), actions/create_reply.md (858b), actions/create_team_drive.md (840b), actions/delete_comment.md (834b), actions/delete_drive.md (804b), actions/delete_file.md (836b), actions/delete_permission.md (849b), actions/delete_reply.md (839b), actions/delete_revision.md (842b), actions/delete_team_drive.md (856b), actions/download_file_operation.md (717b), actions/download_file.md (769b), actions/download_file2.md (672b), actions/edit_file.md (820b), actions/empty_trash.md (826b), actions/export_google_workspace_file.md (811b), actions/find_file.md (705b), actions/find_folder.md (711b), actions/generate_ids.md (694b), actions/get_about.md (694b), actions/get_app.md (653b), actions/get_changes_start_page_token.md (758b), actions/get_comment.md (801b), actions/get_drive.md (639b), actions/get_file_metadata.md (742b), actions/get_permission_id_for_email.md (751b), actions/get_permission.md (708b), actions/get_reply.md (786b), actions/get_revision.md (671b), actions/get_team_drive.md (691b), actions/google_drive_delete_folder_or_file_action.md (963b), actions/hide_drive.md (662b), actions/list_access_proposals.md (725b), actions/list_approvals.md (687b), actions/list_changes.md (682b), actions/list_comments.md (674b), actions/list_file_labels.md (693b), actions/list_permissions.md (692b), actions/list_replies.md (679b), actions/list_revisions.md (673b), actions/list_shared_drives.md (708b), actions/list_team_drives.md (710b), actions/modify_file_labels.md (830b), actions/move_file.md (799b), actions/parse_file.md (707b), actions/patch_permission.md (828b), actions/trash_file.md (829b), actions/unhide_drive.md (687b), actions/untrash_file.md (666b), actions/update_comment.md (817b), actions/update_drive.md (804b), actions/update_file_metadata_patch.md (879b), actions/update_file_revision_metadata.md (936b), actions/update_file.md (812b), actions/update_permission_patch.md (879b), actions/update_permission.md (866b), actions/update_reply.md (818b), actions/update_team_drive.md (840b), actions/upload_file.md (823b), actions/upload_update_file.md (861b), skill-card.md (2628b), SKILL.md (11453b), _meta.json (133b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: oo-googledrive\ndescription: \"Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Google Drive\"\n author: \"OOMOL\"\n version: \"1.0.1\"\n service: \"googledrive\"\n categories: \"Storage, Productivity\"\n homepage: \"https://workspace.google.com/products/drive/\"\n icon: \"https://static.oomol.com/logo/third-party/Google%20Drive.svg\"\n---\n\n# Google Drive\n\nOperate **Google Drive** through your OOMOL-connected account. This skill calls the `googledrive` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\nCategory: Storage, Productivity. Exposes 67 action(s).\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Google Drive. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"googledrive\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"googledrive\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with `oo connector schema` before constructing `--data`.\n\n## Available actions\n\n- [`copy_file`](actions/copy_file.md) — Legacy compatibility alias of `copy_file_advanced` with a simplified input shape.\n- [`copy_file_advanced`](actions/copy_file_advanced.md) — Copy a Drive file and optionally override metadata such as name, parents, description, or properties.\n- [`create_comment`](actions/create_comment.md) — Create a comment on a Drive file, optionally with anchor or quoted file content.\n- [`create_drive`](actions/create_drive.md) — Create a new shared drive.\n- [`create_file`](actions/create_file.md) — Create a Google Drive file with metadata only. Use a Google Workspace mime type to create an empty native file shell.\n- [`create_file_from_text`](actions/create_file_from_text.md) — Create a new Drive file from text content and optional metadata.\n- [`create_folder`](actions/create_folder.md) — Create a Google Drive folder, optionally under one or more parent folders.\n- [`create_permission`](actions/create_permission.md) — Create a permission on a Drive file or shared drive to share it with users, groups, domains, or anyone.\n- [`create_reply`](actions/create_reply.md) — Create a reply under an existing Drive file comment, or use an action payload such as resolve or reopen.\n- [`create_team_drive`](actions/create_team_drive.md) — Legacy compatibility alias of `create_drive` for Team Drives.\n- [`delete_comment`](actions/delete_comment.md) — Permanently delete a comment thread from a Drive file.\n- [`delete_drive`](actions/delete_drive.md) — Permanently delete a shared drive.\n- [`delete_file`](actions/delete_file.md) — Legacy compatibility alias for permanently deleting a Drive file by ID.\n- [`delete_permission`](actions/delete_permission.md) — Delete a permission from a Drive file or shared drive.\n- [`delete_reply`](actions/delete_reply.md) — Permanently delete a specific reply from a Drive file comment thread.\n- [`delete_revision`](actions/delete_revision.md) — Permanently delete a specific revision from a Drive file.\n- [`delete_team_drive`](actions/delete_team_drive.md) — Legacy compatibility alias of `delete_drive` for Team Drives.\n- [`download_file`](actions/download_file.md) — Download a Drive file by ID, or export a Google Workspace file when `mimeType` is provided. Returns a transit URL for the downloaded content.\n- [`download_file_operation`](actions/download_file_operation.md) — Compatibility alias of `download_file`.\n- [`download_file2`](actions/download_file2.md) — Compatibility alias of `download_file`.\n- [`edit_file`](actions/edit_file.md) — Overwrite an existing Drive file with text content and optional metadata changes.\n- [`empty_trash`](actions/empty_trash.md) — Permanently empty the user's trash or a shared drive's trash.\n- [`export_google_workspace_file`](actions/export_google_workspace_file.md) — Export a Google Workspace file to the requested MIME type and return a transit URL for the exported content.\n- [`find_file`](actions/find_file.md) — Search Google Drive files and folders with query, date, starred, trash, and shared-drive filters.\n- [`find_folder`](actions/find_folder.md) — Search Google Drive folders only, with the same query and pagination controls as `find_file`.\n- [`generate_ids`](actions/generate_ids.md) — Generate one or more Drive file IDs for later create or copy requests.\n- [`get_about`](actions/get_about.md) — Get Drive account information such as user details, quota, and supported capabilities.\n- [`get_app`](actions/get_app.md) — Get metadata for a specific Google Drive app by app ID.\n- [`get_changes_start_page_token`](actions/get_changes_start_page_token.md) — Get the page token for monitoring future Drive changes.\n- [`get_comment`](actions/get_comment.md) — Get a specific comment on a Drive file by comment ID.\n- [`get_drive`](actions/get_drive.md) — Get a shared drive by drive ID.\n- [`get_file_metadata`](actions/get_file_metadata.md) — Get metadata for a Drive file by ID, including mime type, parents, ownership, and trash state.\n- [`get_permission`](actions/get_permission.md) — Get a specific permission on a Drive file or shared drive by permission ID.\n- [`get_permission_id_for_email`](actions/get_permission_id_for_email.md) — Look up the Drive permission ID for an email address.\n- [`get_reply`](actions/get_reply.md) — Get a specific reply under a Drive file comment.\n- [`get_revision`](actions/get_revision.md) — Get metadata for a specific Drive file revision.\n- [`get_team_drive`](actions/get_team_drive.md) — Legacy compatibility alias of `get_drive` for Team Drives.\n- [`google_drive_delete_folder_or_file_action`](actions/google_drive_delete_folder_or_file_action.md) — Permanently delete a Drive file or folder by ID.\n- [`hide_drive`](actions/hide_drive.md) — Hide a shared drive from the default Drive view.\n- [`list_access_proposals`](actions/list_access_proposals.md) — List pending access proposals for a specific Drive file.\n- [`list_approvals`](actions/list_approvals.md) — List approvals associated with a specific Drive file.\n- [`list_changes`](actions/list_changes.md) — List file and drive changes for incremental sync workflows.\n- [`list_comments`](actions/list_comments.md) — List comments on a Drive file with pagination.\n- [`list_file_labels`](actions/list_file_labels.md) — List the Drive labels currently applied to a file.\n- [`list_permissions`](actions/list_permissions.md) — List permissions on a Drive file or shared drive.\n- [`list_replies`](actions/list_replies.md) — List replies under a Drive file comment with pagination.\n- [`list_revisions`](actions/list_revisions.md) — List revision metadata for a Drive file.\n- [`list_shared_drives`](actions/list_shared_drives.md) — List shared drives accessible to the connected account.\n- [`list_team_drives`](actions/list_team_drives.md) — Legacy compatibility alias of `list_shared_drives` for Team Drives.\n- [`modify_file_labels`](actions/modify_file_labels.md) — Add, update, or remove Drive labels on a file.\n- [`move_file`](actions/move_file.md) — Move or rename a Drive file by updating parents and/or name.\n- [`parse_file`](actions/parse_file.md) — Compatibility alias of `download_file`, including export behavior when `mimeType` is provided.\n- [`patch_permission`](actions/patch_permission.md) — Patch specific fields on an existing Drive permission.\n- [`trash_file`](actions/trash_file.md) — Move a Drive file or folder to trash without permanently deleting it.\n- [`unhide_drive`](actions/unhide_drive.md) — Unhide a shared drive and restore it to the default Drive view.\n- [`untrash_file`](actions/untrash_file.md) — Restore a Drive file or folder from trash.\n- [`update_comment`](actions/update_comment.md) — Update the content of an existing Drive file comment.\n- [`update_drive`](actions/update_drive.md) — Update metadata or restrictions on a shared drive.\n- [`update_file`](actions/update_file.md) — Patch a Drive file with metadata and optional uploaded content.\n- [`update_file_metadata_patch`](actions/update_file_metadata_patch.md) — Update Drive file metadata fields with patch semantics.\n- [`update_file_revision_metadata`](actions/update_file_revision_metadata.md) — Update revision metadata flags such as publish or keep-forever on a specific Drive file revision.\n- [`update_permission`](actions/update_permission.md) — Compatibility alias of `update_permission_patch`; Google Drive v3 uses PATCH semantics.\n- [`update_permission_patch`](actions/update_permission_patch.md) — Patch an existing Drive permission using structured permission fields.\n- [`update_reply`](actions/update_reply.md) — Update the content of an existing reply on a Drive file comment.\n- [`update_team_drive`](actions/update_team_drive.md) — Legacy compatibility alias of `update_drive` for Team Drives.\n- [`upload_file`](actions/upload_file.md) — Upload a new Drive file with binary or text content and optional metadata.\n- [`upload_update_file`](actions/upload_update_file.md) — Replace the content of an existing Drive file and optionally update metadata.\n\n## Safety\n\n- Read actions (get / list / search) are safe to run directly.\n- **Create, update, send, or post actions change Google Drive state — confirm the exact payload and effect with the user before running.**\n- **Delete or remove actions are destructive — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Google Drive is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=googledrive\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Google Drive homepage: https://workspace.google.com/products/drive/\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn7frdsfy65xpg3b4vyrdjq6pd87yahh\",\n \"slug\": \"oo-googledrive\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1780636388610\n}\n\nFile v1.0.1:actions/copy_file_advanced.md\n\n# Google Drive · `copy_file_advanced`\n\nCopy a Drive file and optionally override metadata such as name, parents, description, or properties.\n\n- **Service**: `googledrive`\n- **Action**: `copy_file_advanced`\n- **Action id**: `googledrive.copy_file_advanced`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"copy_file_advanced\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"copy_file_advanced\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.1:actions/copy_file.md\n\n# Google Drive · `copy_file`\n\nLegacy compatibility alias of `copy_file_advanced` with a simplified input shape.\n\n- **Service**: `googledrive`\n- **Action**: `copy_file`\n- **Action id**: `googledrive.copy_file`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"copy_file\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"copy_file\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.1:actions/create_comment.md\n\n# Google Drive · `create_comment`\n\nCreate a comment on a Drive file, optionally with anchor or quoted file content.\n\n- **Service**: `googledrive`\n- **Action**: `create_comment`\n- **Action id**: `googledrive.create_comment`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_comment\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_comment\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.1:actions/create_drive.md\n\n# Google Drive · `create_drive`\n\nCreate a new shared drive.\n\n- **Service**: `googledrive`\n- **Action**: `create_drive`\n- **Action id**: `googledrive.create_drive`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_drive\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_drive\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.1:actions/create_file_from_text.md\n\n# Google Drive · `create_file_from_text`\n\nCreate a new Drive file from text content and optional metadata.\n\n- **Service**: `googledrive`\n- **Action**: `create_file_from_text`\n- **Action id**: `googledrive.create_file_from_text`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_file_from_text\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_file_from_text\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.1:actions/create_file.md\n\n# Google Drive · `create_file`\n\nCreate a Google Drive file with metadata only. Use a Google Workspace mime type to create an empty native file shell.\n\n- **Service**: `googledrive`\n- **Action**: `create_file`\n- **Action id**: `googledrive.create_file`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_file\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_file\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.1:actions/create_folder.md\n\n# Google Drive · `create_folder`\n\nCreate a Google Drive folder, optionally under one or more parent folders.\n\n- **Service**: `googledrive`\n- **Action**: `create_folder`\n- **Action id**: `googledrive.create_folder`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_folder\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_folder\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.1:actions/create_permission.md\n\n# Google Drive · `create_permission`\n\nCreate a permission on a Drive file or shared drive to share it with users, groups, domains, or anyone.\n\n- **Service**: `googledrive`\n- **Action**: `create_permission`\n- **Action id**: `googledrive.create_permission`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_permission\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_permission\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.1:actions/create_reply.md\n\n# Google Drive · `create_reply`\n\nCreate a reply under an existing Drive file comment, or use an action payload such as resolve or reopen.\n\n- **Service**: `googledrive`\n- **Action**: `create_reply`\n- **Action id**: `googledrive.create_reply`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_reply\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_reply\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.1:actions/create_team_drive.md\n\n# Google Drive · `create_team_drive`\n\nLegacy compatibility alias of `create_drive` for Team Drives.\n\n- **Service**: `googledrive`\n- **Action**: `create_team_drive`\n- **Action id**: `googledrive.create_team_drive`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_team_drive\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_team_drive\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nArchive v1.0.0: 69 files, 42710 bytes\n\nFiles: actions/copy_file_advanced.md (885b), actions/copy_file.md (820b), actions/create_comment.md (844b), actions/create_drive.md (780b), actions/create_file_from_text.md (863b), actions/create_file.md (866b), actions/create_folder.md (833b), actions/create_permission.md (882b), actions/create_reply.md (858b), actions/create_team_drive.md (840b), actions/delete_comment.md (834b), actions/delete_drive.md (804b), actions/delete_file.md (836b), actions/delete_permission.md (849b), actions/delete_reply.md (839b), actions/delete_revision.md (842b), actions/delete_team_drive.md (856b), actions/download_file_operation.md (717b), actions/download_file.md (769b), actions/download_file2.md (672b), actions/edit_file.md (820b), actions/empty_trash.md (826b), actions/export_google_workspace_file.md (811b), actions/find_file.md (705b), actions/find_folder.md (711b), actions/generate_ids.md (694b), actions/get_about.md (694b), actions/get_app.md (653b), actions/get_changes_start_page_token.md (758b), actions/get_comment.md (801b), actions/get_drive.md (639b), actions/get_file_metadata.md (742b), actions/get_permission_id_for_email.md (751b), actions/get_permission.md (708b), actions/get_reply.md (786b), actions/get_revision.md (671b), actions/get_team_drive.md (691b), actions/google_drive_delete_folder_or_file_action.md (963b), actions/hide_drive.md (662b), actions/list_access_proposals.md (725b), actions/list_approvals.md (687b), actions/list_changes.md (682b), actions/list_comments.md (674b), actions/list_file_labels.md (693b), actions/list_permissions.md (692b), actions/list_replies.md (679b), actions/list_revisions.md (673b), actions/list_shared_drives.md (708b), actions/list_team_drives.md (710b), actions/modify_file_labels.md (830b), actions/move_file.md (799b), actions/parse_file.md (707b), actions/patch_permission.md (828b), actions/trash_file.md (829b), actions/unhide_drive.md (687b), actions/untrash_file.md (666b), actions/update_comment.md (817b), actions/update_drive.md (804b), actions/update_file_metadata_patch.md (879b), actions/update_file_put.md (833b), actions/update_file_revision_metadata.md (936b), actions/update_permission.md (850b), actions/update_reply.md (818b), actions/update_team_drive.md (840b), actions/upload_file.md (823b), actions/upload_update_file.md (861b), skill-card.md (2483b), SKILL.md (11305b), _meta.json (133b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: oo-googledrive\ndescription: \"Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Google Drive\"\n author: \"OOMOL\"\n version: \"1.0.0\"\n service: \"googledrive\"\n categories: \"Storage, Productivity\"\n homepage: \"https://workspace.google.com/products/drive/\"\n icon: \"https://static.oomol.com/logo/third-party/Google%20Drive.svg\"\n---\n\n# Google Drive\n\nOperate **Google Drive** through your OOMOL-connected account. This skill calls the `googledrive` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\nCategory: Storage, Productivity. Exposes 66 action(s).\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Google Drive. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"googledrive\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"googledrive\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with `oo connector schema` before constructing `--data`.\n\n## Available actions\n\n- [`copy_file`](actions/copy_file.md) — Legacy compatibility alias of `copy_file_advanced` with a simplified input shape.\n- [`copy_file_advanced`](actions/copy_file_advanced.md) — Copy a Drive file and optionally override metadata such as name, parents, description, or properties.\n- [`create_comment`](actions/create_comment.md) — Create a comment on a Drive file, optionally with anchor or quoted file content.\n- [`create_drive`](actions/create_drive.md) — Create a new shared drive.\n- [`create_file`](actions/create_file.md) — Create a Google Drive file with metadata only. Use a Google Workspace mime type to create an empty native file shell.\n- [`create_file_from_text`](actions/create_file_from_text.md) — Create a new Drive file from text content and optional metadata.\n- [`create_folder`](actions/create_folder.md) — Create a Google Drive folder, optionally under one or more parent folders.\n- [`create_permission`](actions/create_permission.md) — Create a permission on a Drive file or shared drive to share it with users, groups, domains, or anyone.\n- [`create_reply`](actions/create_reply.md) — Create a reply under an existing Drive file comment, or use an action payload such as resolve or reopen.\n- [`create_team_drive`](actions/create_team_drive.md) — Legacy compatibility alias of `create_drive` for Team Drives.\n- [`delete_comment`](actions/delete_comment.md) — Permanently delete a comment thread from a Drive file.\n- [`delete_drive`](actions/delete_drive.md) — Permanently delete a shared drive.\n- [`delete_file`](actions/delete_file.md) — Legacy compatibility alias for permanently deleting a Drive file by ID.\n- [`delete_permission`](actions/delete_permission.md) — Delete a permission from a Drive file or shared drive.\n- [`delete_reply`](actions/delete_reply.md) — Permanently delete a specific reply from a Drive file comment thread.\n- [`delete_revision`](actions/delete_revision.md) — Permanently delete a specific revision from a Drive file.\n- [`delete_team_drive`](actions/delete_team_drive.md) — Legacy compatibility alias of `delete_drive` for Team Drives.\n- [`download_file`](actions/download_file.md) — Download a Drive file by ID, or export a Google Workspace file when `mimeType` is provided. Returns a transit URL for the downloaded content.\n- [`download_file_operation`](actions/download_file_operation.md) — Compatibility alias of `download_file`.\n- [`download_file2`](actions/download_file2.md) — Compatibility alias of `download_file`.\n- [`edit_file`](actions/edit_file.md) — Overwrite an existing Drive file with text content and optional metadata changes.\n- [`empty_trash`](actions/empty_trash.md) — Permanently empty the user's trash or a shared drive's trash.\n- [`export_google_workspace_file`](actions/export_google_workspace_file.md) — Export a Google Workspace file to the requested MIME type and return a transit URL for the exported content.\n- [`find_file`](actions/find_file.md) — Search Google Drive files and folders with query, date, starred, trash, and shared-drive filters.\n- [`find_folder`](actions/find_folder.md) — Search Google Drive folders only, with the same query and pagination controls as `find_file`.\n- [`generate_ids`](actions/generate_ids.md) — Generate one or more Drive file IDs for later create or copy requests.\n- [`get_about`](actions/get_about.md) — Get Drive account information such as user details, quota, and supported capabilities.\n- [`get_app`](actions/get_app.md) — Get metadata for a specific Google Drive app by app ID.\n- [`get_changes_start_page_token`](actions/get_changes_start_page_token.md) — Get the page token for monitoring future Drive changes.\n- [`get_comment`](actions/get_comment.md) — Get a specific comment on a Drive file by comment ID.\n- [`get_drive`](actions/get_drive.md) — Get a shared drive by drive ID.\n- [`get_file_metadata`](actions/get_file_metadata.md) — Get metadata for a Drive file by ID, including mime type, parents, ownership, and trash state.\n- [`get_permission`](actions/get_permission.md) — Get a specific permission on a Drive file or shared drive by permission ID.\n- [`get_permission_id_for_email`](actions/get_permission_id_for_email.md) — Look up the Drive permission ID for an email address.\n- [`get_reply`](actions/get_reply.md) — Get a specific reply under a Drive file comment.\n- [`get_revision`](actions/get_revision.md) — Get metadata for a specific Drive file revision.\n- [`get_team_drive`](actions/get_team_drive.md) — Legacy compatibility alias of `get_drive` for Team Drives.\n- [`google_drive_delete_folder_or_file_action`](actions/google_drive_delete_folder_or_file_action.md) — Permanently delete a Drive file or folder by ID.\n- [`hide_drive`](actions/hide_drive.md) — Hide a shared drive from the default Drive view.\n- [`list_access_proposals`](actions/list_access_proposals.md) — List pending access proposals for a specific Drive file.\n- [`list_approvals`](actions/list_approvals.md) — List approvals associated with a specific Drive file.\n- [`list_changes`](actions/list_changes.md) — List file and drive changes for incremental sync workflows.\n- [`list_comments`](actions/list_comments.md) — List comments on a Drive file with pagination.\n- [`list_file_labels`](actions/list_file_labels.md) — List the Drive labels currently applied to a file.\n- [`list_permissions`](actions/list_permissions.md) — List permissions on a Drive file or shared drive.\n- [`list_replies`](actions/list_replies.md) — List replies under a Drive file comment with pagination.\n- [`list_revisions`](actions/list_revisions.md) — List revision metadata for a Drive file.\n- [`list_shared_drives`](actions/list_shared_drives.md) — List shared drives accessible to the connected account.\n- [`list_team_drives`](actions/list_team_drives.md) — Legacy compatibility alias of `list_shared_drives` for Team Drives.\n- [`modify_file_labels`](actions/modify_file_labels.md) — Add, update, or remove Drive labels on a file.\n- [`move_file`](actions/move_file.md) — Move or rename a Drive file by updating parents and/or name.\n- [`parse_file`](actions/parse_file.md) — Compatibility alias of `download_file`, including export behavior when `mimeType` is provided.\n- [`patch_permission`](actions/patch_permission.md) — Patch specific fields on an existing Drive permission.\n- [`trash_file`](actions/trash_file.md) — Move a Drive file or folder to trash without permanently deleting it.\n- [`unhide_drive`](actions/unhide_drive.md) — Unhide a shared drive and restore it to the default Drive view.\n- [`untrash_file`](actions/untrash_file.md) — Restore a Drive file or folder from trash.\n- [`update_comment`](actions/update_comment.md) — Update the content of an existing Drive file comment.\n- [`update_drive`](actions/update_drive.md) — Update metadata or restrictions on a shared drive.\n- [`update_file_metadata_patch`](actions/update_file_metadata_patch.md) — Update Drive file metadata fields with patch semantics.\n- [`update_file_put`](actions/update_file_put.md) — Update a Drive file with metadata and optional uploaded content.\n- [`update_file_revision_metadata`](actions/update_file_revision_metadata.md) — Update revision metadata flags such as publish or keep-forever on a specific Drive file revision.\n- [`update_permission`](actions/update_permission.md) — Update an existing Drive permission using structured permission fields.\n- [`update_reply`](actions/update_reply.md) — Update the content of an existing reply on a Drive file comment.\n- [`update_team_drive`](actions/update_team_drive.md) — Legacy compatibility alias of `update_drive` for Team Drives.\n- [`upload_file`](actions/upload_file.md) — Upload a new Drive file with binary or text content and optional metadata.\n- [`upload_update_file`](actions/upload_update_file.md) — Replace the content of an existing Drive file and optionally update metadata.\n\n## Safety\n\n- Read actions (get / list / search) are safe to run directly.\n- **Create, update, send, or post actions change Google Drive state — confirm the exact payload and effect with the user before running.**\n- **Delete or remove actions are destructive — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Google Drive is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=googledrive\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Google Drive homepage: https://workspace.google.com/products/drive/\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn7frdsfy65xpg3b4vyrdjq6pd87yahh\",\n \"slug\": \"oo-googledrive\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1780497133644\n}\n\nFile v1.0.0:actions/copy_file_advanced.md\n\n# Google Drive · `copy_file_advanced`\n\nCopy a Drive file and optionally override metadata such as name, parents, description, or properties.\n\n- **Service**: `googledrive`\n- **Action**: `copy_file_advanced`\n- **Action id**: `googledrive.copy_file_advanced`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"copy_file_advanced\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"copy_file_advanced\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/copy_file.md\n\n# Google Drive · `copy_file`\n\nLegacy compatibility alias of `copy_file_advanced` with a simplified input shape.\n\n- **Service**: `googledrive`\n- **Action**: `copy_file`\n- **Action id**: `googledrive.copy_file`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"copy_file\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"copy_file\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/create_comment.md\n\n# Google Drive · `create_comment`\n\nCreate a comment on a Drive file, optionally with anchor or quoted file content.\n\n- **Service**: `googledrive`\n- **Action**: `create_comment`\n- **Action id**: `googledrive.create_comment`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_comment\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_comment\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/create_drive.md\n\n# Google Drive · `create_drive`\n\nCreate a new shared drive.\n\n- **Service**: `googledrive`\n- **Action**: `create_drive`\n- **Action id**: `googledrive.create_drive`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_drive\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_drive\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/create_file_from_text.md\n\n# Google Drive · `create_file_from_text`\n\nCreate a new Drive file from text content and optional metadata.\n\n- **Service**: `googledrive`\n- **Action**: `create_file_from_text`\n- **Action id**: `googledrive.create_file_from_text`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_file_from_text\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_file_from_text\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/create_file.md\n\n# Google Drive · `create_file`\n\nCreate a Google Drive file with metadata only. Use a Google Workspace mime type to create an empty native file shell.\n\n- **Service**: `googledrive`\n- **Action**: `create_file`\n- **Action id**: `googledrive.create_file`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_file\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_file\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/create_folder.md\n\n# Google Drive · `create_folder`\n\nCreate a Google Drive folder, optionally under one or more parent folders.\n\n- **Service**: `googledrive`\n- **Action**: `create_folder`\n- **Action id**: `googledrive.create_folder`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_folder\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_folder\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/create_permission.md\n\n# Google Drive · `create_permission`\n\nCreate a permission on a Drive file or shared drive to share it with users, groups, domains, or anyone.\n\n- **Service**: `googledrive`\n- **Action**: `create_permission`\n- **Action id**: `googledrive.create_permission`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_permission\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_permission\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/create_reply.md\n\n# Google Drive · `create_reply`\n\nCreate a reply under an existing Drive file comment, or use an action payload such as resolve or reopen.\n\n- **Service**: `googledrive`\n- **Action**: `create_reply`\n- **Action id**: `googledrive.create_reply`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_reply\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_reply\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/create_team_drive.md\n\n# Google Drive · `create_team_drive`\n\nLegacy compatibility alias of `create_drive` for Team Drives.\n\n- **Service**: `googledrive`\n- **Action**: `create_team_drive`\n- **Action id**: `googledrive.create_team_drive`\n- **Required scopes**: googledrive.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"googledrive\" --action \"create_team_drive\"\n```\n\n## Run\n\n```bash\noo connector run \"googledrive\" --action \"create_team_drive\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Google Drive state. Confirm the exact payload and intended effect with the user before running.","readmeExcerpt":"Skill: Google Drive Owner: oomol Summary: Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly. Tags: latest:1.0.7 Version history: v1.0.7 | 2026-09-20T03:19:14.808Z | user - Adds Google Drive support through the OOMOL-connected googledrive connector a","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"oo connector schema \"googledrive\" --action \"\""},{"language":"bash","snippet":"oo connector run \"googledrive\" --action \"\" --data '' --json"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux"},{"language":"powershell","snippet":"irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell"},{"language":"bash","snippet":"oo auth login"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: oo-googledrive\ndescription: \"Google Drive (workspace.google.com). Use this skill for ANY Google Drive request — reading, creating, updating, and deleting data. Whenever a task involves Google Drive, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Google Drive\"\n author: \"OOMOL\"\n version: \"1.0.7\"\n services: [\"googledrive\"]\n icon: \"https://static.oomol.com/logo/third-party/Google%20Drive.svg\"\n---\n\n# Google Drive\n\nOperate **Google Drive** through your OOMOL-connected account. This skill calls the `googledrive` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Google Drive. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"googledrive\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"googledrive\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `about.get` — Get Drive account information such as user details, quota, and supported capabilities.\n- `accessproposals.list` — List pending access proposals for a specific Drive file.\n- `approvals.list` — List approvals associated with a specific Drive file.\n- `apps.get` — Get metadata for a specific Google Drive app by app ID.\n- `changes.getStartPageToken` — Get the page token for monitoring future Drive changes.\n- `changes.list` — List file and drive changes for incremental sync workflows.\n- `comments.create` — Create a comment on a Drive file, optionally with anchor or quoted file content. [write]\n- `comments.delete` — Permanently delete a comment thread from a Drive file. [destructive]\n- `comments.get` — Get a specific comment on a Drive file by comment ID.\n- `comments.list` — List comments on a Drive file with pagination.\n- `comments.update` — Update the content of an existing Drive file comment. [write]\n- `drives.create` — Create a new shared drive. [write]\n- `drives.delete` — Permanently delete a shared drive. [destructive]\n- `drives.get` — Get a shared drive by drive ID.\n- `drives.hide` — Hide a shared drive f"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7frdsfy65xpg3b4vyrdjq6pd87yahh\",\n \"slug\": \"oo-googledrive\",\n \"version\": \"1.0.7\",\n \"publishedAt\": 1789874354808\n}"},{"path":"skill-card.md","content":"## Description:\n\nProvides agent guidance for reading, creating, updating, sharing, exporting, and deleting Google Drive content through an OOMOL-connected Google Drive account.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and developers use this skill to let an agent operate Google Drive files, shared drives, permissions, labels, revisions, comments, replies, changes, approvals, and access proposals through the OOMOL connector.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: First-time setup recommends running remote oo CLI installation scripts directly in a shell.\n\nMitigation: Review the oo CLI installation path before installing and prefer a verified package or documented manual installation method.\n\nRisk: The skill can guide write or destructive Google Drive actions that modify, delete, overwrite, or expose Drive content.\n\nMitigation: Confirm the exact target, payload, and expected effect with the user before any write or destructive action.\n\n## Reference(s):\n\n- [ClawHub Google Drive Skill](https://clawhub.ai/oomol/skills/oo-googledrive)\n- [Google Drive](https://workspace.google.com/products/drive/)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI Install Guide](https://cli.oomol.com/install-guide.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON payload guidance]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces connector schema inspection and action-running guidance for the oo CLI.]\n\n## Skill Version(s):\n\n1.0.7 (source: release evidence and SKILL.md frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1629,"uniquenessScore":37,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T04:14:34.174Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T04:14:34.174Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:40:50.395Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}