Google Meet
v1.0.2Google Meet integration. Manage Meetings, Recordings. Use when the user wants to interact with Google Meet data.
⭐ 0· 25·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Google Meet management) match the runtime instructions: all actions are performed via the Membrane CLI and a Membrane account. Required capabilities (network access and a Membrane account) are consistent with the stated purpose.
Instruction Scope
Instructions only tell the agent to install and use the Membrane CLI, create connections, run actions, or proxy custom requests. There is no instruction to read unrelated local files or request unrelated credentials. Important privacy note: the skill explicitly routes API calls and requests through Membrane's proxy, meaning Meet data (including transcripts/recordings) will be transmitted to and processed by Membrane.
Install Mechanism
This is an instruction-only skill (no install spec) but directs users to run `npm install -g @membranehq/cli`. Installing a global npm package is a standard but non-trivial action (writes binaries to disk and grants code execution). The source is a public npm package — expected for this integration but worth verifying the package and publisher before installing in sensitive environments.
Credentials
The skill declares no required env vars or secrets. It avoids asking for Google API keys locally and relies on Membrane to manage auth, which is proportionate. The tradeoff is trust in Membrane to store and handle credentials server‑side.
Persistence & Privilege
The skill is not always-enabled and is user-invocable; it does not request elevated platform privileges or make cross-skill/system modifications in the instructions. No persistent skill-level privileges are requested in the metadata.
Assessment
This skill is coherent: it delegates all Google Meet work to the Membrane CLI/proxy rather than asking for local API keys. Before installing or using it, consider: 1) Privacy/trust — Membrane will see the API calls and any meeting data (transcripts, recordings, participant info). Ensure your organization is comfortable sending this data to Membrane and review their privacy/terms. 2) Verify the CLI package (@membranehq/cli) and publisher on npm/GitHub to avoid supply-chain risks. 3) Installing `npm install -g` writes a global binary — avoid on locked-down hosts or use a scoped environment (container/VM). 4) Check OAuth scopes and permissions when connecting Google accounts and prefer least-privilege / service accounts or dedicated accounts for integrations. 5) If you need strict data residency or compliance, this proxying approach may be unsuitable. If you want, I can list the exact commands the skill will run and wording you can show an admin to evaluate risk/policy compliance.Like a lobster shell, security has layers — review code before you run it.
latestvk974qbh5627dwerf2vyj0nmzjx842f4c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.