Whatsapp By Online Live Support

v1.0.2

WhatsApp by Online Live Support integration. Manage data, records, and automate workflows. Use when the user wants to interact with WhatsApp by Online Live S...

0· 98·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
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The SKILL.md describes a WhatsApp Business integration implemented via the Membrane CLI. All described actions (connectors, actions, proxy requests) map to the CLI usage shown; no unrelated services, binaries, or credentials are requested.
Instruction Scope
Instructions are focused on installing and using the @membranehq/cli, logging in via browser, creating connections, listing actions, running actions, and proxying requests. They do not instruct the agent to read unrelated files, exfiltrate data, or access system paths beyond running the CLI and using the browser-based auth flow.
Install Mechanism
This is an instruction-only skill (no install spec), but it tells users to install @membranehq/cli via npm (global install or npx). Installing a third-party CLI from the public npm registry is a normal step for this integration but carries the usual npm-package trust considerations (verify package author, version, and integrity).
Credentials
The skill declares no required environment variables or local credentials and explicitly recommends letting Membrane handle credentials server-side. That is proportionate to a connector/CLI-based integration.
Persistence & Privilege
The skill does not request always:true or any system-level persistence. It is user-invocable and can be called autonomously per platform defaults; that default autonomous invocation is expected and not by itself concerning here.
Assessment
This skill appears coherent, but before installing or running the CLI: (1) confirm the @membranehq/cli package and getmembrane.com are the official vendor; (2) prefer using npx (or pin a specific CLI version) instead of an unrestricted global npm install to reduce supply-chain risk; (3) complete the browser-based OAuth flow rather than pasting secrets into chat; (4) review the Membrane privacy/security documentation to understand what data is proxied through their servers; and (5) if you need higher assurance, inspect the CLI's source code or install it in an isolated environment first.

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

latestvk9752v9sp2gx0z379q3eytv9cx843cdk

License

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

Comments