Equensworldline
v1.0.2EquensWorldline integration. Manage data, records, and automate workflows. Use when the user wants to interact with EquensWorldline data.
⭐ 0· 95·0 current·0 all-time
byVlad Ursul@gora050
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 (EquensWorldline integration) aligns with the instructions which consistently use the Membrane CLI to connect, list actions, run actions, and proxy API requests to EquensWorldline. Requested capabilities (network, Membrane account) are appropriate.
Instruction Scope
SKILL.md only instructs the agent/user to install and use the Membrane CLI, log in via browser, create/list connections, discover actions, run actions, and proxy requests. It does not ask the agent to read unrelated files, request unrelated credentials, or send data to unexpected endpoints. Auth flows are handled by Membrane per the doc.
Install Mechanism
This is an instruction-only skill (no install spec in the registry), but it tells users to install @membranehq/cli from npm (npm install -g or npx). Installing a third-party CLI from npm is expected for this integration but does pull external code onto the host — verify the package and source before installing.
Credentials
No environment variables, config paths, or credentials are declared or requested by the skill. The SKILL.md explicitly advises against asking users for API keys and uses Membrane to manage auth, which is proportionate.
Persistence & Privilege
The skill is not always-enabled and uses the default autonomous-invocation setting. It does not request system-wide persistent changes itself (it instructs the user to install a CLI and to sign in interactively), so requested privileges are minimal and proportional.
Assessment
This skill appears coherent: it directs you to install and use the Membrane CLI to manage EquensWorldline connections and actions, and to authenticate via your browser. Before installing or running anything, verify the @membranehq/cli package (npm page, maintainer, GitHub repo) and confirm you trust Membrane to proxy requests and hold credentials for the EquensWorldline connection. Installing an npm CLI globally will add third-party code to your system — prefer npx or review the package first if you want to avoid global installs. Finally, when authenticating, follow the official Membrane login flow in your browser and review any commands/JSON you run so you only grant the minimum access needed.Like a lobster shell, security has layers — review code before you run it.
latestvk97bk32hdz8zgpmj269b80112s843gap
License
MIT-0
Free to use, modify, and redistribute. No attribution required.