Google Maps
v1.0.2Google Maps integration. Manage Maps. Use when the user wants to interact with Google Maps data.
⭐ 0· 120·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
Name and description claim a Google Maps integration and the SKILL.md consistently instructs use of the Membrane CLI (which brokers Google Maps auth and API calls). No unrelated services, env vars, or binaries are requested.
Instruction Scope
Instructions are concrete: install the Membrane CLI, login via browser/headless flow, create/list connections, list/run actions, or proxy requests via Membrane. The instructions do not ask the agent to read local files, scan arbitrary system paths, or exfiltrate unrelated data.
Install Mechanism
No install spec in the registry; the SKILL.md recommends installing @membranehq/cli via npm -g. Installing a global npm package is a common approach but carries moderate supply-chain risk compared with no install. This is a recommendation for the human operator rather than an automated install step.
Credentials
The skill declares no required env vars or credentials. It relies on a Membrane account and browser-based auth (handled by Membrane), which is proportionate to a Google Maps integration and avoids asking for direct API keys in the skill.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request persistent system privileges or modify other skills/configuration.
Assessment
This skill is instruction-only and delegates auth and API access to Membrane. Before using it: (1) Confirm you trust the Membrane service and @membranehq/cli npm package (check publisher, package integrity, and docs). (2) Understand installing the CLI globally runs third-party code—prefer installing in a contained environment if you are cautious. (3) Be aware that Membrane will hold the Google credentials and proxy requests on your behalf; review their privacy and access controls. (4) If you need stronger assurance, verify the repository/homepage and test CLI calls in an isolated environment before granting broad network or account access.Like a lobster shell, security has layers — review code before you run it.
latestvk97f1scmtysybrmgk9g8ch8rx58432br
License
MIT-0
Free to use, modify, and redistribute. No attribution required.