Evenium
v1.0.2Evenium integration. Manage Events, Users, Roles. Use when the user wants to interact with Evenium data.
⭐ 0· 116·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
high confidencePurpose & Capability
The skill's name and description are an Evenium integration and all instructions use the Membrane CLI to discover connectors, create connections, run actions, or proxy requests to the Evenium API. Requiring network access and a Membrane account is coherent with that purpose.
Instruction Scope
SKILL.md confines runtime actions to using the membrane CLI (login, connection management, action listing/running, and proxying API calls). It does not instruct reading unrelated files, environment variables, or sending data to unexpected endpoints outside of Membrane/Evenium.
Install Mechanism
There is no embedded install spec (instruction-only). The doc advises installing @membranehq/cli via npm -g, which is reasonable for a CLI-based integration but means the user must trust the npm package and perform a global install; the skill does not pin a specific version.
Credentials
The skill declares no required environment variables or secrets. Authentication is delegated to the Membrane CLI (browser login or headless flow); credentials are handled by Membrane rather than the skill itself, which is proportionate to the stated functionality.
Persistence & Privilege
The skill is not always-on and is user-invocable; it does not request elevated platform privileges, modify other skills, or require persistent platform-wide configuration. Autonomous invocation is permitted (platform default) but the skill's actions remain confined to the Membrane/Evenium integration flow.
Assessment
This skill is instruction-only and uses the Membrane CLI to talk to Evenium. Before installing or following the instructions: 1) Verify the @membranehq/cli npm package (publisher, versions, and release notes) before doing a global npm install; 2) Understand that authentication is handled by the Membrane CLI — it will store tokens/credentials locally and will proxy API calls to Evenium, so anyone with access to that CLI identity can act on your Evenium data; 3) Use the headless flow if you need to avoid opening a browser on the agent host, and avoid pasting sensitive credentials into untrusted UIs; 4) If you need higher assurance, inspect the Membrane CLI source and Membrane's privacy/security docs, or run the CLI in a controlled environment (container) rather than installing it globally.Like a lobster shell, security has layers — review code before you run it.
latestvk97ehztchstxr1hb039wcmety5842wct
License
MIT-0
Free to use, modify, and redistribute. No attribution required.