Livechat
v1.0.2LiveChat integration. Manage Chats, Reports. Use when the user wants to interact with LiveChat data.
⭐ 0· 107·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's name and description (LiveChat integration) align with its instructions: all actions use the Membrane CLI to connect to LiveChat and run actions or proxy API requests. Required tools and auth flows are appropriate for a connector-style integration.
Instruction Scope
SKILL.md instructs the agent/user to install and use the Membrane CLI, create connections, list actions, run actions, and proxy requests. This stays within the LiveChat integration scope, but proxying and action runs will transmit chat content and API requests through Membrane's servers — the document does not explicitly warn about this data-flow/third-party handling.
Install Mechanism
No install spec in the registry (instruction-only), but the README tells users to run `npm install -g @membranehq/cli` and to use npx. Installing a third-party global npm CLI is a standard approach but does require trusting the package source. There is no download-from-arbitrary-URL or extract step in the skill itself.
Credentials
The skill declares no environment variables, config paths, or credentials; it relies on Membrane's hosted auth flows. That is proportionate to the stated functionality. There are no unexplained credential requests in the instructions.
Persistence & Privilege
The skill is instruction-only, has always:false, and does not request persistent system privileges or modify other skills. Autonomous invocation is allowed by default but not combined with other concerning privileges.
Assessment
This skill is coherent: it uses the Membrane CLI to access LiveChat and does not ask for local API keys. Before installing or running it, consider: (1) Installing @membranehq/cli globally requires trusting that npm package—review its npm and GitHub pages and verify the publisher. (2) All proxied requests and chat data will flow through Membrane's servers—confirm that is acceptable for your privacy/compliance needs. (3) Use an isolated environment if you prefer (e.g., container, VM) before trusting it in production. (4) Follow your organization's policy about third-party CLIs and service accounts, and verify the Membrane account you log into is the correct tenant.Like a lobster shell, security has layers — review code before you run it.
latestvk97fxgcexjqm1xg92rs4f9wrx1842np6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.