Watsonx Ai
v1.0.0WatsonX AI integration. Manage data, records, and automate workflows. Use when the user wants to interact with WatsonX AI data.
⭐ 0· 56·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
Skill name/description (WatsonX AI integration) match the instructions: all runtime steps use the Membrane CLI to discover connectors, create connections, list/run actions, or proxy requests to WatsonX. Required capabilities (network access and a Membrane account) are appropriate for this purpose.
Instruction Scope
Instructions stay on-topic (install CLI, login, connect, list/run actions, proxy requests). Important privacy note: Membrane acts as a proxy and will see request/response payloads and manage authentication server-side, so sensitive data and credentials will be handled by Membrane rather than kept locally.
Install Mechanism
No install spec in registry (instruction-only), but SKILL.md directs users to run a global npm install (npm install -g @membranehq/cli). Installing a package from npm is expected for a CLI, but global npm installs have moderate risk—verify the package name, provenance, and repository before installing.
Credentials
The skill requests no environment variables, no local credentials, and no config paths. This is proportionate: authentication is delegated to Membrane, so no local secrets are required. Users should be aware that authentication/state is stored/managed by Membrane (third-party).
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide settings, and is user-invocable only. It does not ask for permanent agent-level privileges.
Assessment
This skill is coherent: it uses the Membrane CLI to access WatsonX and does not request unrelated system access or local secrets. Before installing/using it: (1) verify the npm package (@membranehq/cli) and the linked GitHub repository are legitimate; (2) be aware that Membrane will proxy requests and hold authentication tokens — do not send data you cannot share with that third party; (3) prefer using a low-privilege or test WatsonX account when first trying the integration; and (4) review your organization's policy on installing global npm packages and trusting third-party proxies.Like a lobster shell, security has layers — review code before you run it.
latestvk9700t4f69j3qasc2wq2yxbarh844c0w
License
MIT-0
Free to use, modify, and redistribute. No attribution required.