Zenkraft

v1.0.2

Zenkraft integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zenkraft data.

0· 53·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Zenkraft integration) matches the runtime instructions: all actions are performed via the Membrane CLI and/or Membrane's proxy to Zenkraft. Nothing requested (no env vars, no config paths) is unrelated to the stated purpose.
Instruction Scope
SKILL.md stays on-topic: it tells the user to install the Membrane CLI, authenticate via browser, create a connection, list and run actions, or proxy raw API calls through Membrane. It does not instruct the agent to read unrelated files or exfiltrate local secrets. It does allow sending arbitrary requests to Zenkraft via the Membrane proxy (expected for this integration).
Install Mechanism
There is no formal install spec in the registry; the SKILL.md recommends installing @membranehq/cli globally with npm. This is a common, reasonable instruction for a CLI-based skill, but installing a global npm package requires trusting that package and its publisher.
Credentials
The skill requests no environment variables or credentials and explicitly advises against asking users for API keys. Authentication is delegated to Membrane's hosted flow (browser login), which is proportional to the described integration—but it does mean trusting Membrane to hold and refresh connector credentials server-side.
Persistence & Privilege
always:false and no config paths or persistent modifications are requested. The skill does not request elevated or permanent platform privileges.
Assessment
This skill is instruction-only and coherent, but before using it consider: (1) installing the Membrane CLI (@membranehq/cli) requires trusting that npm package and its publisher—verify the package and its homepage; (2) Membrane will hold and proxy connector credentials server-side, so you must trust Membrane (getmembrane.com) to manage auth for Zenkraft; (3) the skill enables sending arbitrary proxied requests to Zenkraft—only use it with accounts/data you intend to share; (4) if you prefer tighter control, avoid giving the agent autonomous invocation or require explicit user approval before running CLI commands that interact with live systems.

Like a lobster shell, security has layers — review code before you run it.

latestvk977g2vkdj8e0ntd4p6zsmv55d842038

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments