Logistia Route Planner
v1.0.2Logistia Route Planner integration. Manage Routes, Vehicles, Drivers, Depots, OptimizationProfiles. Use when the user wants to interact with Logistia Route P...
⭐ 0· 95·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 (Logistia Route Planner integration) aligns with the instructions which teach how to use the Membrane CLI to connect, list actions, run actions, and proxy API requests to Logistia. No unrelated env vars, binaries, or config paths are requested.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI and browser-based login flow, creating/looking up connections, running actions, and proxying API requests. It does not instruct the agent to read arbitrary files, exfiltrate env vars, or call unrelated external endpoints.
Install Mechanism
The registry contains no automated install spec (instruction-only). The instructions recommend installing @membranehq/cli from npm (npm install -g). This is a reasonable, common approach but means you must trust the npm package and its publisher; using npx is a lower-friction alternative that avoids a global install.
Credentials
The skill requests no environment variables or primary credentials. It deliberately delegates authentication to Membrane connections, which is proportionate to a connector-style integration. Be aware that Membrane will broker credentials/server-side.
Persistence & Privilege
always:false and default invocation settings are appropriate. The skill does not request permanent platform-wide privileges or modify other skills' configs.
Assessment
This is an instruction-only skill that is internally consistent with its stated purpose, but before proceeding: (1) understand that using it requires installing/running the third-party @membranehq/cli npm package—verify the package and publisher if you have concerns (consider npx to avoid global installs); (2) recognize Membrane acts as a proxy and will handle/authenticate API calls (so sensitive payloads and credentials will transit or be managed by Membrane); and (3) when connecting, use appropriate account permissions and review the connector's scopes. If you need stricter control over sensitive data, review Membrane's privacy/security docs and the CLI source repo before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk974xw23g1ss317gqgq0ft07dx842gbh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.