Zulip

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

Before installing or running this skill: (1) understand that it routes Zulip access through a third‑party service (Membrane) — review Membrane's privacy, security, and data retention policies and only proceed if you trust them; (2) the SKILL.md requires npm/node (global install or npx) even though the registry metadata does not list required binaries — installing global npm packages can execute code from the npm registry, so vet the package (@membranehq/cli) and prefer running in a sandbox; (3) the skill intentionally avoids asking for raw API keys, but that means Membrane will hold/mediate credentials — ensure that level of delegation is acceptable; (4) ask the publisher for clarification or updated metadata listing required binaries and a canonical Membrane project homepage/repository if you want higher assurance. If you cannot trust or verify Membrane, consider integrating directly with Zulip using your own API tokens instead.

Type: OpenClaw Skill Name: zulip-integration Version: 1.0.3 The skill acts as a wrapper for the Membrane platform, requiring the installation of a global NPM package (@membranehq/cli) and delegating all Zulip interactions, including authentication and API execution, to a third-party service (getmembrane.com). While these actions are aligned with the stated purpose of the integration, the requirement for global system modifications and the redirection of all sensitive communication and credential management through an external proxy represent significant security trade-offs and a broadened attack surface. Additionally, the 'membrane action create' feature allows for dynamic remote code generation, which is a high-risk capability.