ClawHub

Meta Ads Weekly Performance

v1.1.0

[Didoo AI] Generates a structured weekly performance report for Meta Ads accounts. Use at the end of each week to review performance, explain changes, and id...

⭐ 0· 116·0 current·0 all-time
by@elias-didoo

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for elias-didoo/meta-ads-weekly-performance.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Meta Ads Weekly Performance" (elias-didoo/meta-ads-weekly-performance) from ClawHub.
Skill page: https://clawhub.ai/elias-didoo/meta-ads-weekly-performance
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: META_ACCESS_TOKEN, META_AD_ACCOUNT_ID
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install meta-ads-weekly-performance

ClawHub CLI

Package manager switcher

npx clawhub@latest install meta-ads-weekly-performance
Security Scan
Capability signals
CryptoRequires OAuth tokenRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (weekly Meta Ads report) matches the requested environment variables (META_ACCESS_TOKEN, META_AD_ACCOUNT_ID) which are exactly what's needed to read account/campaign insights via the Graph API.
ℹ
Instruction Scope
SKILL.md instructs the agent to fetch account and campaign metrics, compute week-over-week changes, detect issues, and format a report. It does not ask the agent to read unrelated files, write to other skills, or transmit data to external destinations beyond the implied Graph API. The instructions are somewhat high-level (no explicit Graph API endpoints, pagination or rate-limit handling), which means the agent will need to implement API calls itself — this is expected but worth noting.
✓
Install Mechanism
Instruction-only skill with no install steps and no downloadable artifacts; nothing is written to disk or pulled from external URLs during install.
✓
Credentials
Only two env variables are required: a Meta access token and an ad account ID. These are appropriate and proportionate for read-only reporting. The SKILL.md indicates the token should have ads_read scope (read-only).
✓
Persistence & Privilege
always:false and no config paths requested. The skill does not request permanent presence or system-wide changes; autonomous invocation is allowed by default (normal behavior).
Assessment
This skill is coherent for producing a Meta Ads weekly report, but be mindful that the META_ACCESS_TOKEN is sensitive. Only provide a token with the minimal ads_read scope, prefer short-lived OAuth tokens or a token tied to a read-only user, and rotate/revoke it when no longer needed. Confirm where the agent will run and whether network access or logs might expose the token. Because the SKILL.md is high-level, verify the agent's implementation handles pagination, rate limits, and does not unknowingly send fetched data to other endpoints. If you need stronger assurance, ask the skill owner for concrete API call examples or an implementation review before providing credentials.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

EnvMETA_ACCESS_TOKEN, META_AD_ACCOUNT_ID
latestvk97exvqtasss0naap0r5crfh0n84zrps
116downloads
0stars
2versions
Updated 1w ago
v1.1.0
MIT-0
@elias-didoo
latest
Download

Required Credentials

CredentialWhere to GetUsed ForOAuth Scope
META_ACCESS_TOKENMeta Developer Console → Graph API Explorer → Generate TokenFetching account and campaign insightsads_read (read-only)
META_AD_ACCOUNT_IDAds Manager URL: adsmanager.facebook.com/act_XXXXXXXXXIdentifying which account to query—

When to Use

At the end of each week (every Monday) for ongoing campaigns. Also use after a significant change (new campaign launch, major budget shift, creative swap) to document the impact.

Requirements

  • account_id (required)
  • date_range: last_7d (default)

Step 1: Pull KPI Snapshot

Fetch account and campaign level metrics for this week and prior week:

  • Spend, results, cost per result
  • ROAS, conversion values
  • CTR, CPM, CPC
  • Frequency

Calculate week-over-week (WoW) change for each metric: WoW = (This Week − Prior Week) / Prior Week × 100

Step 2: Identify What Changed

Write 3-5 bullets explaining the biggest moves this week.

Format: "[What changed] — [Spend/ROAS/Revenue impact]"

Examples:

  • "Increased budget on Pizza Campaign by 30% — spend up $1,200, ROAS held at 3.2x"
  • "Creative rotation on Runner Audience — CTR up 0.8pp, CPL down $2.40"

Step 3: Identify Performance Drivers

Identify the top 3 things driving results this week.

For each driver write one sentence with specific metrics: Format: "[What drove results] – [Spend], [ROAS], [Revenue impact vs last week]"

Step 4: Detect Issues

Run issue detection:

  • Campaigns with ROAS drop > 30% vs prior week
  • Campaigns with spend > budget but low conversion rate
  • New campaigns still in Learning Phase
  • Frequency > 4 on any campaign

Step 5: Format Output

Key Metrics Snapshot

MetricThis WeekPrior WeekWoW Change
Spend
ROAS
Conversions
CPA

What Changed This Week

  • [3-5 bullets]

Performance Drivers

  • [3 bullets]

Issues and Actions Required

  • [3 urgent issues, each with problem/solution format]

Rules

  • No executive summary
  • Specific numbers on every line
  • Separate problem from solution clearly in each issue
  • This is a reporting tool — recommendations route to meta-ads-recommendation

Comments

Loading comments...