Badger Maps
v1.0.2Badger Maps integration. Manage data, records, and automate workflows. Use when the user wants to interact with Badger Maps data.
⭐ 0· 99·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
medium confidencePurpose & Capability
The name/description (Badger Maps integration) align with the instructions, which use Membrane as a proxy to access Badger Maps actions and APIs. Requesting a Membrane account and network access is appropriate for this integration.
Instruction Scope
SKILL.md instructs the agent/operator to install and run the Membrane CLI, perform login flows (including headless flow instructions), list connections/actions, run actions, and proxy arbitrary API requests through Membrane. Those instructions are consistent with the stated purpose but give the agent the ability to run arbitrary proxied requests to Badger Maps via the established connection — expected for a connector but broad in capability.
Install Mechanism
There is no declared install spec in the registry metadata, but SKILL.md instructs running `npm install -g @membranehq/cli`. Installing a global npm package is a standard but non-trivial change to the host; the ad-hoc install instruction is not captured in the registry's declared requirements (metadata lists no required binaries). This is moderate-risk because it's an external package from npm and will be executed if the agent follows the instructions.
Credentials
The skill does not request environment variables or local credentials. It explicitly directs use of Membrane for server-side credential management and advises never to ask users for API keys — this reduces local credential exposure and is proportionate to the integration's needs.
Persistence & Privilege
always is false and the skill is instruction-only with no code or installs declared in metadata. It does not request persistent system-wide privileges or modify other skills. The only persistent side-effect would be installing the Membrane CLI and creating connections in the Membrane service, which is in-scope for this integration.
Assessment
This skill is coherent for connecting to Badger Maps via Membrane, but review before installing or running: SKILL.md asks you to run `npm install -g @membranehq/cli` even though the registry declares no required binaries — installing a global npm package modifies the host and should only be done if you trust the package. The skill will open a browser-based login and can proxy arbitrary requests to Badger Maps once a connection exists; only proceed if you trust the Membrane service and are comfortable creating that connection. Consider running the CLI in an isolated environment (container/VM) or manually installing and testing `@membranehq/cli` first, and verify Membrane’s privacy/security posture and that the connector ID and requests are contacting the expected Badger Maps endpoints.Like a lobster shell, security has layers — review code before you run it.
latestvk971e2raeba85bd35zs43bddf5843wkd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.