Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Google Ads CLI
v1.0.0Google Ads data analysis and reporting via google-ads-open-cli. Use when the user wants to check Google Ads performance, pull campaign/ad group/keyword stats...
⭐ 0· 51·0 current·0 all-time
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
Suspicious
medium confidencePurpose & Capability
The SKILL.md describes a read-only CLI for Google Ads and the documented requirements (OAuth2 access token + developer token, optional login-customer-id) are appropriate for that purpose. However, the registry metadata declares no required environment variables or primary credential even though the runtime instructions explicitly require sensitive credentials — that omission is an inconsistency.
Instruction Scope
Instructions are scoped to running the google-ads-open-cli commands, listing accounts, pulling stats, and running GAQL queries. The only filesystem reference is an auto-detected credentials file at ~/.config/google-ads-open-cli/credentials.json, which is consistent with CLI credential storage. The GAQL 'query' command allows arbitrary API queries (expected for an escape-hatch) but also means the tool can retrieve any account data the tokens allow.
Install Mechanism
There is no registry install spec (the skill is instruction-only). SKILL.md recommends installing 'npm install -g google-ads-open-cli' from the public npm registry. Installing an unverified npm package globally can execute arbitrary code; the registry provides no homepage or source link to verify the package origin, which increases risk.
Credentials
The CLI requires sensitive credentials (OAuth2 access token and developer token, plus optional login-customer-id). The skill metadata does not list these required env vars or a primary credential, creating a transparency gap. These tokens grant access to account data and should be treated as high-sensitivity secrets; the SKILL.md also suggests a local credentials file which, if compromised, would expose account access.
Persistence & Privilege
The skill is not set to always:true and is user-invocable only. There is no indication it modifies other skills or system-wide settings. Autonomous invocation is allowed but is the platform default and not elevated here.
What to consider before installing
This skill appears to correctly describe a Google Ads reporting CLI, but there are two things to check before installing or using it: (1) verify where the 'google-ads-open-cli' npm package comes from — the SKILL.md suggests installing from npm but the skill package provides no homepage or source link. Inspect the npm package (or its GitHub repo) before installing, and avoid global installs until you confirm its provenance. (2) The CLI requires sensitive credentials (OAuth2 access token and developer token). Do not reuse high-privilege tokens; use least-privilege tokens or read-only credentials and store them securely. If you must use a credentials file (~/.config/google-ads-open-cli/credentials.json), ensure filesystem permissions restrict access. Because the registry metadata omitted the required env vars, ask the publisher to clarify credential handling and the package source; if you cannot verify the package origin, run it in a sandbox or avoid installing.Like a lobster shell, security has layers — review code before you run it.
latestvk9771yagnez13tva7bgrkzezj184c5k3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.