Wati
v1.0.0WATI integration. Manage data, records, and automate workflows. Use when the user wants to interact with WATI 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
OpenClaw
Benign
high confidencePurpose & Capability
The README describes a WATI integration and all runtime instructions revolve around using the Membrane CLI to discover connectors, create a connection, run actions, and proxy requests to WATI. No unrelated credentials, system paths, or binaries are requested.
Instruction Scope
Instructions stay within the integration scope (install CLI, authenticate via browser, run actions, proxy requests). The CLI's proxy feature allows arbitrary requests to the WATI API through Membrane, which is expected for an integration but means the agent (when authorized) can issue arbitrary API calls on the connected account — review connection permissions and intended actions before granting access.
Install Mechanism
There is no packaged install spec in the registry entry, but the SKILL.md instructs installing @membranehq/cli via npm (global or npx). Installing a third-party npm CLI is a standard approach for this purpose but carries the usual trust considerations for npm packages and global installs.
Credentials
The skill does not request environment variables, local config paths, or secrets. It relies on Membrane-managed auth (browser login) rather than asking for API keys, which is proportionate to the stated purpose.
Persistence & Privilege
The skill is not always-on and is user-invocable. It does not request persistent agent-wide privileges or modify other skills' configs. Autonomous invocation remains allowed by default, which is normal for skills and not flagged here.
Assessment
This skill is coherent: it uses the Membrane CLI to manage a WATI connection and proxy API calls. Before installing, verify you trust the @membranehq/cli npm package and the Membrane service (homepage: https://getmembrane.com). Be aware that authenticating a connection grants Membrane (and anything using that connection) the ability to call WATI APIs on your behalf — grant only the minimum access required, review which WhatsApp numbers and actions the connection can access, and avoid running untrusted or broad 'proxy' requests. If you operate in a sensitive environment, consider installing the CLI in a contained environment and inspect the package source (repository link in SKILL.md) before use.Like a lobster shell, security has layers — review code before you run it.
latestvk97d3v4whxr2hpahstvreybbdh84d16a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.