Whatsable
v1.0.0WhatsAble integration. Manage data, records, and automate workflows. Use when the user wants to interact with WhatsAble data.
⭐ 0· 29·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill claims to integrate with WhatsAble via Membrane and the SKILL.md consistently instructs the agent/user to use the Membrane CLI, create a connection, run actions, or proxy API calls — all expected for this purpose. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Runtime instructions are specific and limited to installing/using the Membrane CLI, logging in, discovering connectors/actions, running actions, and proxying requests. The instructions do not ask the agent to read unrelated local files, environment variables, or exfiltrate data to third-party endpoints beyond Membrane/WhatsAble.
Install Mechanism
This is an instruction-only skill (no install spec). It tells users to run `npm install -g @membranehq/cli` which is coherent with the described workflow. Note: global npm installs pull code from the npm registry and should be installed only after verifying the package and publisher (the SKILL.md points to membrane resources). The skill itself does not perform any downloads or write files.
Credentials
No environment variables, credentials, or config paths are requested by the skill. The instructions explicitly advise letting Membrane handle credentials rather than asking users for API keys, which is proportionate to the integration.
Persistence & Privilege
The skill is not always-included and may be invoked by the user or autonomously per normal platform defaults. It does not request elevated persistence or modify other skills' configurations.
Assessment
This skill appears internally consistent: it uses the Membrane CLI to access WhatsAble and doesn't ask for local secrets. Before installing or following the SKILL.md steps, verify the Membrane CLI package and publisher (e.g., confirm @membranehq on the npm registry and the official docs at getmembrane.com), and be cautious when performing global npm installs. Expect a browser-based login flow (or headless flow with a one-time code). If you don't want to install third-party CLIs, avoid using the skill; otherwise it is reasonable to proceed.Like a lobster shell, security has layers — review code before you run it.
latestvk973ae5kctr5krygr8vfttcbnx846nbm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.