{"id":"670999b3-f224-483c-aadb-8cec565d09bd","entityType":"agent","slug":"clawhub-hith3sh-google-chat-messaging","name":"Google Chat","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-google-chat-messaging","canonicalPath":"/agent/clawhub-hith3sh-google-chat-messaging","generatedAt":"2026-10-09T22:08:28.177Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T11:28:53.422Z","emptyReason":null},"description":"Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spac... Skill: Google Chat Owner: hith3sh Summary: Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spac... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:09:27.832Z | 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. 2.8K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:google-chat-messaging","sourceUrl":"https://clawhub.ai/hith3sh/google-chat-messaging","homepage":"https://clawhub.ai/hith3sh/skills/google-chat-messaging","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/google-chat-messaging","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/google-chat-messaging","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":69,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spac..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T11:28:53.422Z","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-09T11:28:53.422Z","emptyReason":null},"stars":null,"forks":null,"downloads":2795,"packageName":null,"latestVersion":"1.0.6","tractionLabel":"2.8K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T11:28:53.422Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T11:28:53.422Z","lastCrawledAt":"2026-10-09T11:28:53.422Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T11:28:53.422Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.6","createdAt":"2026-06-09T07:09:27.832Z","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":5548},{"version":"1.0.5","createdAt":"2026-06-09T06:08:59.446Z","changelog":"- Documentation refreshed: SKILL.md updated with small edits and formatting adjustments. - Image URL in documentation updated to include a version query. - Removed the redundant file: skill-card.md.","fileCount":3,"zipByteSize":5490},{"version":"1.0.4","createdAt":"2026-06-09T04:55:17.528Z","changelog":"- Removed the file skill-card.md. - No changes to functionality, setup, or user workflow. - Documentation remains unchanged aside from file removal.","fileCount":3,"zipByteSize":5446},{"version":"1.0.1","createdAt":"2026-06-08T16:36:55.715Z","changelog":"- Added a Google Chat brand logo to the documentation. - Made minor edits to SKILL.md formatting and content for clarity. - Removed the separate skill-card.md file.","fileCount":3,"zipByteSize":5489},{"version":"0.1.1","createdAt":"2026-06-07T13:30:06.377Z","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":5339},{"version":"0.1.0","createdAt":"2026-05-16T17:49:46.488Z","changelog":"- Initial release of google-chat-messaging skill. - Enables management of Google Chat spaces, members, messages, attachments, and threaded conversations via ClawLink integration. - No need to configure Google Chat API credentials manually; pairing and connection handled through ClawLink. - Provides step-by-step setup instructions for installing and configuring the ClawLink plugin. - Lists best practices and operational rules, including confirmation before write actions and dynamic discovery of available tools.","fileCount":3,"zipByteSize":3308}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:google-chat-messaging","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-chat-messaging/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-chat-messaging/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-chat-messaging/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-chat-messaging/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-chat-messaging/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-chat-messaging/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-09T22:08:28.175Z"}},"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-chat-messaging/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-chat-messaging/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-chat-messaging/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-chat-messaging/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-09T11:28:53.422Z","emptyReason":null},"readme":"Skill: Google Chat\n\nOwner: hith3sh\n\nSummary: Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spac...\n\nTags: latest:1.0.6\n\nVersion history:\n\nv1.0.6 | 2026-06-09T07:09:27.832Z | 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.5 | 2026-06-09T06:08:59.446Z | auto\n\n- Documentation refreshed: SKILL.md updated with small edits and formatting adjustments.\n- Image URL in documentation updated to include a version query.\n- Removed the redundant file: skill-card.md.\n\nv1.0.4 | 2026-06-09T04:55:17.528Z | auto\n\n- Removed the file skill-card.md.\n- No changes to functionality, setup, or user workflow.\n- Documentation remains unchanged aside from file removal.\n\nv1.0.1 | 2026-06-08T16:36:55.715Z | auto\n\n- Added a Google Chat brand logo to the documentation.\n- Made minor edits to SKILL.md formatting and content for clarity.\n- Removed the separate skill-card.md file.\n\nv0.1.1 | 2026-06-07T13:30:06.377Z | 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-16T17:49:46.488Z | auto\n\n- Initial release of google-chat-messaging skill.\n- Enables management of Google Chat spaces, members, messages, attachments, and threaded conversations via ClawLink integration.\n- No need to configure Google Chat API credentials manually; pairing and connection handled through ClawLink.\n- Provides step-by-step setup instructions for installing and configuring the ClawLink plugin.\n- Lists best practices and operational rules, including confirmation before write actions and dynamic discovery of available tools.\n\nArchive index:\n\nArchive v1.0.6: 3 files, 5548 bytes\n\nFiles: skill-card.md (2483b), SKILL.md (13452b), _meta.json (140b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: google-chat-messaging\ndescription: Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spaces and members, read or inspect messages, send messages after confirmation, create or manage spaces, or work with threads and attachments in Google Chat.\n---\n\n# Google Chat\n\n\n\nAccess Google Chat via the Google Chat API with OAuth authentication. Manage spaces, members, messages, attachments, and threaded conversations.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-chat-messaging) for hosted connection flows and credentials so you do not need to configure Google Chat API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Chat |\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 Chat |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Chat API │\n│ (User Chat) │ │ (OAuth) │ │ (REST) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Google Chat │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Chat │\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 Chat again.\"\n\n## Quick Start\n\n```bash\n# List spaces the user is member of\nclawlink_call_tool --tool \"google_chat_list_spaces\" --params '{}'\n\n# List members in a space\nclawlink_call_tool --tool \"google_chat_list_members\" --params '{\"parent\": \"spaces/space-id\"}'\n\n# Send a message to a space\nclawlink_call_tool --tool \"google_chat_create_message\" --params '{\"parent\": \"spaces/space-id\", \"text\": \"Hello from OpenClaw!\"}'\n```\n\n## Authentication\n\nAll Google Chat 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 Chat 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-chat and connect Google Chat.\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-chat` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-chat\n```\n\n**Response:** Returns the live tool catalog for Google Chat.\n\n### Reconnect\n\nIf Google Chat tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-chat\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-chat`\n\n## Security & Permissions\n\n- Access is scoped to Google Chat spaces and messages accessible to the connected Google account.\n- **All write operations require explicit user confirmation.** Before executing any message send, space create, or member change, confirm the intended effect with the user.\n- Destructive actions (deleting spaces, removing members) are marked as high-impact and must be confirmed.\n- Message size is limited to 32,000 bytes. Card-based messages require bot authentication.\n\n## Tool Reference\n\n### Spaces\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_spaces` | List spaces the authenticated user is a member of | Read |\n| `google_chat_get_space` | Get details for a specific space | Read |\n| `google_chat_create_space` | Create a new space | Write |\n| `google_chat_update_space` | Update space name, description, or settings | Write |\n| `google_chat_delete_space` | Delete a space | Write |\n\n### Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_members` | List all members in a space | Read |\n| `google_chat_get_member` | Get details for a specific member | Read |\n| `google_chat_create_membership` | Add a user or group to a space | Write |\n| `google_chat_delete_membership` | Remove a member from a space | Write |\n\n### Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_messages` | List messages in a space | Read |\n| `google_chat_get_message` | Get a specific message | Read |\n| `google_chat_create_message` | Send a message to a space (supports threading) | Write |\n| `google_chat_update_message` | Update a message's text or content | Write |\n| `google_chat_delete_message` | Delete a message | Write |\n\n### Reactions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_reactions` | List reactions to a message | Read |\n| `google_chat_create_reaction` | Add an emoji reaction to a message | Write |\n| `google_chat_delete_reaction` | Remove an emoji reaction | Write |\n\n### Attachments & Custom Emoji\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_attachments` | List attachments in a space | Read |\n| `google_chat_create_custom_emoji` | Create a custom emoji for the organization | Write |\n\n### Sections\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_create_section` | Create a custom section in a space | Write |\n\n## Code Examples\n\n### List spaces\n\n```bash\nclawlink_call_tool --tool \"google_chat_list_spaces\" \\\n --params '{}'\n```\n\n### Send a message to a space\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_message\" \\\n --params '{\n \"parent\": \"spaces/space-id\",\n \"text\": \"Hello team! Just wanted to share an update on the project status.\"\n }'\n```\n\n### Reply in a thread\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_message\" \\\n --params '{\n \"parent\": \"spaces/space-id\",\n \"text\": \"Thanks for the update!\",\n \"thread\": {\n \"thread_key\": \"original-message-id\"\n }\n }'\n```\n\n### Add a reaction to a message\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_reaction\" \\\n --params '{\n \"parent\": \"spaces/space-id/messages/message-id\",\n \"emoji_unicode\": \"👍\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Chat is connected.\n2. Call `clawlink_list_tools --integration google-chat` 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-chat`.\n5. If no Google Chat tools appear, direct the user to https://claw-link.dev/dashboard?add=google-chat.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List spaces → Get space → Show members │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Preview message → User confirms → Execute send │\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 read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes 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- Space names use format `spaces/space-id` in API calls.\n- Message threading uses `thread_key` to reply to existing threads.\n- Custom emojis are only available for Google Workspace accounts and require admin enablement.\n- With user authentication, only plain text messages are supported. Card-based messages require bot authentication.\n- Message size limit is 32,000 bytes.\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-chat`. |\n| Missing connection | Google Chat is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-chat. |\n| `404 Not Found` | Space, message, or member does not exist. Verify the IDs. |\n| `403 Forbidden` | Insufficient permissions or the space requires bot authentication. |\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-chat`.\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 Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)\n- [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-chat-messaging)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n\n## Related Skills\n\n- [Slack](https://clawhub.ai/hith3sh/slack) — For alternative team messaging\n- [Gmail](https://clawhub.ai/hith3sh/gmail-email) — For email alongside chat\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-chat-messaging)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.6:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"google-chat-messaging\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1780988967832\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nWork with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API.\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\nDevelopers and OpenClaw users use this skill to connect Google Chat through ClawLink, inspect spaces, members, messages, reactions, attachments, and threads, and perform confirmed write actions such as sending messages or managing spaces.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Connecting Google Chat through ClawLink gives the integration access to Chat data available to the connected Google account.\n\nMitigation: Connect only accounts whose Chat access is appropriate for this integration, and verify the Google Chat connection before use.\n\nRisk: Write-capable tools can send or modify messages, spaces, memberships, reactions, sections, or custom emoji.\n\nMitigation: Preview write or destructive actions and execute them only after explicit user confirmation.\n\nRisk: Using an unpinned plugin release can make the installed behavior harder to review over time.\n\nMitigation: Prefer a pinned or verified ClawLink plugin release when available.\n\n## Reference(s):\n\n- [Google Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)\n- [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-chat-messaging)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with inline shell commands and JSON tool parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires a connected ClawLink Google Chat integration; write and destructive actions require explicit user confirmation; Google Chat messages are limited to 32000 bytes.]\n\n## Skill Version(s):\n\n1.0.6 (source: server evidence release.version)\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.5: 3 files, 5490 bytes\n\nFiles: skill-card.md (2532b), SKILL.md (13230b), _meta.json (140b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: google-chat-messaging\ndescription: Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spaces and members, read or inspect messages, send messages after confirmation, create or manage spaces, or work with threads and attachments in Google Chat.\n---\n\n# Google Chat\n\n\n\nAccess Google Chat via the Google Chat API with OAuth authentication. Manage spaces, members, messages, attachments, and threaded conversations.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Chat API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Chat |\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 Chat |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Chat API │\n│ (User Chat) │ │ (OAuth) │ │ (REST) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Google Chat │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Chat │\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 Chat again.\"\n\n## Quick Start\n\n```bash\n# List spaces the user is member of\nclawlink_call_tool --tool \"google_chat_list_spaces\" --params '{}'\n\n# List members in a space\nclawlink_call_tool --tool \"google_chat_list_members\" --params '{\"parent\": \"spaces/space-id\"}'\n\n# Send a message to a space\nclawlink_call_tool --tool \"google_chat_create_message\" --params '{\"parent\": \"spaces/space-id\", \"text\": \"Hello from OpenClaw!\"}'\n```\n\n## Authentication\n\nAll Google Chat 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 Chat 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-chat and connect Google Chat.\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-chat` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-chat\n```\n\n**Response:** Returns the live tool catalog for Google Chat.\n\n### Reconnect\n\nIf Google Chat tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-chat\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-chat`\n\n## Security & Permissions\n\n- Access is scoped to Google Chat spaces and messages accessible to the connected Google account.\n- **All write operations require explicit user confirmation.** Before executing any message send, space create, or member change, confirm the intended effect with the user.\n- Destructive actions (deleting spaces, removing members) are marked as high-impact and must be confirmed.\n- Message size is limited to 32,000 bytes. Card-based messages require bot authentication.\n\n## Tool Reference\n\n### Spaces\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_spaces` | List spaces the authenticated user is a member of | Read |\n| `google_chat_get_space` | Get details for a specific space | Read |\n| `google_chat_create_space` | Create a new space | Write |\n| `google_chat_update_space` | Update space name, description, or settings | Write |\n| `google_chat_delete_space` | Delete a space | Write |\n\n### Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_members` | List all members in a space | Read |\n| `google_chat_get_member` | Get details for a specific member | Read |\n| `google_chat_create_membership` | Add a user or group to a space | Write |\n| `google_chat_delete_membership` | Remove a member from a space | Write |\n\n### Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_messages` | List messages in a space | Read |\n| `google_chat_get_message` | Get a specific message | Read |\n| `google_chat_create_message` | Send a message to a space (supports threading) | Write |\n| `google_chat_update_message` | Update a message's text or content | Write |\n| `google_chat_delete_message` | Delete a message | Write |\n\n### Reactions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_reactions` | List reactions to a message | Read |\n| `google_chat_create_reaction` | Add an emoji reaction to a message | Write |\n| `google_chat_delete_reaction` | Remove an emoji reaction | Write |\n\n### Attachments & Custom Emoji\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_attachments` | List attachments in a space | Read |\n| `google_chat_create_custom_emoji` | Create a custom emoji for the organization | Write |\n\n### Sections\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_create_section` | Create a custom section in a space | Write |\n\n## Code Examples\n\n### List spaces\n\n```bash\nclawlink_call_tool --tool \"google_chat_list_spaces\" \\\n --params '{}'\n```\n\n### Send a message to a space\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_message\" \\\n --params '{\n \"parent\": \"spaces/space-id\",\n \"text\": \"Hello team! Just wanted to share an update on the project status.\"\n }'\n```\n\n### Reply in a thread\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_message\" \\\n --params '{\n \"parent\": \"spaces/space-id\",\n \"text\": \"Thanks for the update!\",\n \"thread\": {\n \"thread_key\": \"original-message-id\"\n }\n }'\n```\n\n### Add a reaction to a message\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_reaction\" \\\n --params '{\n \"parent\": \"spaces/space-id/messages/message-id\",\n \"emoji_unicode\": \"👍\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Chat is connected.\n2. Call `clawlink_list_tools --integration google-chat` 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-chat`.\n5. If no Google Chat tools appear, direct the user to https://claw-link.dev/dashboard?add=google-chat.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List spaces → Get space → Show members │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Preview message → User confirms → Execute send │\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 read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes 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- Space names use format `spaces/space-id` in API calls.\n- Message threading uses `thread_key` to reply to existing threads.\n- Custom emojis are only available for Google Workspace accounts and require admin enablement.\n- With user authentication, only plain text messages are supported. Card-based messages require bot authentication.\n- Message size limit is 32,000 bytes.\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-chat`. |\n| Missing connection | Google Chat is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-chat. |\n| `404 Not Found` | Space, message, or member does not exist. Verify the IDs. |\n| `403 Forbidden` | Insufficient permissions or the space requires bot authentication. |\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-chat`.\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 Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)\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- [Slack](https://clawhub.ai/hith3sh/slack) — For alternative team messaging\n- [Gmail](https://clawhub.ai/hith3sh/gmail-email) — For email alongside chat\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"google-chat-messaging\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780985339446\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:
\nWork with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API.
\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:
\nEmployees, external collaborators, and developers use this skill to inspect Google Chat spaces, members, messages, attachments, reactions, and threads, and to perform confirmed write actions such as sending messages or managing spaces and memberships.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill connects a user's Google Chat account through ClawLink and can access spaces, messages, memberships, and attachments available to that account.
\nMitigation: Install only when comfortable granting that connection, verify the Google Chat integration is active, and keep access scoped to the connected account.
\nRisk: Write actions can send messages, delete content, create spaces, or change space membership.
\nMitigation: Preview and explicitly confirm write, destructive, and membership-changing actions before execution.
\n\n\n## Reference(s):
\n- [Google Chat Skill on ClawHub](https://clawhub.ai/hith3sh/google-chat-messaging)
\n- [hith3sh ClawHub profile](https://clawhub.ai/user/hith3sh)
\n- [Google Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)
\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink Docs for OpenClaw](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Shell commands, Configuration, API calls, Markdown]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Read operations may be executed directly; write and destructive operations require user confirmation before execution.]
\n\n## Skill Version(s):
\n1.0.5 (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 v1.0.4: 3 files, 5446 bytes\n\nFiles: skill-card.md (2427b), SKILL.md (13226b), _meta.json (140b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: google-chat-messaging\ndescription: Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spaces and members, read or inspect messages, send messages after confirmation, create or manage spaces, or work with threads and attachments in Google Chat.\n---\n\n# Google Chat\n\n\n\nAccess Google Chat via the Google Chat API with OAuth authentication. Manage spaces, members, messages, attachments, and threaded conversations.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Chat API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Chat |\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 Chat |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Chat API │\n│ (User Chat) │ │ (OAuth) │ │ (REST) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Google Chat │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Chat │\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 Chat again.\"\n\n## Quick Start\n\n```bash\n# List spaces the user is member of\nclawlink_call_tool --tool \"google_chat_list_spaces\" --params '{}'\n\n# List members in a space\nclawlink_call_tool --tool \"google_chat_list_members\" --params '{\"parent\": \"spaces/space-id\"}'\n\n# Send a message to a space\nclawlink_call_tool --tool \"google_chat_create_message\" --params '{\"parent\": \"spaces/space-id\", \"text\": \"Hello from OpenClaw!\"}'\n```\n\n## Authentication\n\nAll Google Chat 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 Chat 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-chat and connect Google Chat.\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-chat` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-chat\n```\n\n**Response:** Returns the live tool catalog for Google Chat.\n\n### Reconnect\n\nIf Google Chat tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-chat\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-chat`\n\n## Security & Permissions\n\n- Access is scoped to Google Chat spaces and messages accessible to the connected Google account.\n- **All write operations require explicit user confirmation.** Before executing any message send, space create, or member change, confirm the intended effect with the user.\n- Destructive actions (deleting spaces, removing members) are marked as high-impact and must be confirmed.\n- Message size is limited to 32,000 bytes. Card-based messages require bot authentication.\n\n## Tool Reference\n\n### Spaces\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_spaces` | List spaces the authenticated user is a member of | Read |\n| `google_chat_get_space` | Get details for a specific space | Read |\n| `google_chat_create_space` | Create a new space | Write |\n| `google_chat_update_space` | Update space name, description, or settings | Write |\n| `google_chat_delete_space` | Delete a space | Write |\n\n### Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_members` | List all members in a space | Read |\n| `google_chat_get_member` | Get details for a specific member | Read |\n| `google_chat_create_membership` | Add a user or group to a space | Write |\n| `google_chat_delete_membership` | Remove a member from a space | Write |\n\n### Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_messages` | List messages in a space | Read |\n| `google_chat_get_message` | Get a specific message | Read |\n| `google_chat_create_message` | Send a message to a space (supports threading) | Write |\n| `google_chat_update_message` | Update a message's text or content | Write |\n| `google_chat_delete_message` | Delete a message | Write |\n\n### Reactions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_reactions` | List reactions to a message | Read |\n| `google_chat_create_reaction` | Add an emoji reaction to a message | Write |\n| `google_chat_delete_reaction` | Remove an emoji reaction | Write |\n\n### Attachments & Custom Emoji\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_attachments` | List attachments in a space | Read |\n| `google_chat_create_custom_emoji` | Create a custom emoji for the organization | Write |\n\n### Sections\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_create_section` | Create a custom section in a space | Write |\n\n## Code Examples\n\n### List spaces\n\n```bash\nclawlink_call_tool --tool \"google_chat_list_spaces\" \\\n --params '{}'\n```\n\n### Send a message to a space\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_message\" \\\n --params '{\n \"parent\": \"spaces/space-id\",\n \"text\": \"Hello team! Just wanted to share an update on the project status.\"\n }'\n```\n\n### Reply in a thread\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_message\" \\\n --params '{\n \"parent\": \"spaces/space-id\",\n \"text\": \"Thanks for the update!\",\n \"thread\": {\n \"thread_key\": \"original-message-id\"\n }\n }'\n```\n\n### Add a reaction to a message\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_reaction\" \\\n --params '{\n \"parent\": \"spaces/space-id/messages/message-id\",\n \"emoji_unicode\": \"👍\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Chat is connected.\n2. Call `clawlink_list_tools --integration google-chat` 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-chat`.\n5. If no Google Chat tools appear, direct the user to https://claw-link.dev/dashboard?add=google-chat.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List spaces → Get space → Show members │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Preview message → User confirms → Execute send │\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 read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes 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- Space names use format `spaces/space-id` in API calls.\n- Message threading uses `thread_key` to reply to existing threads.\n- Custom emojis are only available for Google Workspace accounts and require admin enablement.\n- With user authentication, only plain text messages are supported. Card-based messages require bot authentication.\n- Message size limit is 32,000 bytes.\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-chat`. |\n| Missing connection | Google Chat is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-chat. |\n| `404 Not Found` | Space, message, or member does not exist. Verify the IDs. |\n| `403 Forbidden` | Insufficient permissions or the space requires bot authentication. |\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-chat`.\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 Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)\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- [Slack](https://clawhub.ai/hith3sh/slack) — For alternative team messaging\n- [Gmail](https://clawhub.ai/hith3sh/gmail-email) — For email alongside chat\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-chat-messaging\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1780980917528\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nWork with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API.
\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 Chat account through ClawLink, inspect spaces, members, messages, attachments, and threads, and perform confirmed write actions such as sending messages or managing memberships.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill connects to a Google Chat account through ClawLink using OAuth and can access spaces and messages available to that account.
\nMitigation: Review the Google OAuth permissions during connection and install only if that ClawLink connection model is acceptable.
\nRisk: Write and destructive actions can send messages, change spaces, or modify memberships.
\nMitigation: Preview and explicitly confirm write or delete operations before execution, especially membership changes and space deletion.
\n\n\n## Reference(s):
\n- [Google Chat Skill on ClawHub](https://clawhub.ai/hith3sh/google-chat-messaging)
\n- [hith3sh Publisher Profile](https://clawhub.ai/user/hith3sh)
\n- [Google Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)
\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink](https://claw-link.dev)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON parameter examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include Google Chat tool names, ClawLink setup steps, OAuth connection guidance, and previews for confirmed write 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, 5489 bytes\n\nFiles: skill-card.md (2487b), SKILL.md (13226b), _meta.json (140b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: google-chat-messaging\ndescription: Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spaces and members, read or inspect messages, send messages after confirmation, create or manage spaces, or work with threads and attachments in Google Chat.\n---\n\n# Google Chat\n\n\n\nAccess Google Chat via the Google Chat API with OAuth authentication. Manage spaces, members, messages, attachments, and threaded conversations.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Chat API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Chat |\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 Chat |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Chat API │\n│ (User Chat) │ │ (OAuth) │ │ (REST) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Google Chat │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Chat │\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 Chat again.\"\n\n## Quick Start\n\n```bash\n# List spaces the user is member of\nclawlink_call_tool --tool \"google_chat_list_spaces\" --params '{}'\n\n# List members in a space\nclawlink_call_tool --tool \"google_chat_list_members\" --params '{\"parent\": \"spaces/space-id\"}'\n\n# Send a message to a space\nclawlink_call_tool --tool \"google_chat_create_message\" --params '{\"parent\": \"spaces/space-id\", \"text\": \"Hello from OpenClaw!\"}'\n```\n\n## Authentication\n\nAll Google Chat 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 Chat 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-chat and connect Google Chat.\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-chat` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-chat\n```\n\n**Response:** Returns the live tool catalog for Google Chat.\n\n### Reconnect\n\nIf Google Chat tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-chat\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-chat`\n\n## Security & Permissions\n\n- Access is scoped to Google Chat spaces and messages accessible to the connected Google account.\n- **All write operations require explicit user confirmation.** Before executing any message send, space create, or member change, confirm the intended effect with the user.\n- Destructive actions (deleting spaces, removing members) are marked as high-impact and must be confirmed.\n- Message size is limited to 32,000 bytes. Card-based messages require bot authentication.\n\n## Tool Reference\n\n### Spaces\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_spaces` | List spaces the authenticated user is a member of | Read |\n| `google_chat_get_space` | Get details for a specific space | Read |\n| `google_chat_create_space` | Create a new space | Write |\n| `google_chat_update_space` | Update space name, description, or settings | Write |\n| `google_chat_delete_space` | Delete a space | Write |\n\n### Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_members` | List all members in a space | Read |\n| `google_chat_get_member` | Get details for a specific member | Read |\n| `google_chat_create_membership` | Add a user or group to a space | Write |\n| `google_chat_delete_membership` | Remove a member from a space | Write |\n\n### Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_messages` | List messages in a space | Read |\n| `google_chat_get_message` | Get a specific message | Read |\n| `google_chat_create_message` | Send a message to a space (supports threading) | Write |\n| `google_chat_update_message` | Update a message's text or content | Write |\n| `google_chat_delete_message` | Delete a message | Write |\n\n### Reactions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_reactions` | List reactions to a message | Read |\n| `google_chat_create_reaction` | Add an emoji reaction to a message | Write |\n| `google_chat_delete_reaction` | Remove an emoji reaction | Write |\n\n### Attachments & Custom Emoji\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_attachments` | List attachments in a space | Read |\n| `google_chat_create_custom_emoji` | Create a custom emoji for the organization | Write |\n\n### Sections\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_create_section` | Create a custom section in a space | Write |\n\n## Code Examples\n\n### List spaces\n\n```bash\nclawlink_call_tool --tool \"google_chat_list_spaces\" \\\n --params '{}'\n```\n\n### Send a message to a space\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_message\" \\\n --params '{\n \"parent\": \"spaces/space-id\",\n \"text\": \"Hello team! Just wanted to share an update on the project status.\"\n }'\n```\n\n### Reply in a thread\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_message\" \\\n --params '{\n \"parent\": \"spaces/space-id\",\n \"text\": \"Thanks for the update!\",\n \"thread\": {\n \"thread_key\": \"original-message-id\"\n }\n }'\n```\n\n### Add a reaction to a message\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_reaction\" \\\n --params '{\n \"parent\": \"spaces/space-id/messages/message-id\",\n \"emoji_unicode\": \"👍\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Chat is connected.\n2. Call `clawlink_list_tools --integration google-chat` 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-chat`.\n5. If no Google Chat tools appear, direct the user to https://claw-link.dev/dashboard?add=google-chat.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List spaces → Get space → Show members │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Preview message → User confirms → Execute send │\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 read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes 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- Space names use format `spaces/space-id` in API calls.\n- Message threading uses `thread_key` to reply to existing threads.\n- Custom emojis are only available for Google Workspace accounts and require admin enablement.\n- With user authentication, only plain text messages are supported. Card-based messages require bot authentication.\n- Message size limit is 32,000 bytes.\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-chat`. |\n| Missing connection | Google Chat is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-chat. |\n| `404 Not Found` | Space, message, or member does not exist. Verify the IDs. |\n| `403 Forbidden` | Insufficient permissions or the space requires bot authentication. |\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-chat`.\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 Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)\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- [Slack](https://clawhub.ai/hith3sh/slack) — For alternative team messaging\n- [Gmail](https://clawhub.ai/hith3sh/gmail-email) — For email alongside chat\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-chat-messaging\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1780936615715\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nWork with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API.
\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:
\nEmployees, external collaborators, developers, and agent users use this skill to inspect Google Chat spaces and messages, manage memberships and spaces, and draft or send Chat messages through the connected Google account.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The OAuth connection grants ClawLink-mediated access to Google Chat data available to the connected Google account.
\nMitigation: Approve the OAuth connection only after confirming the ClawLink integration is trusted and appropriate for the account.
\nRisk: Write actions can send messages, change memberships, alter spaces, or delete Google Chat resources.
\nMitigation: Preview and explicitly confirm message sends, member changes, space changes, and deletions before executing them.
\nRisk: Tool availability and parameters may vary with the live Google Chat integration catalog.
\nMitigation: Use the live ClawLink integration and tool catalog before calling tools, and describe unfamiliar tools before invoking them.
\n\n\n## Reference(s):
\n- [ClawHub Google Chat Skill](https://clawhub.ai/hith3sh/google-chat-messaging)
\n- [Google Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)
\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses OAuth through ClawLink; write and destructive 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, 5339 bytes\n\nFiles: skill-card.md (2191b), SKILL.md (13107b), _meta.json (140b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: google-chat-messaging\ndescription: Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spaces and members, read or inspect messages, send messages after confirmation, create or manage spaces, or work with threads and attachments in Google Chat.\n---\n\n# Google Chat\n\nAccess Google Chat via the Google Chat API with OAuth authentication. Manage spaces, members, messages, attachments, and threaded conversations.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Chat API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Chat |\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 Chat |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Chat API │\n│ (User Chat) │ │ (OAuth) │ │ (REST) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Google Chat │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Chat │\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 Chat again.\"\n\n## Quick Start\n\n```bash\n# List spaces the user is member of\nclawlink_call_tool --tool \"google_chat_list_spaces\" --params '{}'\n\n# List members in a space\nclawlink_call_tool --tool \"google_chat_list_members\" --params '{\"parent\": \"spaces/space-id\"}'\n\n# Send a message to a space\nclawlink_call_tool --tool \"google_chat_create_message\" --params '{\"parent\": \"spaces/space-id\", \"text\": \"Hello from OpenClaw!\"}'\n```\n\n## Authentication\n\nAll Google Chat 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 Chat 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-chat and connect Google Chat.\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-chat` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-chat\n```\n\n**Response:** Returns the live tool catalog for Google Chat.\n\n### Reconnect\n\nIf Google Chat tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-chat\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-chat`\n\n## Security & Permissions\n\n- Access is scoped to Google Chat spaces and messages accessible to the connected Google account.\n- **All write operations require explicit user confirmation.** Before executing any message send, space create, or member change, confirm the intended effect with the user.\n- Destructive actions (deleting spaces, removing members) are marked as high-impact and must be confirmed.\n- Message size is limited to 32,000 bytes. Card-based messages require bot authentication.\n\n## Tool Reference\n\n### Spaces\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_spaces` | List spaces the authenticated user is a member of | Read |\n| `google_chat_get_space` | Get details for a specific space | Read |\n| `google_chat_create_space` | Create a new space | Write |\n| `google_chat_update_space` | Update space name, description, or settings | Write |\n| `google_chat_delete_space` | Delete a space | Write |\n\n### Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_members` | List all members in a space | Read |\n| `google_chat_get_member` | Get details for a specific member | Read |\n| `google_chat_create_membership` | Add a user or group to a space | Write |\n| `google_chat_delete_membership` | Remove a member from a space | Write |\n\n### Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_messages` | List messages in a space | Read |\n| `google_chat_get_message` | Get a specific message | Read |\n| `google_chat_create_message` | Send a message to a space (supports threading) | Write |\n| `google_chat_update_message` | Update a message's text or content | Write |\n| `google_chat_delete_message` | Delete a message | Write |\n\n### Reactions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_reactions` | List reactions to a message | Read |\n| `google_chat_create_reaction` | Add an emoji reaction to a message | Write |\n| `google_chat_delete_reaction` | Remove an emoji reaction | Write |\n\n### Attachments & Custom Emoji\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_list_attachments` | List attachments in a space | Read |\n| `google_chat_create_custom_emoji` | Create a custom emoji for the organization | Write |\n\n### Sections\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `google_chat_create_section` | Create a custom section in a space | Write |\n\n## Code Examples\n\n### List spaces\n\n```bash\nclawlink_call_tool --tool \"google_chat_list_spaces\" \\\n --params '{}'\n```\n\n### Send a message to a space\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_message\" \\\n --params '{\n \"parent\": \"spaces/space-id\",\n \"text\": \"Hello team! Just wanted to share an update on the project status.\"\n }'\n```\n\n### Reply in a thread\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_message\" \\\n --params '{\n \"parent\": \"spaces/space-id\",\n \"text\": \"Thanks for the update!\",\n \"thread\": {\n \"thread_key\": \"original-message-id\"\n }\n }'\n```\n\n### Add a reaction to a message\n\n```bash\nclawlink_call_tool --tool \"google_chat_create_reaction\" \\\n --params '{\n \"parent\": \"spaces/space-id/messages/message-id\",\n \"emoji_unicode\": \"👍\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Chat is connected.\n2. Call `clawlink_list_tools --integration google-chat` 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-chat`.\n5. If no Google Chat tools appear, direct the user to https://claw-link.dev/dashboard?add=google-chat.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List spaces → Get space → Show members │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Preview message → User confirms → Execute send │\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 read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes 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- Space names use format `spaces/space-id` in API calls.\n- Message threading uses `thread_key` to reply to existing threads.\n- Custom emojis are only available for Google Workspace accounts and require admin enablement.\n- With user authentication, only plain text messages are supported. Card-based messages require bot authentication.\n- Message size limit is 32,000 bytes.\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-chat`. |\n| Missing connection | Google Chat is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-chat. |\n| `404 Not Found` | Space, message, or member does not exist. Verify the IDs. |\n| `403 Forbidden` | Insufficient permissions or the space requires bot authentication. |\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-chat`.\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 Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)\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- [Slack](https://clawhub.ai/hith3sh/slack) — For alternative team messaging\n- [Gmail](https://clawhub.ai/hith3sh/gmail-email) — For email alongside chat\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-chat-messaging\",\n \"version\": \"0.1.1\",\n \"publishedAt\": 1780839006377\n}\n\nFile v0.1.1:skill-card.md\n\n## Description:
\nWork with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API.
\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 developers use this skill to inspect Google Chat spaces, members, messages, attachments, and threads, and to perform confirmed write actions through a connected Google account.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill uses OAuth-backed access to Google Chat data available to the connected account.
\nMitigation: Connect only the intended Google account and rely on the documented scoped access model before reading spaces, members, messages, or attachments.
\nRisk: Write or destructive Google Chat actions can send messages, create or update spaces, or change memberships.
\nMitigation: Preview and confirm the intended effect with the user before any write, membership change, message deletion, or space deletion.
\n\n\n## Reference(s):
\n- [Google Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)
\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, configuration, text]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Google Chat write operations should be previewed and executed only after explicit user confirmation.]
\n\n## Skill Version(s):
\n0.1.1 (source: server 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, 3308 bytes\n\nFiles: skill-card.md (2039b), SKILL.md (5010b), _meta.json (140b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: google-chat-messaging\ndescription: Work with Google Chat spaces, members, messages, attachments, and threaded conversations - powered by ClawLink.\n---\n\n# Google Chat\n\nWork with Google Chat from chat - manage spaces, members, messages, attachments, and threaded conversations.\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 Chat 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 Chat at [claw-link.dev/dashboard?add=google-chat](https://claw-link.dev/dashboard?add=google-chat)\n7. When the user confirms Google Chat is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `google-chat` 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 Chat\n\nTell the user to open https://claw-link.dev/dashboard?add=google-chat and connect Google Chat there. The page opens the add-connection panel filtered to Google Chat. ClawLink's hosted page runs the provider connection flow. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `google-chat`.\n\n## Using Google Chat 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 Chat is connected.\n2. Call `clawlink_list_tools` with integration `google-chat`.\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-chat`.\n5. If no Google Chat tools appear, direct the user to https://claw-link.dev/dashboard?add=google-chat.\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 read, list, search, and get operations before writes.\n4. For writes 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 Chat tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- List spaces and members\n- Read or inspect messages where permitted\n- Send messages after confirmation\n- Create or manage spaces when available\n- Work with threads and attachments\n\n## Rules\n\n- Always use ClawLink tools for Google Chat. Do not ask the user for separate Google Chat 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 destructive, external-facing, or bulk write actions.\n- If Google Chat is not connected, direct the user to https://claw-link.dev/dashboard?add=google-chat.\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 Chat API: https://developers.google.com/workspace/chat/api/reference/rest\n\nFile v0.1.0:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"google-chat-messaging\",\n \"version\": \"0.1.0\",\n \"publishedAt\": 1778953786488\n}\n\nFile v0.1.0:skill-card.md\n\n## Description:
\nWork with Google Chat spaces, members, messages, attachments, and threaded conversations - 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:
\nDevelopers and external users use this skill to connect an agent to Google Chat through ClawLink, discover available Google Chat tools, and manage spaces, members, messages, attachments, and threads with confirmation before write actions.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The agent may use ClawLink with Google Chat permissions approved by the user.
\nMitigation: Install only when the user trusts ClawLink with the approved Google Chat permissions.
\nRisk: Message-send, space-management, or bulk actions can affect external Google Chat content.
\nMitigation: Preview and confirm write, destructive, external-facing, or bulk actions before execution.
\n\n\n## Reference(s):
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n- [Google Chat API](https://developers.google.com/workspace/chat/api/reference/rest)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Shell commands, Configuration instructions, API Calls]
\n**Output Format:** [Markdown guidance with inline shell commands and tool-call instructions]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires live ClawLink tool discovery; external-facing, destructive, and bulk write actions require user confirmation.]
\n\n## Skill Version(s):
\n0.1.0 (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.
","readmeExcerpt":"Skill: Google Chat Owner: hith3sh Summary: Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spac... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:09:27.832Z | 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 Chat API │\n│ (User Chat) │ │ (OAuth) │ │ (REST) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Google Chat │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Chat │\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":"# List spaces the user is member of\nclawlink_call_tool --tool \"google_chat_list_spaces\" --params '{}'\n\n# List members in a space\nclawlink_call_tool --tool \"google_chat_list_members\" --params '{\"parent\": \"spaces/space-id\"}'\n\n# Send a message to a space\nclawlink_call_tool --tool \"google_chat_create_message\" --params '{\"parent\": \"spaces/space-id\", \"text\": \"Hello from OpenClaw!\"}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration google-chat"},{"language":"bash","snippet":"clawlink_call_tool --tool \"google_chat_list_spaces\" \\\n --params '{}'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: google-chat-messaging\ndescription: Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spaces and members, read or inspect messages, send messages after confirmation, create or manage spaces, or work with threads and attachments in Google Chat.\n---\n\n# Google Chat\n\n\n\nAccess Google Chat via the Google Chat API with OAuth authentication. Manage spaces, members, messages, attachments, and threaded conversations.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-chat-messaging) for hosted connection flows and credentials so you do not need to configure Google Chat API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Chat |\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 Chat |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Google Chat API │\n│ (User Chat) │ │ (OAuth) │ │ (REST) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Google Chat │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Google │\n │ File │ │ Auth │ │ Chat │\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 Chat again.\"\n\n## Quick Start\n\n```bash\n# List spaces the user is member of\nclawlink_call_tool --tool \"google_chat_list_spaces\" --params '{}'\n\n# List membe"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"google-chat-messaging\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1780988967832\n}"},{"path":"skill-card.md","content":"## Description:\n\nWork with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API.\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\nDevelopers and OpenClaw users use this skill to connect Google Chat through ClawLink, inspect spaces, members, messages, reactions, attachments, and threads, and perform confirmed write actions such as sending messages or managing spaces.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Connecting Google Chat through ClawLink gives the integration access to Chat data available to the connected Google account.\n\nMitigation: Connect only accounts whose Chat access is appropriate for this integration, and verify the Google Chat connection before use.\n\nRisk: Write-capable tools can send or modify messages, spaces, memberships, reactions, sections, or custom emoji.\n\nMitigation: Preview write or destructive actions and execute them only after explicit user confirmation.\n\nRisk: Using an unpinned plugin release can make the installed behavior harder to review over time.\n\nMitigation: Prefer a pinned or verified ClawLink plugin release when available.\n\n## Reference(s):\n\n- [Google Chat API Reference](https://developers.google.com/workspace/chat/api/reference/rest)\n- [Google Chat API Overview](https://developers.google.com/workspace/chat/api/guides/overview)\n- [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-chat-messaging)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with inline shell commands and JSON tool parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires a connected ClawLink Google Chat integration; write and destructive actions require explicit user confirmation; Google Chat messages are limited to 32000 bytes.]\n\n## Skill Version(s):\n\n1.0.6 (source: server evidence release.version)\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":"Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spac... Skill: Google Chat Owner: hith3sh Summary: Work with Google Chat spaces, members, messages, attachments, and threaded conversations via the Google Chat API. Use this skill when users want to list spac... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:09:27.832Z | 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":1080,"uniquenessScore":49,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T11:28:53.422Z","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-09T11:28:53.422Z","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-09T22:08:28.177Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}