Eventzilla
v1.0.2Eventzilla integration. Manage Events, Contacts. Use when the user wants to interact with Eventzilla data.
⭐ 0· 111·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 name/description say 'Eventzilla integration' and the SKILL.md documents using the Membrane CLI to connect to Eventzilla, list actions, run actions, and proxy API requests. Required resources (network access and a Membrane account) match the stated purpose.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, logging in, creating/listing connections, running actions, and proxying requests to Eventzilla. There are no instructions to read unrelated system files, ask for local API keys, or exfiltrate data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec), but it tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a common but privileged action (it writes to the system and can execute package lifecycle scripts). The package namespace (@membranehq) is a standard npm scope — lower risk than arbitrary download URLs — but users should verify the package's authenticity before installing in sensitive environments.
Credentials
The skill declares no required environment variables or credentials. It explicitly advises to let Membrane manage credentials and not to ask users for API keys. The scope of access (act on the user's Eventzilla account via Membrane after the user authenticates) is proportional to the integration's purpose.
Persistence & Privilege
The skill does not request always:true or any special persistent system presence. It is user-invocable and can be invoked autonomously per platform defaults; that is expected and not excessive here. The skill does not instruct modifying other skills or system-wide agent settings.
Assessment
This skill appears to do what it says: it guides you to install and use the @membranehq CLI to connect your Eventzilla account and run actions via Membrane's proxy. Before installing or running it, verify the @membranehq npm package (check the npm page, package owner, and repository), understand that a global npm install can run package scripts and write to system locations, and be aware the CLI will open a browser for authentication and will act on your Eventzilla data once you create a connection. If you are in a locked-down or high-security environment, avoid global npm installs or run the CLI in an isolated container/VM and review Membrane's privacy/permissions for tokens and stored connections.Like a lobster shell, security has layers — review code before you run it.
latestvk9711bbdydmzehyhhyxb8crm3s842w3a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.