Avada Commerce
v1.0.2AVADA Commerce integration. Manage data, records, and automate workflows. Use when the user wants to interact with AVADA Commerce data.
⭐ 0· 88·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 AVADA Commerce and the SKILL.md exclusively describes using the Membrane CLI and Membrane-managed connections to talk to AVADA — this aligns with the stated purpose. (Minor note: the skill does not declare a required binary in metadata even though it instructs installing/using the membrane CLI.)
Instruction Scope
Instructions stay within the integration scope: install the Membrane CLI, run membrane login, create connections, list/run actions, and proxy requests via Membrane. The guide does not ask the agent to read unrelated files, export unrelated credentials, or perform system-wide scans.
Install Mechanism
This is an instruction-only skill (no install spec). It tells users to run `npm install -g @membranehq/cli` which will install a global npm package. That is a legitimate way to obtain the described CLI, but global npm installs modify the host environment and rely on the npm registry — users should verify the package identity on npm and be comfortable granting that install.
Credentials
No environment variables or credentials are requested by the skill. The SKILL.md explicitly directs authentication through Membrane (browser-based OAuth flow) and advises not to ask users for API keys, which is proportionate for the stated functionality.
Persistence & Privilege
The skill is not always-enabled and does not request elevated privileges or cross-skill configuration changes. Autonomous invocation is permitted (platform default) but that is expected for an integration skill and is not combined with broad credential access.
Assessment
This skill appears coherent and focused on using the Membrane CLI to talk to Avada. Before installing: (1) verify the @membranehq/cli package on npm and that you trust getmembrane.com / the Membrane project; (2) be aware that `npm install -g` will change your global environment — consider using a scoped environment (nvm, container, or `npx`) if you prefer not to install globally; (3) the Membrane flow proxies requests and handles auth server-side, so API calls and data will transit Membrane infrastructure — confirm that fits your privacy/security needs; (4) expect browser-based OAuth for login. If any of these are unacceptable, do not install or run the CLI until you’ve validated the upstream project.Like a lobster shell, security has layers — review code before you run it.
latestvk97be6avnxrxfegzz4k8deadm5843g1n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.