meta-ads-analyzer
Skill0 starsChanged 3 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'. Apply automatically when the request matches; the user does not need to mention this skill.
6 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- athina-ai/goose-skillstheir own version, first seen Nov 9, 2026
- Eugenevdm01/eugenes-meta-agenttheir own version, first seen Nov 8, 2026
- gooseworks-ai/goose-skillstheir own version, first seen Nov 1, 2026
- Synero/meta-ads-analyzertheir own version, first seen Jun 1, 2026
- mathiaschu/meta-ads-analyzeredited, first seen Feb 26, 2026
- Tommyvr7/meta-ads-analyzeredited, first seen Feb 26, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- mathiaschu/meta-ads-analyzer★ 42846% same
- Tommyvr7/meta-ads-analyzer★ 046% same
Wrote their own version · 4
- athina-ai/goose-skills★ 1.3ksame name
- gooseworks-ai/goose-skills★ 1.3ksame name
- Synero/meta-ads-analyzer★ 9same name
- 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.
In this repository76 other files it gives its agents.
- app-store-submission-packagerSkill
- digital-product-inventorSkill
- ios-testflight-github-actionsSkill
- get-to-know-a-clientSkill
- investigate-before-recommendSkill
- production-system-auditSkill
- similarweb-analyticsSkill
- stock-analysisSkill
- system-architectSkill
- autonomous-github-syncSkill
- autonomous-sync-scriptSkill
- github-gem-seekerSkill
- organize-github-reposSkill
- using-git-worktreesSkill
- brainstorm-logosSkill
- brand-driven-ux-overhaulSkill
- canvas-designSkill
- excel-generatorSkill
- frontend-designSkill
- inspirational-music-video-productionSkill
- theme-factorySkill
- video-generatorSkill
- multiplayer-game-builderSkill
- promo-code-systemSkill
- realistic-ai-persona-builderSkill
- role-based-access-controlSkill
- serverless-debuggingSkill
- vertical-expansion-blueprintSkill
- manus-mcp-configuratorSkill
- mcp-auto-recoverySkill
- mcp-builderSkill
- mcp-connector-testerSkill
- mcp-ecosystem-optimizerSkill
- voice-ai-integrationSkill
- api-endpoint-builderSkill
- database-schema-generatorSkill
- testing-frameworkSkill
- deployment-automationSkill
- error-monitoring-setupSkill
- github-workflow-automationSkill
- analytics-dashboardSkill
- email-system-builderSkill
- feature-flag-systemSkill
- user-authentication-systemSkill
- cron-job-schedulerSkill
- file-upload-systemSkill
- notification-systemSkill
- payment-integrationSkill
- search-implementationSkill
- debug-mining-engineSkill
- doc-coauthoringSkill
- docxSkill
- internet-skill-finderSkill
- pdfSkill
- pptxSkill
- project-handoff-ingestionSkill
- serverless-debuggingSkill
- skill-arsenal-builderSkill
- skill-creatorSkill
- skill-demo-builderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
5
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
- Distinctive: line 15
Use this skill when the request matches its description.
- Distinctive: line 21
Use this skill when you need to analyze and diagnose Meta Ads campaign performance, including:
- Distinctive: line 33
EVERY insight must include data evidence and explanation: Every recommendation must be actionable and verifiable.
- Very specific: line 35
ALIGN WITH OFFICIAL RECOMMENDATIONS: Check get_recommendations API first.
- Distinctive: line 36
Disambiguate clicks: Never use the term "clicks" alone.
- Distinctive: line 72
Ad Relevance Diagnostics: Check Quality, Engagement, and Conversion Rate Rankings to diagnose creative, targeting, or post-click issues.
“Common” is measured: kept by at least 6 in 10 of the 6 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.
Files
Overview
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'. Apply automatically when the request matches; the user does not need to mention this skill.
This skill should apply automatically when the request matches; the user does not need to mention this skill.
Usage
Use this skill when the request matches its description. The skill is discovered automatically; the user does not need to mention the skill explicitly.
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
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.
- USE QUALIFIED LANGUAGE. Say "Estimated Reach of ~1,000" not "You reached 1,000 people." All metrics are estimates.
- ALIGN WITH OFFICIAL RECOMMENDATIONS. Check
get_recommendationsAPI 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.**
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.
Analysis Workflow
Reference Documents:
references/breakdown_effect.md- The Breakdown Effect with examples (read this first)references/core_concepts.md- Ad Auction, Pacing, Learning Phase overviewreferences/learning_phase.md- Learning phase mechanicsreferences/ad_relevance_diagnostics.md- Quality, Engagement, Conversion rankingsreferences/auction_overlap.md- Diagnosing auction overlapreferences/pacing.md- Budget and bid pacingreferences/bid_strategies.md- Spend-based, goal-based, manual biddingreferences/ad_auctions.md- How auction winners are determinedreferences/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 Setup | Correct Evaluation Level |
| Advantage+ Campaign Budget (CBO) | Campaign Level |
| Automatic Placements (without CBO) | Ad Set Level |
| Multiple Ads within a single Ad Set | Ad Set Level |
Step 2: Analyze with Meta-Specific Lens
Focus on these Meta-specific analytical angles:
- 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.
- Ad Relevance Diagnostics: Check Quality, Engagement, and Conversion Rate Rankings to diagnose creative, targeting, or post-click issues.
- Learning Phase Status: Determine if ad sets are still in learning phase (~50 results needed to exit).
Step 3: Synthesize Findings Through Breakdown Effect Lens
Interpret all findings through the Breakdown Effect. 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."
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
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.

