Ad Ops & Cross-Channel Advertising Agent
v1.1.0Manages and optimizes cross-channel ad campaigns autonomously with planning, auditing, budget allocation, and performance reporting across major platforms.
⭐ 0· 652·2 current·4 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The name and description promise autonomous management across Google Ads, Meta, LinkedIn, TikTok, and programmatic. However, the skill is instruction-only and does not request any platform credentials, API keys, or binaries, nor does it provide concrete integration steps (API calls, OAuth flows, or connectors). That mismatch suggests the skill is a playbook/templates bundle rather than an actual autonomous integrator, or that crucial integration pieces are missing or externalized elsewhere.
Instruction Scope
SKILL.md contains frameworks, audit checklists, optimization rules, and reporting templates — all benign on their face — but it also makes broad claims about turning an agent into an autonomous ad ops manager 'without touching a dashboard' while giving no concrete runtime instructions for executing changes on ad platforms. The prose is high-level and open-ended, which grants an agent broad discretion (e.g., 'rebalance weekly') without specifying safe boundaries or required credentials. This vagueness is a scope concern because it leaves unanswered how the agent would act and what data it would access.
Install Mechanism
There is no install spec and no code files. From an install point of view this is low-risk: nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. This is proportionate to the actual content (playbooks/templates). However, it contrasts with the described capability (platform integrations), which would normally require credentials — the absence of requested credentials is a notable mismatch but not itself an overreach.
Persistence & Privilege
Flags show defaults: not always-on, user-invocable, and model invocation enabled. There is no indication the skill requests persistent system presence or manipulates other skills or system-wide settings.
What to consider before installing
This skill looks like a detailed ad-ops playbook and reporting template, not an actual autonomous integrator. Before installing or granting any access: (1) Ask the publisher how the agent will connect to ad platforms — request exact integration steps (OAuth flows, API endpoints, SDKs) and a list of required environment variables. (2) Do not provide platform credentials or tokens until you verify where and how they'll be used and stored. (3) If the agent will perform changes, require least-privilege credentials (scoped tokens) and test in a sandbox account. (4) Verify the source — the registry metadata lacks a homepage; prefer skills from known maintainers or with published code. (5) Be cautious of the external paid links in the README; they are marketing for paid context packs and don't change the skill's runtime behavior. If the publisher provides concrete integration code or an install spec, re-evaluate for any network endpoints, downloads, or requested secrets; that information would materially change this assessment.Like a lobster shell, security has layers — review code before you run it.
ad-opsvk975kerd7dhbxvxzes0tfghqe981eggzadvertisingvk975kerd7dhbxvxzes0tfghqe981eggzaivk97cj0t6sva86q1pnshhnt0prx81m2y8businessvk97cj0t6sva86q1pnshhnt0prx81m2y8cross-channelvk975kerd7dhbxvxzes0tfghqe981eggzgoogle-adsvk975kerd7dhbxvxzes0tfghqe981eggzlatestvk97cj0t6sva86q1pnshhnt0prx81m2y8linkedinvk975kerd7dhbxvxzes0tfghqe981eggzmarketingvk975kerd7dhbxvxzes0tfghqe981eggzmeta-adsvk975kerd7dhbxvxzes0tfghqe981eggzppcvk975kerd7dhbxvxzes0tfghqe981eggz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.