Wso2
v1.0.2WSO2 integration. Manage data, records, and automate workflows. Use when the user wants to interact with WSO2 data.
⭐ 0· 113·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/description (WSO2 integration) matches the instructions: it consistently instructs using Membrane to connect to WSO2 and run API actions. Relying on Membrane as a proxy is coherent with the stated purpose.
Instruction Scope
SKILL.md stays on-task (install Membrane CLI, login, create connections, list/run actions, or proxy requests). It does not ask to read unrelated files or environment variables, but it does direct traffic through Membrane (external service) which will see proxied requests and any data sent.
Install Mechanism
There is no packaged install spec in the registry (instruction-only). The README instructs users to run `npm install -g @membranehq/cli` (global npm install) or use npx. Installing a third‑party CLI globally is a normal but moderate supply‑chain risk compared with no install; prefer npx or pinned, audited releases if you are cautious.
Credentials
The skill requests no environment variables or local secrets. Instead it relies on a Membrane account and browser-based login; this is proportionate to the functionality but means your WSO2 access is mediated/stored by Membrane—consider data exposure and who controls those credentials.
Persistence & Privilege
The skill is instruction-only, has no always:true, and does not request persistent modifications to agent/system configuration. It does not require elevated agent privileges.
Assessment
This skill is coherent and likely does what it claims, but before installing or using it consider: (1) Membrane is a third‑party service that will proxy and manage authentication for your WSO2 connections—any requests and data you send will transit/possibly be stored by Membrane, so review their security/privacy docs and trustworthiness; (2) prefer running the CLI via npx or a pinned release rather than `npm install -g` to reduce supply‑chain risk; (3) use a least‑privileged/test WSO2 account when first trying this, and inspect what actions the connector exposes before running them; (4) if you need an offline or self‑hosted integration, confirm whether Membrane provides that option; (5) verify the Membrane repository/homepage and license (links are provided in SKILL.md) before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk976z9b82938qt92mgsmdn8w3x842464
License
MIT-0
Free to use, modify, and redistribute. No attribution required.