Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

meta-ads-analyzer元广告分析器

Agent Skill

meta-ads-analyzer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,497

周安装

63

GitHub Stars

公开资料未说明

下载量

524
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:meta-ads-analyzer(元广告分析器)
来源仓库:https://github.com/ideola-ai/marketing-ads-skills
仓库路径:skills/meta-ads-analyzer
安装命令:
npx skills add https://github.com/ideola-ai/marketing-ads-skills --skill meta-ads-analyzer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/ideola-ai/marketing-ads-skills --skill meta-ads-analyzer

简介

用于查找、检索和筛选相关信息。

  • 适合根据关键词或任务场景快速定位候选结果。
  • 可结合来源仓库和原始 README 核验具体用法。
  • 安装命令:npx skills add https://github.com/ideola-ai/marketing-ads-skills --skill meta-ads-analyzer
  • 安装前建议确认权限范围和是否会触发联网。

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

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_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.**

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)

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" (e.g., "Your reach is 17,000" or "Your ad reached 17,000 Accounts Center accounts").
  • "People" Usage: When "people" is used in contexts referring to audience size (e.g., "reach more people", "seen by people", "your ad reached people", "show ads to people"), the word "people" must be replaced with "Accounts Center accounts". When "people" is used with specific actions, behaviors, characteristics, or qualifiers that describe what people do or are likely to do, "people" is acceptable.

Campaign & Performance Definitions

  • Conversion Ads: Ad entities with objectives like Lead, Sales, or App Promotions are categorized as conversion ads.
  • Conversion Rate: Conversion rate = conversion / impression.
  • Performance Indicators: Lower value of Cost Per result or CPM is associated with higher performance. Higher value of ROAS is associated with higher performance.

Account & Asset Issues

  • Disabled or Restricted Account: Occurs when one or more of the customer's assets (e.g., FB account, IG account, ad account, page, payout account) have been disabled or restricted by Meta, usually because the customer violated some policies. This is not relevant for general questions about business manager setup, deleting a business manager, or converting a Facebook page to a business page.

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. Advertisers can check limit, lower, or increase their payment threshold. The billing threshold is also relevant to billing frequency (e.g., monthly billing, daily billing).

Support Intent Recognition

  • Support or Troubleshooting Intent: Occurs when a user is seeking actionable help to fix, recover, or resolve a specific issue, error, or technical problem related to their Meta assets, accounts, payments, or advertising activities, or seeking to speak with a human agent. This intent is characterized by a need for step-by-step guidance, procedural instructions, or direct intervention—rather than general learning, strategic planning, or performance improvement.

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 overview
  • references/learning_phase.md - Learning phase mechanics
  • references/ad_relevance_diagnostics.md - Quality, Engagement, Conversion rankings
  • references/auction_overlap.md - Diagnosing auction overlap
  • references/pacing.md - Budget and bid pacing
  • references/bid_strategies.md - Spend-based, goal-based, manual bidding
  • references/ad_auctions.md - How auction winners are determined
  • references/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: Analyze with Meta-Specific Lens

Focus on these Meta-specific 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. 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."

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.4%
按下载量换算191

Claude

30.92%
按下载量换算162

Cursor

16.88%
按下载量换算88

Gemini CLI

9.43%
按下载量换算49

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills