eonik creative audit

Identifies creative fatigue, budget leaks, and scaling opportunities by running the eonik creative audit engine.

Security Scan

The skill's code, instructions, and requested credential (EONIK_API_KEY) are consistent with its stated purpose (running an external eonik audit API and presenting results); there are no obvious mismatches or hidden exfiltration mechanisms in the provided files.

Purpose & Capability

Name/description match behavior: the skill runs a local pipeline which calls the eonik backend (api.eonik.ai) using a single EONIK_API_KEY to produce an audit report. Requiring a single service API key is appropriate for this purpose. The README, SKILL.md, and scripts all align on the advertised functionality.

Instruction Scope

Runtime instructions are limited to checking/creating config.json, invoking the included pipeline (python3 scripts/pipeline.py --config config.json), and reading the generated output file. The scripts only read the config and write an output JSON containing audit findings (ad IDs, spend, thumbnails). There are no instructions to scan unrelated files, read other credentials, or transmit local files to unexpected endpoints beyond the declared api.eonik.ai endpoint.

Install Mechanism

This is an instruction-only skill with included Python scripts (no external install downloads or archive extracts). There is no install spec that fetches arbitrary code at runtime. Dependencies are standard library-only and the repository includes the script files.

Credentials

The skill requests only one credential: EONIK_API_KEY (primaryEnv). That is proportionate to a service that calls a vendor API. One small inconsistency: top-level metadata in the provided registry snapshot said 'required binaries: none', while skill.json lists python3 in 'requirements.bins' — in practice Python is required to run the included scripts. Otherwise no unrelated secrets or extra credentials are requested.

Persistence & Privilege

The skill is not always-enabled (always:false) and uses standard invocation. It suggests using OpenCLAW's cron scheduler to run periodically; scheduling itself is a normal convenience but will create regular scans and outputs, so users should enable scheduling intentionally. The skill does not modify other skills or global config.

Assessment

This skill appears to do what it says: it calls eonik's API with your EONIK_API_KEY and prints/writes the audit report. Before installing or scheduling it: 1) Verify you trust the eonik.ai service and that the endpoint (https://api.eonik.ai) is expected for your account. 2) Treat output/ directory as sensitive — reports include Meta Ad IDs and thumbnails; ensure DLP/permissions prevent accidental sharing. 3) Use a dedicated, scoped API key for this skill and rotate/revoke if you stop using it. 4) Confirm you want daily automated audits before adding the cron job (scheduling increases the blast radius if the key is compromised). 5) Note the minor metadata mismatch: skill.json requires python3 even though the registry snapshot earlier showed none — ensure Python 3.7+ is available on the runner. If you want extra assurance, review or run the scripts in an isolated environment and inspect network traffic to confirm calls go only to api.eonik.ai.

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: Check if config.json exists in the local directory.
2. Request Input (if needed): If config.json is missing, check if they want to run it on their default connected Meta account. Once confirmed, copy config.example.json to config.json (the Meta Account ID can be left blank as it auto-resolves).
3. Execute Pipeline: Once config.json is present and configured, you MUST run the audit pipeline natively by executing the following command in the terminal:

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

4. Display Results: After the script finishes, read the output report (typically output/audit-<date>.json) and provide a concise, formatted summary of the findings to the user. 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-ad-budget-leak
cp config.example.json config.json
# Edit config.json: optionally add your Meta Account ID (or leave blank to auto-resolve)

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": "",
    "evaluation_days": 30
  }
}

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.

2. 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!

3. 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 and 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.

You do NOT need to over-engineer a loop or write your own dispatcher. OpenCLAW has a built-in, native cron scheduler that will automatically run the skill and route the output to your linked channels.

Schedule Daily Audits (e.g., Every morning at 8 AM): To set up continuous automated scanning, use OpenCLAW's native scheduler:

# 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.