Bigcommerce
v1.0.2BigCommerce integration. Manage Products, Customers, Orders, Carts, Coupons, GiftCertificates and more. Use when the user wants to interact with BigCommerce...
⭐ 0· 34·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 purpose (BigCommerce integration) matches the runtime instructions (use Membrane to connect and proxy to BigCommerce). However, the skill metadata declares no required binaries while the SKILL.md explicitly instructs installing and using the `membrane` CLI; that mismatch is a minor incoherence.
Instruction Scope
SKILL.md confines actions to discovering and running Membrane-provided BigCommerce actions and proxying requests to the BigCommerce API via Membrane. It does not instruct reading unrelated files or environment variables.
Install Mechanism
There is no automated install spec in the registry (instruction-only), but the README instructs running `npm install -g @membranehq/cli`. Installing a global npm CLI is a typical approach but carries the usual risks of running third-party npm code — verify the package and source before installing.
Credentials
The skill declares no required environment variables or credentials. Authentication is delegated to Membrane (interactive browser login), which is appropriate for this integration. Expect the Membrane connection to gain access to BigCommerce store data as part of normal operation; no unrelated credentials are requested.
Persistence & Privilege
The skill is instruction-only, does not request permanent 'always' presence, and does not modify other skills. Agent autonomous invocation is allowed (platform default) — this is normal for skills but increases impact if the skill or its upstream service is compromised.
Assessment
This skill is an instruction-only wrapper that relies on the Membrane CLI to talk to BigCommerce. Before installing or running it: 1) Verify you trust the @membranehq/cli npm package and its publisher (review the npm page and GitHub repo) because `npm install -g` runs third-party code system-wide. 2) Understand that authenticating via Membrane grants Membrane access to your BigCommerce store data — only authorize if you trust that service and the connector workflow. 3) Note the minor metadata mismatch: the skill doesn't list required binaries even though it expects the `membrane` CLI; be prepared to install that CLI. 4) Prefer creating least-privilege connections in BigCommerce and review the actions the connector requests when you authorize it. 5) If you need stricter control, avoid installing global CLIs on shared hosts or test this first in an isolated environment.Like a lobster shell, security has layers — review code before you run it.
latestvk97ex2z4hfr2svx8r7ek9j06kh842m7g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
