Google Meet
PassAudited by ClawScan on May 6, 2026.
Overview
The skill is coherent for Google Meet through ClawLink, but it depends on an external plugin and OAuth connection that users should trust and review before use.
This skill appears safe to install if you intend to use ClawLink for Google Meet. Before using it, make sure you trust the ClawLink plugin and service, review the Google OAuth scopes, do not paste raw credentials into chat, and only approve write or bulk meeting actions after reading the preview.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The ClawLink plugin will provide the actual runtime tools, so its trustworthiness matters even though this skill file itself contains no code.
The skill depends on installing an external plugin that is not included in the provided artifact set. The install is user-directed and central to the skill's purpose, so this is a provenance notice rather than a concern.
Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`
Install the plugin only from the expected ClawHub source and review ClawLink's verification/source information if you need higher assurance.
ClawLink may be able to read or act on Google Meet data according to the scopes the user approves.
The skill requires delegated Google Meet account access through OAuth. This is expected for the stated purpose and is disclosed, but it grants account-level authority within the approved scopes.
ClawLink's hosted page runs the hosted OAuth flow — the user signs in with Google and approves the requested access.
Review the Google OAuth consent scopes carefully, connect only the intended Google account, and revoke the connection if it is no longer needed.
Meeting data and authorized actions may pass through ClawLink rather than only between OpenClaw and Google.
A third-party integration hub mediates credential handling and tool execution. The artifact discloses this data boundary and says credentials are sent only to claw-link.dev, but users should still understand that ClawLink is in the trust path.
Powered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials
Use this skill only if you trust ClawLink's handling of credentials and Google Meet data.
If the connected catalog includes write tools, the agent could change meeting-related data after confirmation.
The skill can invoke dynamically discovered Google Meet tools, including possible write actions. The instructions add preview and confirmation safeguards, making this purpose-aligned but still worth user awareness.
For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user. Execute with `clawlink_call_tool`.
Confirm any proposed write, bulk, destructive, or external-facing action only after checking the preview and intended target.