agentleFS
mathiaschumathiaschu/meta-ads-analyzer/skill/SKILL.md

meta-ads-analyzer

Skill428 starsChanged 9 months agoMITView on GitHub

Provides expert-level analysis and diagnosis for Meta Ads campaigns. Use this skill to interpret performance data, identify root causes of issues, and generate actionable recommendations, with a special focus on correctly handling the 'Breakdown Effect'. Use when the user mentions Meta Ads analysis, campaign diagnosis, ad performance, CPA analysis, ROAS analysis, or asks to analyze exported data from Meta Ads Manager.

6 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 1

    1. Tommyvr7/meta-ads-analyzer★ 0100% same

    Edited · 1

    1. TehseenTech/manus-skills★ 074% same

    Wrote their own version · 4

    1. athina-ai/goose-skills★ 1.3ksame name
    2. gooseworks-ai/goose-skills★ 1.3ksame name
    3. Synero/meta-ads-analyzer★ 9same name
    4. Eugenevdm01/eugenes-meta-agent★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when you need to analyze and diagnose Meta Ads campaign performance, including:

    line 10
  2. Distinctive:

    EVERY insight must include data evidence and explanation: Every recommendation must be actionable and verifiable.

    line 23
  3. Very specific:

    ALIGN WITH OFFICIAL RECOMMENDATIONS: Check get_recommendations API first.

    line 24
  4. Distinctive:

    Disambiguate clicks: Never use the term "clicks" alone.

    line 25
  5. Distinctive:

    Audience size: When reporting reach or audience size, use "Accounts Center accounts" or the number without unit — never "people" — per …

    line 26
  6. Distinctive:

    IMPORTANT: Always rename metric names to standardized, non-sensitive names exactly as specified below in all responses:

    line 30
  7. Distinctive:

    "People" Usage: When "people" is used in contexts referring to audience size, replace with "Accounts Center accounts".

    line 61
  8. Distinctive:

    If in learning: caveat all findings as preliminary

    line 106
  9. Distinctive:

    Ad Relevance Diagnostics: Check Quality, Engagement, and Conversion Rate Rankings to diagnose creative, targeting, or post-click issues.

    line 113

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meta Ads Analysis & Diagnosis Skill

When to Use This Skill

Use this skill when you need to analyze and diagnose Meta Ads campaign performance, including:

  • Interpreting campaign, ad set, or ad-level performance data
  • Identifying root causes of performance issues
  • Generating actionable optimization recommendations
  • Understanding why Meta's system makes certain budget allocation decisions
  • Analyzing CSV exports, screenshots, or raw data from Meta Ads Manager

Result Recommendations (MANDATORY for Final Reports)

IMPORTANT: The following rules are MANDATORY and MUST be strictly followed when writing the final analysis report. These are not optional guidelines — they define the required standards for all deliverables.

  • NEVER recommend pausing or reducing budget for any segment based solely on higher average CPA/CPM in breakdown reports. Higher average cost does NOT mean poor performance — it often reflects the system capturing low marginal cost opportunities earlier. Removing segments may increase overall costs. Always frame changes as testable hypotheses, not directives.
  • ALWAYS justify recommendations with data evidence, Meta's system mechanics, and expected impact on overall campaign performance.
  • EVERY insight must include data evidence and explanation. Every recommendation must be actionable and verifiable.
  • ALIGN WITH OFFICIAL RECOMMENDATIONS. Check get_recommendations API first. If diverging, explicitly acknowledge and explain why.
  • Disambiguate clicks. Never use the term "clicks" alone. Use "Clicks (all)" for total interactions (likes, shares, page clicks, link clicks) or "Link Clicks" for clicks that lead offsite; these are distinct metrics with different meanings.
  • Audience size: When reporting reach or audience size, use "Accounts Center accounts" or the number without unit — never "people" — per legal requirements.

Metric Naming Guidelines

IMPORTANT: Always rename metric names to standardized, non-sensitive names exactly as specified below in all responses:

Raw Metric NameStandardized Display Name
impressionsImpressions
video_thruplay_watched_actionsThruPlays
clicksClicks (all)
purchase_roasPurchase ROAS (return on ad spend)
cpmCPM
cpcCPC (all)
ctrCTR (all)
cost_per_action_type:link_clickCPC (Link Click)
outbound_clicks_ctrOutbound CTR
cost_per_action_type:purchaseCost per Purchase
actions:purchasePurchases
action_values:purchasePurchase Value
frequencyFrequency
reachReach (Accounts Center accounts)
spendAmount Spent

Core Principles

  • Holistic First: Evaluate at aggregate level before drilling down. The system optimizes for the whole, not the parts.
  • Dynamic over Static: Analyze performance over time, not single snapshots.
  • Marginal over Average: The system prioritizes marginal CPA (cost of the next result), not average CPA. A higher average CPA segment might be preventing even higher marginal costs elsewhere.

Meta Ads Domain Knowledge

Legal Requirements & Terminology

  • Audience Size Metrics: Due to legal requirements, when referring to audience size metrics (the total number of accounts that view the ad), you must use "Accounts Center accounts" (case insensitive) or report the metric without any unit instead of "people".
  • "People" Usage: When "people" is used in contexts referring to audience size, replace with "Accounts Center accounts". When a specific number is used with "people" (e.g., "17,000 people"), use "person" after the number (e.g., "17,000 person").

Campaign & Performance Definitions

  • Conversion Ads: Ad entities with objectives like Lead, Sales, or App Promotions are categorized as conversion ads.
  • Conversion Rate: Conversion rate = conversions / impressions.
  • Performance Indicators: Lower Cost Per Result or CPM = higher performance. Higher ROAS = higher performance.

Account & Asset Issues

  • Disabled or Restricted Account: Occurs when assets (FB account, IG account, ad account, page, payout account) have been disabled or restricted by Meta, usually due to policy violations.

Budget & Billing

  • Daily Spending Limit (DSL): The current daily spending limit that advertisers can check, increase, or decrease.
  • Billing Threshold (Payment Threshold): The amount of ad spend that triggers a payment method charge when reached.

Analysis Workflow

Reference Documents (loaded automatically from references/):

  • breakdown_effect.md - The Breakdown Effect with examples (READ THIS FIRST)
  • core_concepts.md - Ad Auction, Pacing, Learning Phase overview
  • learning_phase.md - Learning phase mechanics
  • ad_relevance_diagnostics.md - Quality, Engagement, Conversion rankings
  • auction_overlap.md - Diagnosing auction overlap
  • pacing.md - Budget and bid pacing
  • bid_strategies.md - Spend-based, goal-based, manual bidding
  • ad_auctions.md - How auction winners are determined
  • performance_fluctuations.md - Normal vs. concerning fluctuations

Step 1: Identify the Correct Evaluation Level

This is the most critical step to avoid the Breakdown Effect.

Campaign SetupCorrect Evaluation Level
Advantage+ Campaign Budget (CBO)Campaign Level
Automatic Placements (without CBO)Ad Set Level
Multiple Ads within a single Ad SetAd Set Level

Step 2: Check Learning Phase Status

Before any analysis:

  • Is the ad set still in learning phase? (~50 optimization events needed)
  • Were there recent significant edits that reset learning?
  • If in learning: caveat all findings as preliminary

Step 3: Analyze with Meta-Specific Lens

Focus on these analytical angles:

  1. Marginal Efficiency Analysis: Infer marginal CPA trends from time-series data. A segment with low average CPA but rising marginal CPA explains why the system shifts budget away.
  2. Ad Relevance Diagnostics: Check Quality, Engagement, and Conversion Rate Rankings to diagnose creative, targeting, or post-click issues.
  3. Auction Overlap Check: Are ad sets competing against each other? Look for learning limited status and underdelivery.
  4. Pacing Analysis: Is the system holding back budget for better opportunities? Evaluate over full campaign, not daily snapshots.
  5. Performance Fluctuation Assessment: Is this normal variation (20-30% day-to-day) or a concerning trend (>50% sustained)?

Step 4: Synthesize Findings Through Breakdown Effect Lens

Interpret ALL findings through the Breakdown Effect framework. Explain why the system makes certain decisions.

Example: "While Placement A shows $10 average CPA vs Placement B's $15, time-series analysis reveals Placement A's CPA rising sharply — its marginal CPA likely exceeds Placement B's. The system correctly shifts budget to secure more conversions at lower marginal cost."

Step 5: Generate Report

Structure every analysis report as:

  1. Executive Summary - 2-3 key findings
  2. Evaluation Level - Which level and why
  3. Learning Phase Status - Current state per ad set
  4. Performance Analysis - Metrics with proper naming
  5. Diagnosis - Root causes with evidence
  6. Recommendations - Actionable, with expected impact, framed as testable hypotheses
  7. Breakdown Effect Notes - Explicit callouts where this applies

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.