Google Merchant Center
v1.0.2Google Merchant Center integration. Manage Accounts. Use when the user wants to interact with Google Merchant Center data.
⭐ 0· 126·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
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name/description align with the content (it uses Membrane to talk to Google Merchant Center). However the runtime instructions require the @membranehq/cli and a Membrane account (interactive login), but the registry metadata lists no required binaries or primary credential — a minor metadata omission (the CLI and network access are necessary to achieve the stated purpose).
Instruction Scope
SKILL.md stays on-topic: it instructs installing the Membrane CLI, performing an interactive login, creating connections, listing/running actions, and proxying requests to Google Merchant Center. It does not instruct reading unrelated files, harvesting environment variables, or transmitting data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec). The doc tells users to run `npm install -g @membranehq/cli` — a normal approach but it requires installing a third-party global npm package. Users should verify the CLI/package source before installing and be aware of the usual risks of global npm installs.
Credentials
No environment variables or credentials are declared in the registry metadata. The skill expects interactive Membrane login (browser flow) which is proportional to its purpose; it does not ask for unrelated secrets or broad system credentials.
Persistence & Privilege
The skill does not request always:true and does not request elevated or system-wide persistence. Autonomous invocation is allowed (platform default) but there are no additional privileges or self-modifying install steps described.
Assessment
This skill appears to be what it says: a Membrane-backed Google Merchant Center integration. Before installing or running commands: 1) verify the @membranehq/cli package and its GitHub repo (review maintainers, recent commits, and npm publisher) 2) run the CLI and login from a machine you control (the login is an interactive browser flow) and review the OAuth/permission scopes granted, 3) avoid installing global npm packages on sensitive systems — consider using a container or isolated environment, and 4) confirm that Membrane connectors and actions access only the Google Merchant accounts you expect. If you need stricter assurance, ask the skill author for an explicit manifest stating required binaries and network/account requirements.Like a lobster shell, security has layers — review code before you run it.
latestvk971wg7nztbet7qp2cww4f00qh842szb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
