Google Cloud
v1.0.0Google Cloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with Google Cloud data.
⭐ 0· 20·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (Google Cloud integration) aligns with the instructions (use the Membrane CLI to create a Google Cloud connector, list/run actions, or proxy raw requests). Relying on a connector-proxy service (Membrane) explains why no GCP credentials or env vars are declared.
Instruction Scope
SKILL.md only instructs installing/running the Membrane CLI, authenticating via the browser, creating/listing connections, running actions, or proxying API calls. It does not instruct reading unrelated local files or asking for unrelated secrets.
Install Mechanism
There is no automated install spec in the registry; the doc tells the user to run `npm install -g @membranehq/cli` or use `npx`. Installing or running packages from npm can execute arbitrary install/runtime scripts—this is a moderate-risk, standard distribution mechanism. Verify the package publisher and prefer npx/sandboxed usage if you want to avoid a global install.
Credentials
The skill declares no required env vars or local credentials and explicitly says Membrane handles auth server-side. That is proportionate for a connector-based design. If you create a connection, the connector will be able to act on whatever GCP resources the user authorizes—so principle of least privilege still applies when authorizing.
Persistence & Privilege
always is false and the skill is user-invocable. The skill can be invoked autonomously by the agent (platform default) but it does not request elevated persistent privileges or modify other skills' configs.
Assessment
Before installing: 1) Verify the @membranehq/cli package and its publisher (npm page, GitHub repo) so you trust the code you're installing or running via npx. 2) Prefer npx (ephemeral execution) if you don't want a global install. 3) When you connect a Google Cloud account through Membrane, only grant the minimal scopes/permissions needed—connectors can perform real actions (create/delete) in your projects. 4) Review each action the skill proposes to run before confirming it (especially write/delete actions). 5) If you have regulatory or privacy concerns, review Membrane's docs/privacy and consider using a dedicated, least-privilege service account or isolated GCP project for testing.Like a lobster shell, security has layers — review code before you run it.
latestvk97evff4f14raz93abnmh2sqd984f90t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.