Route4Me

v1.0.2

Route4Me integration. Manage Users, Addresses, Routes, Territories, Geofences, Contacts. Use when the user wants to interact with Route4Me data.

0· 124·1 current·1 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description state a Route4Me integration and the SKILL.md consistently instructs use of the Membrane CLI as a proxy to Route4Me. Required resources (network access, Membrane account, CLI) align with that purpose.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, logging in, creating/listing connections, running actions, and proxying requests to the Route4Me API. The instructions do not ask the agent to read unrelated files, environment variables, or system paths.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the SKILL.md tells users to run `npm install -g @membranehq/cli`. Global npm installs are common but carry the usual trust risk — you should trust the @membranehq/cli package before installing globally.
Credentials
The skill declares no required env vars or credentials; it relies on browser-based authentication via Membrane. That is proportionate for a connector that uses an external proxy service for auth and credential refresh.
Persistence & Privilege
The skill does not request always-on presence and uses normal autonomous invocation defaults. It doesn't modify other skills or system-wide settings in the instructions.
Assessment
This skill delegates Route4Me access to the Membrane CLI. Before installing: (1) confirm you trust the @membranehq/cli package (review its npm page or source), since the SKILL.md asks you to install it globally; (2) understand that authenticating via the CLI/browser gives Membrane the ability to act on your Route4Me account (it will proxy API requests and refresh credentials); (3) run the CLI in a controlled environment (not on a machine holding unrelated secrets) if you have sensitive accounts; and (4) if you need stricter control, inspect the Membrane CLI source or use limited-scope API credentials on a test account first. The skill itself is coherent with its stated purpose.

Like a lobster shell, security has layers — review code before you run it.

latestvk97b146n9yar7d1vn08cj7d5r1843svz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments