Token导航 LogoToken导航TokenDH.com
效率需要联网clawhub未标认证来源可访问clear审计通过

meta-ads-healthcheck元广告健康检查

Agent Skill

meta-ads-healthcheck 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

3,387

周安装

137

GitHub Stars

公开资料未说明

下载量

1,063
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:meta-ads-healthcheck(元广告健康检查)
来源仓库:https://github.com/elias-didoo/meta-ads-healthcheck
安装命令:
openclaw skills install meta-ads-healthcheck
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install meta-ads-healthcheck

简介

快速检查广告活动健康状态,用绿黄红标识整体表现水平。

  • 适合日常监控“我的广告是否有效”类查询。
  • 基于预设阈值自动分类问题严重程度。meta-ads-healthcheck 属于效率类 Skill,可作为该场景下的辅助能力补充。
  • 需授予读取活动指标的只读权限方可生效。
  • 原始文档包含阈值调整建议与自定义规则扩展方式。

SKILL.md

name
meta-ads-healthcheck
description
[Didoo AI] Fast on-demand campaign status check — answers \"are my ads working?\" using Green/Yellow/Red thresholds. For daily routine monitoring, use meta-ads-daily-pulse instead.
homepage
https://didoo.ai/blog
metadata

Required Credentials

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

When to Use

When user wants a quick "are my ads working?" check — not a deep diagnostic, just a status update. Use before a meeting, or any time something feels off.

meta-ads-healthcheckmeta-ads-daily-pulse
Primary question"Is this campaign healthy or not?""Did anything change vs. last week?"
Comparison basisFixed Green/Yellow/Red thresholdsSame day of prior week (WoW)
Best forOn-demand check when something feels wrong; meeting prepDaily routine, morning scan
Output styleCampaign-by-campaign status reportChange alerts ranked by revenue impact

Step 1: Get the Basics

Pull the user's Meta Ads data for today and the past 7 days:

  • Campaign name, status, spend
  • Results, cost per result
  • CTR, frequency
  • Any alerts or issues (delivery low, learning limited, paused)

Use Meta Marketing API to fetch campaign and adset level data.


Step 2: Traffic Light Assessment

Score each campaign as Green / Yellow / Red:

SignalGreenYellowRed
DeliverySpending normally< 80% of budget< 50% or zero
Cost per resultAt or below target10–30% above target (and variance is normal)30%+ above target and sustained (not just a spike)
Frequency< 33–4> 4
LearningOut of learningIn learning (< 7 days)Stuck in learning
CTR> 1%0.5–1%< 0.5%

Step 3: Check for Normal Performance Fluctuations

Before flagging a campaign as Yellow or Red, confirm it's not normal fluctuation.

Normal fluctuation — monitor only:

  • CPA is bouncing around day-to-day (up to ±30%) but the rolling average is stable — this is normal Meta Ads volatility, not a problem
  • Weekend vs. weekday differences
  • Gradual changes over weeks
  • Variation while in Learning Phase

Concerning — investigate today:

  • CPA average has shifted up and stayed there for 3+ consecutive days (not just a one-day spike) — this is a real trend, not fluctuation
  • Delivery dropping to near zero with no budget change
  • Conversion rate declining while spend increases
  • Performance degradation after a recent edit

Before diagnosing problems, ask:

  1. Is the ad set still in Learning Phase? (if yes, delay judgment — data is unstable)
  2. What's the baseline for normal variation for this campaign?
  3. Are there external factors — seasonality, competitor activity, or platform changes?
  4. Is sample size sufficient? (typically need 7+ days of data for stable ad sets)

Step 4: Surface Key Issues

For each Yellow or Red campaign, identify:

  • What is the specific problem?
  • How urgent is it? (Needs attention today / this week / monitor)
  • What likely caused it?

Creative Refresh Trigger — Frequency > 3: When frequency reaches 3 or higher, flag the campaign as "Creative Refresh Needed": "Campaign [X] has frequency at [N] — audience is seeing the same ads too often. This typically causes CTR to drop and CPL to rise. Creative refresh is indicated."

Note: When this flag appears, the appropriate next step is meta-ads-recommendation — it will prescribe the specific creative refresh action based on the full analysis context. Do not trigger meta-ads-builder directly from this skill.

Step 5: Quick Output

Overall Status: [N] campaigns running | [N] Green | [N] Yellow | [N] Red

For each Red/Yellow campaign:
- Campaign name
- Status: [Issue]
- Spend / Results / CPL
- What happened (1 sentence)
- Suggested focus area (1 sentence)

Everything else: brief healthy summary.

Priority Sort — What to Check First

When you have 10+ active campaigns:

  1. Red campaigns with spend > $50/day → Check today
  2. Yellow campaigns where CPL is 20%+ above target → Check today
  3. New campaigns (< 7 days, still in Learning) → Flag as "Learning Phase — Do Not Judge Yet"
  4. Green campaigns → Review weekly

When to Escalate

  • If the health check surfaces a real problem: suggest meta-ads-analysis for a full diagnostic
  • For daily routine monitoring: suggest meta-ads-daily-pulse instead

Skill Boundary

  • This is a quick scan, not a deep diagnostic — don't draw conclusions beyond what's clearly broken or healthy
  • Do not make optimization recommendations in this skill — that's meta-ads-recommendation's job
  • Do not re-fetch data if it was recently pulled in the same session

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

OpenClaw

82.55%
按下载量换算878

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills