Google Ads
v1.0.2Google Ads integration. Manage Campaigns, Accounts, Users, Budgets, Reports. Use when the user wants to interact with Google Ads data.
⭐ 0· 226·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 (Google Ads management) matches the instructions: all commands use the Membrane CLI to connect to Google Ads, run actions, and proxy API requests. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions tell the agent/operator to install and use the @membranehq/cli, perform an interactive/ headless login flow, create a Membrane connection to Google Ads, list/run actions, and proxy raw API requests through Membrane. These steps are appropriate for the stated integration, but they give the Membrane service (and any agent-run commands) the ability to make destructive changes (create/remove campaigns, upload conversions) — which is expected for an integration but worth explicit caution.
Install Mechanism
There is no formal install spec in the skill bundle (instruction-only), but the SKILL.md directs users to install a global npm package (npm install -g @membranehq/cli). Installing a CLI from the npm registry is a common pattern; verify the package and upstream repository (homepage/repo provided) before installing on sensitive systems.
Credentials
The skill declares no required environment variables or local credentials and explicitly recommends letting Membrane handle auth server-side. That is proportionate to its purpose, but note that account access/credentials will be stored/managed by Membrane (third party), not locally.
Persistence & Privilege
always is false and the skill is user-invocable (normal). The default ability for the agent to invoke the skill autonomously is allowed by platform defaults; because the skill can perform account-modifying actions, users should consider least-privilege connections and whether they want autonomous invocation enabled in their agent settings.
Assessment
This skill appears to do what it claims: it uses Membrane as a proxy to access Google Ads and does not request unrelated secrets. Before installing/using it:
- Verify the @membranehq/cli package and the repository/homepage (getmembrane.com / the GitHub link) to ensure you trust the third party.
- Understand that Membrane will manage your Google Ads credentials server-side — review their privacy/security docs and where credentials are stored.
- Use least-privilege connections where possible (grant read-only or limited access to accounts you don't want modified). Test on a sandbox/test account if available.
- Be cautious with agent-autonomous invocation: the skill can run actions that modify or delete campaigns; consider requiring manual approval for destructive actions.
- If installing the CLI on shared systems, treat global npm installs as privileged operations and validate the package integrity.Like a lobster shell, security has layers — review code before you run it.
latestvk975xx83v4cb3n8vhww8kfvfq5843615
License
MIT-0
Free to use, modify, and redistribute. No attribution required.