Ads Manager Claw
v1.0.3Manage paid advertising campaigns across Meta (Facebook & Instagram), Google Ads, X, and Snapchat — optimized for Indian businesses. This skill analyzes perf...
⭐ 1· 203·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the content: the skill provides rules, reporting, and API call templates for Meta, Google Ads, X, and Snapchat. The references explain the exact credentials each platform requires (access tokens, OAuth refresh tokens, developer token, OAuth1 creds), which are appropriate for the stated purpose.
Instruction Scope
The SKILL.md stays within ad-management scope and includes explicit decision rules, reporting formats, and a 'confirm with user before ANY action' rule. However it instructs the agent to ask users to paste account IDs and access tokens into the conversation and claims these will be 'only used for this session' — that is vague and gives the agent discretion about use and storage. Also Google Ads requires a multi-part OAuth/developer-token flow (covered in references) but the top-level instruction simplifies credential collection to 'Ad Account ID and access token', which could confuse users and lead to sharing more-sensitive credentials than necessary.
Install Mechanism
Instruction-only skill with no install spec and no bundled code or downloads. Nothing is written to disk or installed, which reduces risk.
Credentials
No environment variables or config paths are requested by the skill package itself, which is proportionate. The runtime instructions do solicit high-privilege credentials (access tokens, OAuth refresh tokens, developer tokens, API secrets) — these are necessary for managing ads but are sensitive. The skill does not document storage/retention practices or recommend least-privilege tokens, which is a risk to consider.
Persistence & Privilege
The skill is not always-enabled and does not request special platform privileges. It contains no install-time behavior that would grant persistent system-level access or modify other skills. Autonomous invocation is allowed (platform default), but not combined with other red flags here.
Assessment
This skill appears to do what it says, but it asks you to provide sensitive ad-platform credentials in-session. Before using it: (1) Prefer providing read-only or limited-scope tokens where possible (diagnosis only) and avoid sharing client secrets or refresh tokens unless absolutely required. (2) Use platform OAuth flows (not pasting secrets into chat) when available — for Google Ads you typically need a developer token and an OAuth refresh token obtained via an OAuth flow, not just a one-line access token. (3) Confirm every action the assistant proposes before it executes changes (the skill says it will confirm, but don't rely solely on that). (4) Revoke any tokens you shared after the session, and monitor your ad account activity and billing/funding instruments for unexpected changes. (5) If you must share tokens, prefer session-limited tokens and document what the skill will and will not store. If you need, I can draft a short message to paste to the skill asking for only read-only tokens and forbidding storage of credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk972cjhe8j50w3ehg8bk2sm555843bz2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.