Zenler
v1.0.0Zenler integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zenler data.
⭐ 0· 33·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 claims to integrate with Zenler and all runtime instructions use the Membrane CLI / Membrane proxy to access Zenler APIs, which is consistent with the stated purpose.
Instruction Scope
SKILL.md limits actions to installing/using the Membrane CLI, creating a connection, listing actions, running actions, and proxying requests to the Zenler API. It does not instruct reading unrelated system files or requesting unrelated credentials.
Install Mechanism
The skill is instruction-only (no install spec in the registry), but the README instructs installing @membranehq/cli globally via npm (npm install -g). This is a reasonable mechanism for a CLI-based integration but the registry metadata did not list the Membrane CLI or network access as requirements — a minor inconsistency to be aware of.
Credentials
No environment variables or credentials are declared; instead the skill relies on interactive Membrane login and a Membrane account/connection to Zenler. That model avoids asking for raw API keys locally, but it does require trusting Membrane (getmembrane.com) to store/manage Zenler credentials.
Persistence & Privilege
The skill does not request always:true and does not ask to modify other skills or global agent settings. Agent autonomous invocation is allowed (platform default) but not elevated beyond normal.
Assessment
This skill looks coherent: it uses the Membrane CLI to talk to Zenler and does not ask for unrelated secrets. Before installing, verify you trust the Membrane vendor (getmembrane.com/@membranehq), since your Zenler connection and credentials will be managed via Membrane's service. Note the SKILL.md instructs running npm install -g @membranehq/cli (global npm install) and performing a browser login — if you prefer to avoid global installs, run the CLI via npx or inside a controlled environment (container/VM). Also confirm the connector permissions shown during the Membrane browser auth match what you expect (access to Zenler records, etc.). The only minor inconsistency is that the registry metadata did not list the CLI/network requirement — that's an authoring omission, not necessarily malicious.Like a lobster shell, security has layers — review code before you run it.
latestvk978s0b6fkh4es5jxbf80gdkxs847ms0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.