Adobe Commerce
v1.0.0Adobe Commerce integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adobe Commerce data.
⭐ 0· 29·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
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (Adobe Commerce integration) match the instructions: all runtime guidance is about using the Membrane CLI to connect to Adobe Commerce and run actions or proxy API requests. The use of Membrane is a reasonable implementation choice for this purpose.
Instruction Scope
Instructions stay within the integration scope (install CLI, login, create connection, list/run actions, proxy requests). They do route API calls and authentication through Membrane's service — meaning request payloads and credentials are handled server-side by Membrane. This is expected for a proxy-based integration but is a privacy/third-party data-flow consideration users should be aware of.
Install Mechanism
There is no formal install spec in the registry (skill is instruction-only), but the SKILL.md tells the user to run npm install -g @membranehq/cli. Installing a global npm package is a normal but non-trivial action (it executes code from npm and writes binaries to PATH); users should trust the package source and review it if concerned.
Credentials
The skill requests no environment variables or credentials and explicitly instructs not to ask users for API keys, relying on Membrane-managed connections. That is proportionate for an integration that delegates auth to a proxy service.
Persistence & Privilege
Skill does not request always:true, does not require system-wide config changes, and contains no instructions to alter other skills or agent settings. Autonomous invocation is allowed (platform default) and is not combined with other red flags.
Assessment
This skill appears to do what it says: it uses Membrane's CLI to connect to Adobe Commerce and run actions. Before installing or using it: 1) Understand that API calls and credential handling will pass through Membrane's servers — review Membrane's privacy/security posture if that matters to you. 2) Installing the CLI uses npm -g (which writes to your PATH and runs code from the npm registry); verify the @membranehq/cli package and its repository if you need higher assurance. 3) The skill does not request local secrets, which is good; follow the documented browser-login flow rather than sharing API keys directly.Like a lobster shell, security has layers — review code before you run it.
latestvk976jxfq3jbxb0mdf5pnyyq2m1848aaa
License
MIT-0
Free to use, modify, and redistribute. No attribution required.