Mapbox
v1.0.2Mapbox integration. Manage Maps. Use when the user wants to interact with Mapbox data.
⭐ 0· 108·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/description (Mapbox integration) match the instructions, which exclusively describe using the Membrane CLI to connect to Mapbox and run actions or proxy requests. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md confines runtime steps to installing/using the Membrane CLI, logging into a Membrane account via browser, creating/using a Mapbox connection, listing/running actions, and optionally proxying API requests. It does not instruct reading unrelated files, harvesting environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no automated installer). It advises installing @membranehq/cli via 'npm install -g', which is a reasonable way to obtain the CLI but carries the usual npm-global risks (package trust, global install privileges). The document also demonstrates safer ad-hoc use via 'npx', which mitigates global install concerns.
Credentials
The skill declares no required environment variables or credentials; it relies on a Membrane account and browser-based auth for the connection flow. That is proportional for a connector that delegates credential management to Membrane.
Persistence & Privilege
No 'always: true' or other elevated persistence flags are present. The skill is user-invocable and may be invoked autonomously by the agent (platform default) but does not request persistent modifications to agent/system configuration or other skills' settings.
Assessment
This skill appears to be what it says: a Mapbox integration that uses Membrane to handle auth and API calls. Before installing or running commands: 1) Verify you trust the Membrane service and the @membranehq/cli package (check the npm page, maintainers, and homepage). 2) Prefer running commands with 'npx' (as shown in the doc) if you want to avoid a global npm install. 3) Expect browser-based login to your Membrane account and that Membrane will manage Mapbox credentials server-side—do not share Mapbox API keys locally. 4) If you need higher assurance, ask the publisher for the canonical repo/package links and verify checksums or package provenance before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97941367n35g7v8wp38vwd5ts842ey5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.