{"id":"9fdd3406-7475-4101-b8f3-775c7d637cf6","entityType":"agent","slug":"clawhub-hith3sh-google-docs-documents","name":"Google Docs","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-google-docs-documents","canonicalPath":"/agent/clawhub-hith3sh-google-docs-documents","generatedAt":"2026-10-09T14:33:24.444Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T03:00:06.679Z","emptyReason":null},"description":"Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text,... Skill: Google Docs Owner: hith3sh Summary: Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text,... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:09:50.722Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic s","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 7.3K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:google-docs-documents","sourceUrl":"https://clawhub.ai/hith3sh/google-docs-documents","homepage":"https://clawhub.ai/hith3sh/skills/google-docs-documents","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/google-docs-documents","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/google-docs-documents","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":77,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text,..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T03:00:06.679Z","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-09T03:00:06.679Z","emptyReason":null},"stars":null,"forks":null,"downloads":7291,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"7.3K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T03:00:06.679Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T03:00:06.679Z","lastCrawledAt":"2026-10-09T03:00:06.679Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T03:00:06.679Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-06-09T07:09:50.722Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":6358},{"version":"1.0.4","createdAt":"2026-06-09T04:55:39.399Z","changelog":"- Removed the file skill-card.md. - No changes to functionality or user-facing features. - Skill documentation and capabilities remain the same.","fileCount":3,"zipByteSize":6317},{"version":"1.0.1","createdAt":"2026-06-08T16:37:12.912Z","changelog":"- Added a branded Google Docs logo at the top of the documentation. - Minor formatting improvements for clarity and readability. - Removed the redundant skill-card.md file. - No changes to functionality or commands.","fileCount":3,"zipByteSize":6256},{"version":"0.1.1","createdAt":"2026-06-07T13:30:28.769Z","changelog":"Full rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.","fileCount":3,"zipByteSize":6229},{"version":"0.1.0","createdAt":"2026-05-03T13:33:31.442Z","changelog":"Initial release enabling Google Docs access via ClawLink integration: - Search, read, export, and create Google Docs through a chat interface - Update document content and structure with confirmation - Guided setup using ClawLink for easy connection—no manual API configuration needed - Dynamic discovery and execution of Google Docs tools based on user account and permissions - Built-in confirmation steps for actions that modify or create documents","fileCount":3,"zipByteSize":3622}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:google-docs-documents","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"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-hith3sh-google-docs-documents/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-docs-documents/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-docs-documents/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-docs-documents/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-docs-documents/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-docs-documents/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-09T14:33:24.442Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-docs-documents/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-docs-documents/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-docs-documents/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-docs-documents/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":"high","updatedAt":"2026-10-09T03:00:06.679Z","emptyReason":null},"readme":"Skill: Google Docs\n\nOwner: hith3sh\n\nSummary: Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text,...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-06-09T07:09:50.722Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv1.0.4 | 2026-06-09T04:55:39.399Z | auto\n\n- Removed the file skill-card.md.\n- No changes to functionality or user-facing features.\n- Skill documentation and capabilities remain the same.\n\nv1.0.1 | 2026-06-08T16:37:12.912Z | auto\n\n- Added a branded Google Docs logo at the top of the documentation.\n- Minor formatting improvements for clarity and readability.\n- Removed the redundant skill-card.md file.\n- No changes to functionality or commands.\n\nv0.1.1 | 2026-06-07T13:30:28.769Z | user\n\nFull rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.\n\nv0.1.0 | 2026-05-03T13:33:31.442Z | auto\n\nInitial release enabling Google Docs access via ClawLink integration:\n\n- Search, read, export, and create Google Docs through a chat interface\n- Update document content and structure with confirmation\n- Guided setup using ClawLink for easy connection—no manual API configuration needed\n- Dynamic discovery and execution of Google Docs tools based on user account and permissions\n- Built-in confirmation steps for actions that modify or create documents\n\nArchive index:\n\nArchive v1.0.5: 3 files, 6358 bytes\n\nFiles: skill-card.md (2236b), SKILL.md (16159b), _meta.json (140b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: google-docs-documents\ndescription: Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text, create drafts from prompts, insert content, or modify document structure.\n---\n\n# Google Docs\n\n\n\nAccess Google Docs via the Google Docs API with managed OAuth authentication. Search, read, create, and update documents stored in Google Drive.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-docs-documents) for hosted connection flows and credentials so you do not need to configure Google Docs API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Docs |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Docs |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Docs │\n│ (User Chat) │ │ (OAuth) │ │ (Docs API) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Docs │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Drive │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Docs again.\"\n\n## Quick Start\n\n```bash\n# Search for documents\nclawlink_call_tool --tool \"googledocs_search_documents\" --params '{\"query\": \"report\"}'\n\n# Get document plaintext\nclawlink_call_tool --tool \"googledocs_get_document_plaintext\" --params '{\"document_id\": \"YOUR_DOCUMENT_ID\"}'\n\n# Create a new document\nclawlink_call_tool --tool \"googledocs_create_document\" --params '{\"title\": \"New Document\"}'\n```\n\n## Authentication\n\nAll Google Docs tool calls are authenticated automatically by ClawLink using the user's connected Google account.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Google Docs API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=google-docs and connect Google Docs.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `google-docs` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-docs\n```\n\n**Response:** Returns the live tool catalog for Google Docs.\n\n### Reconnect\n\nIf Google Docs tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-docs\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-docs`\n\n## Security & Permissions\n\n- Access is scoped to documents within the connected Google account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete content range, delete table row/column) are marked as high-impact and must be confirmed.\n- Document sharing permissions can be inspected to understand access levels before making changes.\n\n## Tool Reference\n\n### Document Discovery & Reading\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_search_documents` | Search for Google Docs by name, content, or date range | Read |\n| `googledocs_get_document_by_id` | Retrieve a document's full metadata | Read |\n| `googledocs_get_document_plaintext` | Get a best-effort plain-text rendering of a document | Read |\n| `googledocs_export_document_as_pdf` | Export a document as PDF (10MB limit) | Read |\n| `googledocs_list_spreadsheet_charts` | List charts from a linked Google Sheets spreadsheet | Read |\n\n### Document Creation\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_create_document` | Create a new empty document with a title | Write |\n| `googledocs_create_document_markdown` | Create a document initialized with Markdown content | Write |\n\n### Content Insertion & Updates\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_insert_text_action` | Insert text at a specific index or append to end | Write |\n| `googledocs_replace_all_text` | Replace all occurrences of a string throughout a document | Write |\n| `googledocs_update_document_markdown` | Replace entire document content with Markdown | Write |\n| `googledocs_update_document_section_markdown` | Insert or replace a section of a document with Markdown | Write |\n| `googledocs_update_existing_document` | Apply programmatic edits via batchUpdate API | Write |\n| `googledocs_update_document_style` | Update page size, margins, and default text direction | Write |\n\n### Structural Elements\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_insert_table_action` | Insert a table at a specific location | Write |\n| `googledocs_insert_table_column` | Insert a new column into an existing table | Write |\n| `googledocs_insert_page_break` | Insert a page break into a document | Write |\n| `googledocs_insert_inline_image` | Insert an image from a URI at a specific location | Write |\n| `googledocs_create_paragraph_bullets` | Add bullet formatting to paragraphs in a range | Write |\n| `googledocs_delete_paragraph_bullets` | Remove bullet formatting from paragraphs | Write |\n\n### Header, Footer & Named Ranges\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_create_header` | Create a new header with optional text | Write |\n| `googledocs_create_footer` | Create a new footer with optional text | Write |\n| `googledocs_create_footnote` | Add a footnote at a location or end of document | Write |\n| `googledocs_create_named_range` | Assign a name to a specific part of a document | Write |\n| `googledocs_delete_header` | Delete a header from a document | Write |\n| `googledocs_delete_footer` | Delete a footer from a document | Write |\n\n### Table Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_delete_table_row` | Delete a row from a table | Write |\n| `googledocs_delete_table_column` | Delete a column from a table | Write |\n| `googledocs_unmerge_table_cells` | Unmerge previously merged cells in a table | Write |\n| `googledocs_update_table_row_style` | Update row style (height, header marking) | Write |\n\n### Copying & Duplication\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_copy_document` | Create a copy of an existing document | Write |\n\n### Deletion\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_delete_content_range` | Delete a range of content from a document | Write |\n| `googledocs_delete_named_range` | Delete a named range from a document | Write |\n\n### Image Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_replace_image` | Replace an existing image with a new one from a URI | Write |\n\n## Code Examples\n\n### Search for documents\n\n```bash\nclawlink_call_tool --tool \"googledocs_search_documents\" \\\n --params '{\n \"query\": \"meeting notes\",\n \"page_size\": 10\n }'\n```\n\n### Read document plaintext\n\n```bash\nclawlink_call_tool --tool \"googledocs_get_document_plaintext\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\"\n }'\n```\n\n### Create a document from Markdown\n\n```bash\nclawlink_call_tool --tool \"googledocs_create_document_markdown\" \\\n --params '{\n \"title\": \"Project Brief\",\n \"markdown\": \"# Project Brief\\n\\n## Overview\\n\\nThis is the project overview section.\\n\\n## Next Steps\\n\\n1. Define requirements\\n2. Create mockups\\n3. Implement feature\"\n }'\n```\n\n### Insert text at a location\n\n```bash\nclawlink_call_tool --tool \"googledocs_insert_text_action\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\",\n \"text\": \"New paragraph content here.\",\n \"insertion_index\": 150\n }'\n```\n\n### Replace all text occurrences\n\n```bash\nclawlink_call_tool --tool \"googledocs_replace_all_text\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\",\n \"replace_text\": \"New Company Name\",\n \"search_text\": \"Old Company Name\"\n }'\n```\n\n### Copy a document\n\n```bash\nclawlink_call_tool --tool \"googledocs_copy_document\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Docs is connected.\n2. Call `clawlink_list_tools --integration google-docs` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-docs`.\n5. If no Google Docs tools appear, direct the user to https://claw-link.dev/dashboard?add=google-docs.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ search → get → export → call │\n│ │\n│ Example: Search docs → Get plaintext → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer search, read, export, and inspection operations before writes.\n4. For document creation, content replacement, Markdown imports, structural edits, or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Document IDs are stable Google Drive file IDs — capture them from search or get responses for subsequent operations.\n- `googledocs_insert_text_action`: Use `append_to_end=true` to safely append without index concerns. When using `insertion_index`, it must fall within an existing paragraph's bounds.\n- Table operations require knowing the table index within the document structure.\n- Every document segment (body, header, footer, footnote) ends with a final newline that cannot be deleted.\n- PDF export has a 10MB content limit enforced by Google Drive API.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration google-docs`. |\n| Missing connection | Google Docs is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-docs. |\n| `RESOURCE_NOT_FOUND` | Document does not exist. Check the document_id. |\n| `INVALID_ARGUMENT` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| `FORBIDDEN` | No read or write access to the document. Check sharing permissions. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `google-docs`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Google Docs API Overview](https://developers.google.com/docs/api)\n- [Documents Resource](https://developers.google.com/docs/api/reference/rest/v1/documents)\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-docs-documents\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Google Drive](https://clawhub.ai/hith3sh/google-drive-files) — For file management, permissions, and Drive-level operations\n- [Google Sheets](https://clawhub.ai/hith3sh/google-sheets-spreadsheets) — For spreadsheet operations in Google Workspace\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-docs-documents)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"google-docs-documents\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780988990722\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nGoogle Docs API integration with managed OAuth for searching, reading, creating, and updating Google Docs documents.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\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 find, read, create, and update Google Docs documents through a connected Google account.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill relies on ClawLink as an external OAuth bridge for Google Docs access.\n\nMitigation: Install only after reviewing ClawLink verification or source information where available, and use the least-privileged Google account suitable for the task.\n\nRisk: Connected tools can modify Google Docs content.\n\nMitigation: Preview and explicitly confirm create, update, delete, and other write operations before execution.\n\nRisk: OAuth access may remain available after the immediate task is complete.\n\nMitigation: Revoke the Google authorization or remove the plugin allowlist entry when the integration is no longer needed.\n\n## Reference(s):\n\n- [Google Docs API Overview](https://developers.google.com/docs/api)\n- [Google Docs Documents Resource](https://developers.google.com/docs/api/reference/rest/v1/documents)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/google-docs-documents)\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 tool-call examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include Google Docs document identifiers, previews, document text, and confirmation prompts before write operations.]\n\n## Skill Version(s):\n\n1.0.5 (source: 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, 6317 bytes\n\nFiles: skill-card.md (2330b), SKILL.md (15937b), _meta.json (140b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: google-docs-documents\ndescription: Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text, create drafts from prompts, insert content, or modify document structure.\n---\n\n# Google Docs\n\n\n\nAccess Google Docs via the Google Docs API with managed OAuth authentication. Search, read, create, and update documents stored in Google Drive.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Docs API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Docs |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Docs |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Docs │\n│ (User Chat) │ │ (OAuth) │ │ (Docs API) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Docs │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Drive │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Docs again.\"\n\n## Quick Start\n\n```bash\n# Search for documents\nclawlink_call_tool --tool \"googledocs_search_documents\" --params '{\"query\": \"report\"}'\n\n# Get document plaintext\nclawlink_call_tool --tool \"googledocs_get_document_plaintext\" --params '{\"document_id\": \"YOUR_DOCUMENT_ID\"}'\n\n# Create a new document\nclawlink_call_tool --tool \"googledocs_create_document\" --params '{\"title\": \"New Document\"}'\n```\n\n## Authentication\n\nAll Google Docs tool calls are authenticated automatically by ClawLink using the user's connected Google account.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Google Docs API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=google-docs and connect Google Docs.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `google-docs` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-docs\n```\n\n**Response:** Returns the live tool catalog for Google Docs.\n\n### Reconnect\n\nIf Google Docs tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-docs\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-docs`\n\n## Security & Permissions\n\n- Access is scoped to documents within the connected Google account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete content range, delete table row/column) are marked as high-impact and must be confirmed.\n- Document sharing permissions can be inspected to understand access levels before making changes.\n\n## Tool Reference\n\n### Document Discovery & Reading\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_search_documents` | Search for Google Docs by name, content, or date range | Read |\n| `googledocs_get_document_by_id` | Retrieve a document's full metadata | Read |\n| `googledocs_get_document_plaintext` | Get a best-effort plain-text rendering of a document | Read |\n| `googledocs_export_document_as_pdf` | Export a document as PDF (10MB limit) | Read |\n| `googledocs_list_spreadsheet_charts` | List charts from a linked Google Sheets spreadsheet | Read |\n\n### Document Creation\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_create_document` | Create a new empty document with a title | Write |\n| `googledocs_create_document_markdown` | Create a document initialized with Markdown content | Write |\n\n### Content Insertion & Updates\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_insert_text_action` | Insert text at a specific index or append to end | Write |\n| `googledocs_replace_all_text` | Replace all occurrences of a string throughout a document | Write |\n| `googledocs_update_document_markdown` | Replace entire document content with Markdown | Write |\n| `googledocs_update_document_section_markdown` | Insert or replace a section of a document with Markdown | Write |\n| `googledocs_update_existing_document` | Apply programmatic edits via batchUpdate API | Write |\n| `googledocs_update_document_style` | Update page size, margins, and default text direction | Write |\n\n### Structural Elements\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_insert_table_action` | Insert a table at a specific location | Write |\n| `googledocs_insert_table_column` | Insert a new column into an existing table | Write |\n| `googledocs_insert_page_break` | Insert a page break into a document | Write |\n| `googledocs_insert_inline_image` | Insert an image from a URI at a specific location | Write |\n| `googledocs_create_paragraph_bullets` | Add bullet formatting to paragraphs in a range | Write |\n| `googledocs_delete_paragraph_bullets` | Remove bullet formatting from paragraphs | Write |\n\n### Header, Footer & Named Ranges\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_create_header` | Create a new header with optional text | Write |\n| `googledocs_create_footer` | Create a new footer with optional text | Write |\n| `googledocs_create_footnote` | Add a footnote at a location or end of document | Write |\n| `googledocs_create_named_range` | Assign a name to a specific part of a document | Write |\n| `googledocs_delete_header` | Delete a header from a document | Write |\n| `googledocs_delete_footer` | Delete a footer from a document | Write |\n\n### Table Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_delete_table_row` | Delete a row from a table | Write |\n| `googledocs_delete_table_column` | Delete a column from a table | Write |\n| `googledocs_unmerge_table_cells` | Unmerge previously merged cells in a table | Write |\n| `googledocs_update_table_row_style` | Update row style (height, header marking) | Write |\n\n### Copying & Duplication\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_copy_document` | Create a copy of an existing document | Write |\n\n### Deletion\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_delete_content_range` | Delete a range of content from a document | Write |\n| `googledocs_delete_named_range` | Delete a named range from a document | Write |\n\n### Image Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_replace_image` | Replace an existing image with a new one from a URI | Write |\n\n## Code Examples\n\n### Search for documents\n\n```bash\nclawlink_call_tool --tool \"googledocs_search_documents\" \\\n --params '{\n \"query\": \"meeting notes\",\n \"page_size\": 10\n }'\n```\n\n### Read document plaintext\n\n```bash\nclawlink_call_tool --tool \"googledocs_get_document_plaintext\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\"\n }'\n```\n\n### Create a document from Markdown\n\n```bash\nclawlink_call_tool --tool \"googledocs_create_document_markdown\" \\\n --params '{\n \"title\": \"Project Brief\",\n \"markdown\": \"# Project Brief\\n\\n## Overview\\n\\nThis is the project overview section.\\n\\n## Next Steps\\n\\n1. Define requirements\\n2. Create mockups\\n3. Implement feature\"\n }'\n```\n\n### Insert text at a location\n\n```bash\nclawlink_call_tool --tool \"googledocs_insert_text_action\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\",\n \"text\": \"New paragraph content here.\",\n \"insertion_index\": 150\n }'\n```\n\n### Replace all text occurrences\n\n```bash\nclawlink_call_tool --tool \"googledocs_replace_all_text\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\",\n \"replace_text\": \"New Company Name\",\n \"search_text\": \"Old Company Name\"\n }'\n```\n\n### Copy a document\n\n```bash\nclawlink_call_tool --tool \"googledocs_copy_document\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Docs is connected.\n2. Call `clawlink_list_tools --integration google-docs` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-docs`.\n5. If no Google Docs tools appear, direct the user to https://claw-link.dev/dashboard?add=google-docs.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ search → get → export → call │\n│ │\n│ Example: Search docs → Get plaintext → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer search, read, export, and inspection operations before writes.\n4. For document creation, content replacement, Markdown imports, structural edits, or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Document IDs are stable Google Drive file IDs — capture them from search or get responses for subsequent operations.\n- `googledocs_insert_text_action`: Use `append_to_end=true` to safely append without index concerns. When using `insertion_index`, it must fall within an existing paragraph's bounds.\n- Table operations require knowing the table index within the document structure.\n- Every document segment (body, header, footer, footnote) ends with a final newline that cannot be deleted.\n- PDF export has a 10MB content limit enforced by Google Drive API.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration google-docs`. |\n| Missing connection | Google Docs is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-docs. |\n| `RESOURCE_NOT_FOUND` | Document does not exist. Check the document_id. |\n| `INVALID_ARGUMENT` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| `FORBIDDEN` | No read or write access to the document. Check sharing permissions. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `google-docs`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Google Docs API Overview](https://developers.google.com/docs/api)\n- [Documents Resource](https://developers.google.com/docs/api/reference/rest/v1/documents)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Google Drive](https://clawhub.ai/hith3sh/google-drive-files) — For file management, permissions, and Drive-level operations\n- [Google Sheets](https://clawhub.ai/hith3sh/google-sheets-spreadsheets) — For spreadsheet operations in Google Workspace\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"google-docs-documents\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1780980939399\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nGoogle Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nOpenClaw users use this skill to search, read, create, and update Google Docs documents through a connected Google account. It is suited for document drafting, plain-text extraction, content insertion, structural edits, and document management workflows.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can read and edit documents in the user's connected Google Docs account through OAuth.
\nMitigation: Install only when the user trusts ClawLink with Google Docs access, review the Google consent scopes, and disconnect the integration when it is no longer needed.
\nRisk: Write operations may create, replace, delete, or restructure document content.
\nMitigation: Use preview and explicit user confirmation before document changes, especially destructive actions such as content range, table row, or table column deletion.
\n\n\n## Reference(s):
\n- [Google Docs API Overview](https://developers.google.com/docs/api)
\n- [Google Docs Documents Resource](https://developers.google.com/docs/api/reference/rest/v1/documents)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/google-docs-documents)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, configuration, text, markdown]
\n**Output Format:** [Markdown with inline shell commands and JSON tool-call examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires a connected ClawLink Google Docs OAuth account for live Google Docs actions.]
\n\n## Skill Version(s):
\n1.0.4 (source: 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.1: 3 files, 6256 bytes\n\nFiles: skill-card.md (2236b), SKILL.md (15937b), _meta.json (140b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: google-docs-documents\ndescription: Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text, create drafts from prompts, insert content, or modify document structure.\n---\n\n# Google Docs\n\n\n\nAccess Google Docs via the Google Docs API with managed OAuth authentication. Search, read, create, and update documents stored in Google Drive.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Docs API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Docs |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Docs |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Docs │\n│ (User Chat) │ │ (OAuth) │ │ (Docs API) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Docs │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Drive │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Docs again.\"\n\n## Quick Start\n\n```bash\n# Search for documents\nclawlink_call_tool --tool \"googledocs_search_documents\" --params '{\"query\": \"report\"}'\n\n# Get document plaintext\nclawlink_call_tool --tool \"googledocs_get_document_plaintext\" --params '{\"document_id\": \"YOUR_DOCUMENT_ID\"}'\n\n# Create a new document\nclawlink_call_tool --tool \"googledocs_create_document\" --params '{\"title\": \"New Document\"}'\n```\n\n## Authentication\n\nAll Google Docs tool calls are authenticated automatically by ClawLink using the user's connected Google account.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Google Docs API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=google-docs and connect Google Docs.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `google-docs` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-docs\n```\n\n**Response:** Returns the live tool catalog for Google Docs.\n\n### Reconnect\n\nIf Google Docs tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-docs\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-docs`\n\n## Security & Permissions\n\n- Access is scoped to documents within the connected Google account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete content range, delete table row/column) are marked as high-impact and must be confirmed.\n- Document sharing permissions can be inspected to understand access levels before making changes.\n\n## Tool Reference\n\n### Document Discovery & Reading\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_search_documents` | Search for Google Docs by name, content, or date range | Read |\n| `googledocs_get_document_by_id` | Retrieve a document's full metadata | Read |\n| `googledocs_get_document_plaintext` | Get a best-effort plain-text rendering of a document | Read |\n| `googledocs_export_document_as_pdf` | Export a document as PDF (10MB limit) | Read |\n| `googledocs_list_spreadsheet_charts` | List charts from a linked Google Sheets spreadsheet | Read |\n\n### Document Creation\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_create_document` | Create a new empty document with a title | Write |\n| `googledocs_create_document_markdown` | Create a document initialized with Markdown content | Write |\n\n### Content Insertion & Updates\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_insert_text_action` | Insert text at a specific index or append to end | Write |\n| `googledocs_replace_all_text` | Replace all occurrences of a string throughout a document | Write |\n| `googledocs_update_document_markdown` | Replace entire document content with Markdown | Write |\n| `googledocs_update_document_section_markdown` | Insert or replace a section of a document with Markdown | Write |\n| `googledocs_update_existing_document` | Apply programmatic edits via batchUpdate API | Write |\n| `googledocs_update_document_style` | Update page size, margins, and default text direction | Write |\n\n### Structural Elements\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_insert_table_action` | Insert a table at a specific location | Write |\n| `googledocs_insert_table_column` | Insert a new column into an existing table | Write |\n| `googledocs_insert_page_break` | Insert a page break into a document | Write |\n| `googledocs_insert_inline_image` | Insert an image from a URI at a specific location | Write |\n| `googledocs_create_paragraph_bullets` | Add bullet formatting to paragraphs in a range | Write |\n| `googledocs_delete_paragraph_bullets` | Remove bullet formatting from paragraphs | Write |\n\n### Header, Footer & Named Ranges\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_create_header` | Create a new header with optional text | Write |\n| `googledocs_create_footer` | Create a new footer with optional text | Write |\n| `googledocs_create_footnote` | Add a footnote at a location or end of document | Write |\n| `googledocs_create_named_range` | Assign a name to a specific part of a document | Write |\n| `googledocs_delete_header` | Delete a header from a document | Write |\n| `googledocs_delete_footer` | Delete a footer from a document | Write |\n\n### Table Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_delete_table_row` | Delete a row from a table | Write |\n| `googledocs_delete_table_column` | Delete a column from a table | Write |\n| `googledocs_unmerge_table_cells` | Unmerge previously merged cells in a table | Write |\n| `googledocs_update_table_row_style` | Update row style (height, header marking) | Write |\n\n### Copying & Duplication\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_copy_document` | Create a copy of an existing document | Write |\n\n### Deletion\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_delete_content_range` | Delete a range of content from a document | Write |\n| `googledocs_delete_named_range` | Delete a named range from a document | Write |\n\n### Image Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_replace_image` | Replace an existing image with a new one from a URI | Write |\n\n## Code Examples\n\n### Search for documents\n\n```bash\nclawlink_call_tool --tool \"googledocs_search_documents\" \\\n --params '{\n \"query\": \"meeting notes\",\n \"page_size\": 10\n }'\n```\n\n### Read document plaintext\n\n```bash\nclawlink_call_tool --tool \"googledocs_get_document_plaintext\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\"\n }'\n```\n\n### Create a document from Markdown\n\n```bash\nclawlink_call_tool --tool \"googledocs_create_document_markdown\" \\\n --params '{\n \"title\": \"Project Brief\",\n \"markdown\": \"# Project Brief\\n\\n## Overview\\n\\nThis is the project overview section.\\n\\n## Next Steps\\n\\n1. Define requirements\\n2. Create mockups\\n3. Implement feature\"\n }'\n```\n\n### Insert text at a location\n\n```bash\nclawlink_call_tool --tool \"googledocs_insert_text_action\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\",\n \"text\": \"New paragraph content here.\",\n \"insertion_index\": 150\n }'\n```\n\n### Replace all text occurrences\n\n```bash\nclawlink_call_tool --tool \"googledocs_replace_all_text\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\",\n \"replace_text\": \"New Company Name\",\n \"search_text\": \"Old Company Name\"\n }'\n```\n\n### Copy a document\n\n```bash\nclawlink_call_tool --tool \"googledocs_copy_document\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Docs is connected.\n2. Call `clawlink_list_tools --integration google-docs` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-docs`.\n5. If no Google Docs tools appear, direct the user to https://claw-link.dev/dashboard?add=google-docs.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ search → get → export → call │\n│ │\n│ Example: Search docs → Get plaintext → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer search, read, export, and inspection operations before writes.\n4. For document creation, content replacement, Markdown imports, structural edits, or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Document IDs are stable Google Drive file IDs — capture them from search or get responses for subsequent operations.\n- `googledocs_insert_text_action`: Use `append_to_end=true` to safely append without index concerns. When using `insertion_index`, it must fall within an existing paragraph's bounds.\n- Table operations require knowing the table index within the document structure.\n- Every document segment (body, header, footer, footnote) ends with a final newline that cannot be deleted.\n- PDF export has a 10MB content limit enforced by Google Drive API.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration google-docs`. |\n| Missing connection | Google Docs is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-docs. |\n| `RESOURCE_NOT_FOUND` | Document does not exist. Check the document_id. |\n| `INVALID_ARGUMENT` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| `FORBIDDEN` | No read or write access to the document. Check sharing permissions. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `google-docs`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Google Docs API Overview](https://developers.google.com/docs/api)\n- [Documents Resource](https://developers.google.com/docs/api/reference/rest/v1/documents)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Google Drive](https://clawhub.ai/hith3sh/google-drive-files) — For file management, permissions, and Drive-level operations\n- [Google Sheets](https://clawhub.ai/hith3sh/google-sheets-spreadsheets) — For spreadsheet operations in Google Workspace\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"google-docs-documents\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1780936632912\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nGoogle Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and OpenClaw users use this skill to search, read, create, and update Google Docs documents through ClawLink-managed OAuth connections.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can access documents in the connected Google account and may handle sensitive document content.
\nMitigation: Use ClawLink-managed OAuth, verify the active Google Docs connection, and inspect sharing permissions when access level matters.
\nRisk: Create, update, replacement, and deletion tools can change document content or structure.
\nMitigation: Preview and explicitly confirm the target document and intended effect before any write or destructive operation.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/hith3sh/google-docs-documents)
\n- [Google Docs API overview](https://developers.google.com/docs/api)
\n- [Google Docs Documents resource](https://developers.google.com/docs/api/reference/rest/v1/documents)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink verification](https://claw-link.dev/verify)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown with inline bash commands and tool-call examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires a connected Google Docs account through ClawLink; write operations require user confirmation.]
\n\n## Skill Version(s):
\n1.0.1 (source: server release evidence)
\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 v0.1.1: 3 files, 6229 bytes\n\nFiles: skill-card.md (2145b), SKILL.md (15818b), _meta.json (140b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: google-docs-documents\ndescription: Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text, create drafts from prompts, insert content, or modify document structure.\n---\n\n# Google Docs\n\nAccess Google Docs via the Google Docs API with managed OAuth authentication. Search, read, create, and update documents stored in Google Drive.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Docs API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Docs |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Docs |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Docs │\n│ (User Chat) │ │ (OAuth) │ │ (Docs API) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Docs │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Drive │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Docs again.\"\n\n## Quick Start\n\n```bash\n# Search for documents\nclawlink_call_tool --tool \"googledocs_search_documents\" --params '{\"query\": \"report\"}'\n\n# Get document plaintext\nclawlink_call_tool --tool \"googledocs_get_document_plaintext\" --params '{\"document_id\": \"YOUR_DOCUMENT_ID\"}'\n\n# Create a new document\nclawlink_call_tool --tool \"googledocs_create_document\" --params '{\"title\": \"New Document\"}'\n```\n\n## Authentication\n\nAll Google Docs tool calls are authenticated automatically by ClawLink using the user's connected Google account.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Google Docs API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=google-docs and connect Google Docs.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `google-docs` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-docs\n```\n\n**Response:** Returns the live tool catalog for Google Docs.\n\n### Reconnect\n\nIf Google Docs tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-docs\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-docs`\n\n## Security & Permissions\n\n- Access is scoped to documents within the connected Google account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete content range, delete table row/column) are marked as high-impact and must be confirmed.\n- Document sharing permissions can be inspected to understand access levels before making changes.\n\n## Tool Reference\n\n### Document Discovery & Reading\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_search_documents` | Search for Google Docs by name, content, or date range | Read |\n| `googledocs_get_document_by_id` | Retrieve a document's full metadata | Read |\n| `googledocs_get_document_plaintext` | Get a best-effort plain-text rendering of a document | Read |\n| `googledocs_export_document_as_pdf` | Export a document as PDF (10MB limit) | Read |\n| `googledocs_list_spreadsheet_charts` | List charts from a linked Google Sheets spreadsheet | Read |\n\n### Document Creation\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_create_document` | Create a new empty document with a title | Write |\n| `googledocs_create_document_markdown` | Create a document initialized with Markdown content | Write |\n\n### Content Insertion & Updates\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_insert_text_action` | Insert text at a specific index or append to end | Write |\n| `googledocs_replace_all_text` | Replace all occurrences of a string throughout a document | Write |\n| `googledocs_update_document_markdown` | Replace entire document content with Markdown | Write |\n| `googledocs_update_document_section_markdown` | Insert or replace a section of a document with Markdown | Write |\n| `googledocs_update_existing_document` | Apply programmatic edits via batchUpdate API | Write |\n| `googledocs_update_document_style` | Update page size, margins, and default text direction | Write |\n\n### Structural Elements\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_insert_table_action` | Insert a table at a specific location | Write |\n| `googledocs_insert_table_column` | Insert a new column into an existing table | Write |\n| `googledocs_insert_page_break` | Insert a page break into a document | Write |\n| `googledocs_insert_inline_image` | Insert an image from a URI at a specific location | Write |\n| `googledocs_create_paragraph_bullets` | Add bullet formatting to paragraphs in a range | Write |\n| `googledocs_delete_paragraph_bullets` | Remove bullet formatting from paragraphs | Write |\n\n### Header, Footer & Named Ranges\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_create_header` | Create a new header with optional text | Write |\n| `googledocs_create_footer` | Create a new footer with optional text | Write |\n| `googledocs_create_footnote` | Add a footnote at a location or end of document | Write |\n| `googledocs_create_named_range` | Assign a name to a specific part of a document | Write |\n| `googledocs_delete_header` | Delete a header from a document | Write |\n| `googledocs_delete_footer` | Delete a footer from a document | Write |\n\n### Table Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_delete_table_row` | Delete a row from a table | Write |\n| `googledocs_delete_table_column` | Delete a column from a table | Write |\n| `googledocs_unmerge_table_cells` | Unmerge previously merged cells in a table | Write |\n| `googledocs_update_table_row_style` | Update row style (height, header marking) | Write |\n\n### Copying & Duplication\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_copy_document` | Create a copy of an existing document | Write |\n\n### Deletion\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_delete_content_range` | Delete a range of content from a document | Write |\n| `googledocs_delete_named_range` | Delete a named range from a document | Write |\n\n### Image Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googledocs_replace_image` | Replace an existing image with a new one from a URI | Write |\n\n## Code Examples\n\n### Search for documents\n\n```bash\nclawlink_call_tool --tool \"googledocs_search_documents\" \\\n --params '{\n \"query\": \"meeting notes\",\n \"page_size\": 10\n }'\n```\n\n### Read document plaintext\n\n```bash\nclawlink_call_tool --tool \"googledocs_get_document_plaintext\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\"\n }'\n```\n\n### Create a document from Markdown\n\n```bash\nclawlink_call_tool --tool \"googledocs_create_document_markdown\" \\\n --params '{\n \"title\": \"Project Brief\",\n \"markdown\": \"# Project Brief\\n\\n## Overview\\n\\nThis is the project overview section.\\n\\n## Next Steps\\n\\n1. Define requirements\\n2. Create mockups\\n3. Implement feature\"\n }'\n```\n\n### Insert text at a location\n\n```bash\nclawlink_call_tool --tool \"googledocs_insert_text_action\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\",\n \"text\": \"New paragraph content here.\",\n \"insertion_index\": 150\n }'\n```\n\n### Replace all text occurrences\n\n```bash\nclawlink_call_tool --tool \"googledocs_replace_all_text\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\",\n \"replace_text\": \"New Company Name\",\n \"search_text\": \"Old Company Name\"\n }'\n```\n\n### Copy a document\n\n```bash\nclawlink_call_tool --tool \"googledocs_copy_document\" \\\n --params '{\n \"document_id\": \"YOUR_DOCUMENT_ID\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Docs is connected.\n2. Call `clawlink_list_tools --integration google-docs` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-docs`.\n5. If no Google Docs tools appear, direct the user to https://claw-link.dev/dashboard?add=google-docs.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ search → get → export → call │\n│ │\n│ Example: Search docs → Get plaintext → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer search, read, export, and inspection operations before writes.\n4. For document creation, content replacement, Markdown imports, structural edits, or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Document IDs are stable Google Drive file IDs — capture them from search or get responses for subsequent operations.\n- `googledocs_insert_text_action`: Use `append_to_end=true` to safely append without index concerns. When using `insertion_index`, it must fall within an existing paragraph's bounds.\n- Table operations require knowing the table index within the document structure.\n- Every document segment (body, header, footer, footnote) ends with a final newline that cannot be deleted.\n- PDF export has a 10MB content limit enforced by Google Drive API.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration google-docs`. |\n| Missing connection | Google Docs is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-docs. |\n| `RESOURCE_NOT_FOUND` | Document does not exist. Check the document_id. |\n| `INVALID_ARGUMENT` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| `FORBIDDEN` | No read or write access to the document. Check sharing permissions. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `google-docs`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Google Docs API Overview](https://developers.google.com/docs/api)\n- [Documents Resource](https://developers.google.com/docs/api/reference/rest/v1/documents)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Google Drive](https://clawhub.ai/hith3sh/google-drive-files) — For file management, permissions, and Drive-level operations\n- [Google Sheets](https://clawhub.ai/hith3sh/google-sheets-spreadsheets) — For spreadsheet operations in Google Workspace\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v0.1.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"google-docs-documents\",\n \"version\": \"0.1.1\",\n \"publishedAt\": 1780839028769\n}\n\nFile v0.1.1:skill-card.md\n\n## Description:
\nGoogle Docs API integration with managed OAuth for searching, reading, creating, and updating Google Docs documents.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and OpenClaw users use this skill to connect a Google account through ClawLink, inspect Google Docs content, and create or update documents after confirming write operations.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires sensitive Google account access through OAuth.
\nMitigation: Review Google account permissions during OAuth and revoke the ClawLink or Google connection when it is no longer needed.
\nRisk: Write and destructive document actions can alter or remove Google Docs content.
\nMitigation: Confirm the target document and intended effect before create, update, delete, or structural edit operations.
\n\n\n## Reference(s):
\n- [Google Docs API Overview](https://developers.google.com/docs/api)
\n- [Google Docs Documents Resource](https://developers.google.com/docs/api/reference/rest/v1/documents)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [Google Docs Skill on ClawHub](https://clawhub.ai/hith3sh/google-docs-documents)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown with inline bash commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Includes OAuth connection checks, live tool discovery guidance, and confirmation guidance for write operations.]
\n\n## Skill Version(s):
\n0.1.1 (source: server release evidence)
\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 v0.1.0: 3 files, 3622 bytes\n\nFiles: skill-card.md (2507b), SKILL.md (5453b), _meta.json (140b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: google-docs-documents\ndescription: Search documents, read document text, create docs from text or Markdown, and update document content and structure — powered by ClawLink.\n---\n\n# Google Docs via ClawLink\n\nWork with Google Docs from chat — search documents, read document text, create new docs, and update existing document content and structure.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Google Docs API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect Google Docs at [claw-link.dev/dashboard?add=google-docs](https://claw-link.dev/dashboard?add=google-docs)\n7. When the user confirms Google Docs is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `google-docs` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting Google Docs\n\nTell the user to open https://claw-link.dev/dashboard?add=google-docs and connect Google Docs there. The page opens the add-connection panel filtered to Google Docs. ClawLink's hosted page runs the Google account connection flow — the user clicks through Google sign-in and consent. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `google-docs`.\n\n## Using Google Docs tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm Google Docs is connected.\n2. Call `clawlink_list_tools` with integration `google-docs`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-docs`.\n5. If no Google Docs tools appear, direct the user to https://claw-link.dev/dashboard?add=google-docs.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer search, read, export, and inspection operations before writes.\n4. For document creation, content replacement, Markdown imports, structural edits, or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical Google Docs tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- Search for Google Docs documents in Drive\n- Read document metadata, structure, or plain text\n- Export a document as PDF\n- Create new documents from prompts, plain text, or Markdown after confirmation\n- Insert text, tables, images, and page breaks after confirmation\n- Replace placeholders or update existing content after confirmation\n- Refresh an existing document from Markdown or structured source content after confirmation\n\n## Rules\n\n- Always use ClawLink tools for Google Docs. Do not ask the user for separate Google credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before creating documents or modifying existing content or structure.\n- If Google Docs is not connected, direct the user to https://claw-link.dev/dashboard?add=google-docs.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- Google Docs API: https://developers.google.com/docs/api\n\nFile v0.1.0:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"google-docs-documents\",\n \"version\": \"0.1.0\",\n \"publishedAt\": 1777815211442\n}\n\nFile v0.1.0:skill-card.md\n\n## Description:
\nSearch documents, read document text, create docs from text or Markdown, and update document content and structure -- powered by ClawLink.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nOpenClaw users and agents use this skill to connect Google Docs through ClawLink, discover the live Google Docs tool catalog, and search, read, export, create, or update documents with confirmation before writes.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Connecting Google Docs through ClawLink grants access based on the Google consent scopes approved by the user.
\nMitigation: Install only if ClawLink is trusted, review Google consent scopes, and connect the intended Google account.
\nRisk: Document creation or edits could change the wrong document or introduce unintended content.
\nMitigation: Use ClawLink previews and confirm the target document and planned change before creating or modifying Google Docs.
\nRisk: Pairing or credential material could be exposed if copied into chat.
\nMitigation: Use the hosted ClawLink pairing flow and do not paste or repeat raw ClawLink credentials in chat.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/google-docs-documents)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [Connect Google Docs in ClawLink](https://claw-link.dev/dashboard?add=google-docs)
\n- [Google Docs API](https://developers.google.com/docs/api)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Shell commands, Configuration instructions, API calls]
\n**Output Format:** [Markdown instructions with inline shell commands and ClawLink tool-call guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses live ClawLink tool schemas and previews before document creation or modification.]
\n\n## Skill Version(s):
\n0.1.0 (source: 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.
","readmeExcerpt":"Skill: Google Docs Owner: hith3sh Summary: Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text,... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:09:50.722Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic s","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Docs │\n│ (User Chat) │ │ (OAuth) │ │ (Docs API) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Docs │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Drive │\n └──────────┘ └──────────┘ └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# Search for documents\nclawlink_call_tool --tool \"googledocs_search_documents\" --params '{\"query\": \"report\"}'\n\n# Get document plaintext\nclawlink_call_tool --tool \"googledocs_get_document_plaintext\" --params '{\"document_id\": \"YOUR_DOCUMENT_ID\"}'\n\n# Create a new document\nclawlink_call_tool --tool \"googledocs_create_document\" --params '{\"title\": \"New Document\"}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration google-docs"},{"language":"bash","snippet":"clawlink_call_tool --tool \"googledocs_search_documents\" \\\n --params '{\n \"query\": \"meeting notes\",\n \"page_size\": 10\n }'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: google-docs-documents\ndescription: Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text, create drafts from prompts, insert content, or modify document structure.\n---\n\n# Google Docs\n\n\n\nAccess Google Docs via the Google Docs API with managed OAuth authentication. Search, read, create, and update documents stored in Google Drive.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-docs-documents) for hosted connection flows and credentials so you do not need to configure Google Docs API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Docs |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Docs |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Docs │\n│ (User Chat) │ │ (OAuth) │ │ (Docs API) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Docs │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Drive │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Docs again.\"\n\n## Quick Start\n\n```bash\n# Search for documents\nclawlink_call_tool --tool \"googledocs_search_documents\" --params '{\"query\": \"report\"}'\n\n# Get document plaintext\nclawlink_call_tool --tool \"googledocs_get_document_plaintext\" "},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"google-docs-documents\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780988990722\n}"},{"path":"skill-card.md","content":"## Description:\n\nGoogle Docs API integration with managed OAuth for searching, reading, creating, and updating Google Docs documents.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\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 find, read, create, and update Google Docs documents through a connected Google account.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill relies on ClawLink as an external OAuth bridge for Google Docs access.\n\nMitigation: Install only after reviewing ClawLink verification or source information where available, and use the least-privileged Google account suitable for the task.\n\nRisk: Connected tools can modify Google Docs content.\n\nMitigation: Preview and explicitly confirm create, update, delete, and other write operations before execution.\n\nRisk: OAuth access may remain available after the immediate task is complete.\n\nMitigation: Revoke the Google authorization or remove the plugin allowlist entry when the integration is no longer needed.\n\n## Reference(s):\n\n- [Google Docs API Overview](https://developers.google.com/docs/api)\n- [Google Docs Documents Resource](https://developers.google.com/docs/api/reference/rest/v1/documents)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/google-docs-documents)\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 tool-call examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include Google Docs document identifiers, previews, document text, and confirmation prompts before write operations.]\n\n## Skill Version(s):\n\n1.0.5 (source: 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."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text,... Skill: Google Docs Owner: hith3sh Summary: Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text,... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:09:50.722Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic s","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1028,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T03:00:06.679Z","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-09T03:00:06.679Z","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-09T14:33:24.444Z","emptyReason":null},"items":[{"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":"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-04-10T18:48:31.762Z","createdAt":"2026-02-25T03:38:16.584Z","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"}]}}}