Api To Every Ecommerce Cart And Marketplace

v1.0.2

API to every Ecommerce Cart and Marketplace integration. Manage data, records, and automate workflows. Use when the user wants to interact with API to every...

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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description claim a unified API for ecommerce platforms and all declared requirements (none) and instructions (use Membrane CLI + Membrane account) are consistent with that purpose — no unrelated credentials or tools are requested.
Instruction Scope
SKILL.md instructs only on installing and using the Membrane CLI (login, connect, action list/run, proxy requests). It does not ask the agent to read local files, arbitrary env vars, or exfiltrate data beyond interacting with Membrane as documented.
Install Mechanism
The skill recommends installing the @membranehq/cli npm package globally. Using an npm package is appropriate for a CLI, but global npm installs and third‑party packages carry the usual supply‑chain risks; verify the package source (npm registry, package owner, and repository) before installing.
Credentials
No environment variables, primary credential, or config paths are required by the skill. The instructions explicitly advise against asking users for API keys and rely on Membrane-managed OAuth/connections, which is proportionate for this connector-style skill.
Persistence & Privilege
Skill is instruction-only, has no install spec and does not request persistent 'always' presence or modify other skills or system‑wide settings. Autonomous invocation is allowed but not exceptional here and is standard for skills.
Assessment
This skill tells you to install and use the official Membrane CLI to manage connections to e-commerce platforms — that is coherent. Before installing: (1) verify the CLI package @membranehq/cli on npm and its GitHub repo to ensure it is the official client, (2) be aware that using Membrane means API traffic and credentials are handled by Membrane’s service (so review their privacy/security docs and OAuth scopes during connector setup), (3) avoid pasting secrets into chat and follow the provided browser OAuth flow, and (4) prefer using the official package source rather than random forks or manual downloads to reduce supply‑chain risk.

Like a lobster shell, security has layers — review code before you run it.

latestvk97cq8pv8x4xk5xynvjx35xxwn842718

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments