Commercetools
v1.0.1Commercetools integration. Manage data, records, and automate workflows. Use when the user wants to interact with Commercetools data.
⭐ 0· 53·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
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 skill claims to manage Commercetools data and all runtime instructions show how to do that via the Membrane CLI. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md instructs the agent/user to install and use the @membranehq/cli, run membrane login (browser-based auth or headless flow), create connections, run actions, and proxy requests through Membrane. These steps are within scope for a Commercetools integration, but they imply that Commercetools requests/responses and any data you send will be proxied through Membrane—users should be aware of that data flow.
Install Mechanism
The registry contains no install spec (instruction-only), but the doc recommends installing an npm CLI (npm install -g @membranehq/cli) or using npx. Installing global npm packages modifies the host environment; this is expected for a CLI-based integration but worth noting for environments where installing global binaries is restricted.
Credentials
The skill declares no required env vars or credentials and explicitly says not to ask users for API keys because Membrane manages auth. That is proportional for a proxy/connector-based approach.
Persistence & Privilege
always:false and there are no instructions to modify other skills or system-wide agent settings. The skill does not request elevated or persistent privileges beyond running a CLI the user installs.
Assessment
This skill delegates auth and API calls to the third-party Membrane service and recommends installing the @membranehq/cli. Before installing or using it, verify you trust Membrane (review their privacy/security documentation and the CLI package), prefer npx for ephemeral invocation if you want to avoid a global install, and be aware that Commercetools requests/responses will be proxied through Membrane (so sensitive data will pass that service). If you operate in a restricted or high-compliance environment, test the CLI in an isolated environment and confirm the data handling practices with Membrane and your Commercetools policies.Like a lobster shell, security has layers — review code before you run it.
latestvk97e6whb6zannhnfq325dwhejh84cqzp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.