Elorus
v1.0.2Elorus integration. Manage Organizations. Use when the user wants to interact with Elorus data.
⭐ 0· 112·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 skill clearly targets Elorus but relies on the Membrane CLI and a Membrane account (documented in SKILL.md). The registry metadata did not declare the CLI or network/account requirement as a required binary/credential — this is a minor metadata omission but functionally consistent with the described purpose.
Instruction Scope
SKILL.md instructs the agent (and user) to install and use the Membrane CLI, perform browser-based login, create or reuse a connection, run actions, or proxy requests to the Elorus API. Instructions do not ask the agent to read unrelated files, exfiltrate data, or access unrelated credentials.
Install Mechanism
There is no automated install spec in the registry (instruction-only). The documentation requires running `npm install -g @membranehq/cli` (public npm package) — a reasonable and expected step but one the user must perform manually; the skill itself does not download arbitrary URLs or include code.
Credentials
The skill does not request environment variables or unrelated credentials. Authentication is handled interactively by the Membrane CLI (browser flow or headless completion), which is appropriate for this integration.
Persistence & Privilege
The skill is instruction-only, does not request persistent privileges, and is not force-enabled (always:false). It does not modify other skills or system-wide settings.
Assessment
This skill is essentially a how-to for using the Membrane CLI to access Elorus. Before installing or using it: 1) Verify you trust the Membrane project and the @membranehq/cli npm package (check npm and the GitHub repo linked in the SKILL.md). 2) Understand that authorizing a connection will give Membrane access to your Elorus data via the proxy — only authorize accounts you trust and review requested scopes. 3) In shared or CI/headless environments, be cautious about where CLI tokens are stored and how you complete the login flow. 4) Note the registry metadata didn’t list the CLI requirement — that’s a documentation omission, not a functional mismatch. If any of these points are unacceptable, do not install or authorize the connection.Like a lobster shell, security has layers — review code before you run it.
latestvk97668x3t1emw2jckdmbme20q5842rdf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.