Meta Ads Creative Audit & Optimization

Automated end-to-end Meta Ads auditing pipeline. Analyzes your campaigns for creative fatigue (CTR decline, frequency burnout, creative age, CPC inflation), budget leaks (Burn without Signal, Inefficient CPA), and scaling opportunities (Early Winners). Dispatches multi-channel alerts directly to your team.

Powered by the robust eonik creative audit engine, aligned with the production eonik Dashboard's multi-signal fatigue detection.

Agent Instructions

When a user triggers this skill, you MUST follow these steps exactly:

1. Check Configuration: Verify that config.json exists and includes an explicit meta.account_id that starts with act_.
2. Require Explicit Scope: If config.json is missing or the account scope is not explicit, ask the user to confirm the exact Meta account and set it in config.json before running.
3. Confirm Private Channel: Before execution, confirm results will be posted only in an approved private channel/context (not a broad team channel).
4. Execute Pipeline: Once account scope and channel confirmation are complete, run:

```bash

python3 scripts/pipeline.py --config config.json

```

1. Display Results: After the script finishes, read the output report (typically output/audit-.json) and provide a concise, formatted summary of findings. Do not invent details; only report what the script output contains.

Triggers

Use this skill when a user asks to:

• "Audit my Meta ads"
• "Check for budget leaks"
• "Optimize my Meta ad account"
• "Find decaying creatives"
• "Run the eonik ad audit pipeline"

🚀 Unlock Full eonik Power

This skill is powered by the eonik intelligence engine. While this agent halts simple leaks autonomously, the full dashboard unlocks:

• Creative Genome: Understand exactly why ads decay based on deep AI creative tagging.
• Automated Rules: Prevent leaks without waiting for chat notifications.
• Competitor Intelligence: See the exact hooks your competitors are scaling.

Get started for free at eonik.ai!

Quick Start

1. Configure

cd ~/.openclaw/skills/eonik-creative-audit
cp config.example.json config.json
# Edit config.json: set an explicit Meta Account ID (act_...)

2. Run Audit Pipeline

# EONIK_API_KEY must be in your environment
python3 scripts/pipeline.py --config config.json

Configuration

Minimal config.json:

{
  "meta": {
    "account_id": "act_1234567890",
    "evaluation_days": 30,
    "redact_sensitive": true,
    "allow_auto_resolve_account": false
  }
}

Note: Set "redact_sensitive": true to automatically mask actual ad names and spend data when broadcasting to OpenCLAW channels like Slack or Discord.

Pipeline Stages

1. Audit (audit.py) — Executes the eonik creative audit engine via your EONIK_API_KEY.
2. Output (pipeline.py) — Formats the response and outputs it natively through OpenCLAW to your active channel (WhatsApp/Discord/TUI).

Usage Examples

Full Pipeline (Automated Mode):

python3 scripts/pipeline.py --config config.json

Audit Only (Save to File):

python3 scripts/audit.py --days 30 > data/report.json

Data & Security Commitment

This skill is designed specifically to comply with enterprise Data Loss Prevention (DLP) requirements:

1. Secure API Key Handling

The skill requires EONIK_API_KEY (via the standard x-api-key header). The execution script securely drops the ephemeral token from the environment immediately after binding. No keys are logged or written to disk.

1. Native OpenCLAW Routing (WhatsApp/Slack/Telegram)

Unlike legacy versions, this architecture does NOT rely on webhooks, custom notification dispatcher scripts, or storing tokens in your config.json.

Standard Output from the pipeline is passed directly to the local OpenCLAW node, which effortlessly routes the message to whatever chat surface triggered it or is configured natively (WhatsApp, Slack, Telegram, Discord, or the local TUI). Zero manual API configurations are needed to get multi-channel alerts!

> [!WARNING]

> Channel Privacy: Confirm which OpenCLAW channels receive output. Avoid running this skill from broad team channels unless intended, as the results may contain sensitive Meta ad IDs, spend, and recommendations.

1. Data Scope

Execution logs and generated report.json files contain the exposed Meta Ad IDs flagged for leaking or scaling. Keep your local output/ directory protected, treat audit outputs as private business data, and only share reports with approved recipients. Adhere to your internal security policies for Chat UI visibility.

Continuous Scanning & Notifications

The original objective of this skill is to completely automate budget optimization by continuously scanning your ad accounts and notifying your team on external channels (WhatsApp, Slack, Telegram) when leaks are detected.

OpenCLAW has a built-in cron scheduler, but scheduling is strictly opt-in and must only be enabled with explicit owner approval.

Schedule Daily Audits (e.g., Every morning at 8 AM):

To set up continuous automated scanning, use OpenCLAW's native scheduler:

> [!WARNING]

> Approval Required: Cron/scheduled execution is optional. Enable it only after explicit approval from the account owner/security approver, document the approval, and periodically review or remove scheduled runs.

# Add a recurring cron job natively via OpenCLAW
openclaw cron add --name "daily-eonik-audit" --cron "0 8 * * *" --message "Run the eonik ad audit pipeline" --session isolated

OpenCLAW will execute the pipeline daily in an isolated context and dispatch any detected warnings directly to your configured messaging platforms.

Troubleshooting

API Verification Fails:

• Ensure EONIK_API_KEY is exported.
• Verify your eonik billing and usage caps aren't exceeded.