Cloudcart
v1.0.2CloudCart integration. Manage data, records, and automate workflows. Use when the user wants to interact with CloudCart data.
⭐ 0· 92·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
high confidencePurpose & Capability
The name/description say 'CloudCart integration' and the instructions consistently show how to use the Membrane CLI to connect to CloudCart, list actions, run actions, or proxy API calls. Requiring a Membrane account and network access is coherent with that purpose.
Instruction Scope
Instructions are scoped to installing and using the @membranehq/cli, creating connections, running actions, and proxying requests to CloudCart. The skill explicitly avoids asking for raw API keys and instead relies on browser-based authentication via Membrane. Note: using the proxy means requests and CloudCart data will transit Membrane's infrastructure — this is expected but worth being aware of.
Install Mechanism
There is no automated install spec in the registry (instruction-only). The SKILL.md tells users to run `npm install -g @membranehq/cli`. That is a normal, traceable install from the npm registry but installing global packages runs third-party code on the host — verify the package and its publisher (GitHub repo and npm page) before installing.
Credentials
The skill declares no required environment variables or config paths. It relies on the Membrane CLI/browser auth flow to manage credentials, which is proportional to its stated function. Users should understand that authentication tokens will be managed by Membrane.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. As an instruction-only skill it does not modify other skills or system-wide settings.
Assessment
This skill appears to do what it says: it teaches you to use the Membrane CLI to work with CloudCart. Before proceeding: (1) verify the @membranehq/cli package and its GitHub repo to ensure you're installing the official tool; (2) understand that using the Membrane proxy sends CloudCart requests and data through Membrane's service — only proceed if you trust that provider and their privacy/security posture; (3) prefer running the CLI in a dedicated environment if you are cautious about global npm installs; (4) no environment variables or hidden credentials are requested by the skill itself, but authentication is handled via the Membrane login flow (browser-based). If you want extra assurance, inspect the Membrane CLI source and npm package prior to installation.Like a lobster shell, security has layers — review code before you run it.
latestvk978awbcptwfb0p4mrrarfjbzn84337r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.