Meta Ads Drop Diagnosis

[Didoo AI] Diagnoses sudden performance drops in Meta Ads campaigns. Use when CTR, ROAS, or conversions suddenly decline with no obvious explanation, or when...

Security Scan

The skill's requests and runtime instructions are consistent with diagnosing Meta Ads drops — it only asks for the Meta access token and ad account ID and contains no installable code or unrelated permissions.

Purpose & Capability

The name/description (Meta Ads drop diagnosis) matches the two declared requirements: META_ACCESS_TOKEN and META_AD_ACCOUNT_ID. Both are necessary and sufficient to query the Meta Graph API for campaign performance data; no unrelated credentials or tools are requested.

Instruction Scope

SKILL.md describes fetching campaign metrics, computing week-over-week changes, performing root-cause logic, producing a recovery plan, and writing two session-context keys. It does not instruct reading arbitrary system files, other environment variables, or transmitting data to endpoints other than Meta's API. The only scope creep to note is that it asks the user to generate an access token (via Graph API Explorer) but does not discuss token lifetime or storage.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk or downloaded during install, which minimizes installation risk.

Credentials

Only two env vars are required: a Meta access token and the ad account id. These are directly relevant to the stated purpose. The SKILL.md recommends ads_read (read-only) scope, which is appropriate; the user should prefer short-lived/read-only tokens where possible.

Persistence & Privilege

always is false and the skill is user-invocable. It writes two session-context keys (primary_root_cause, recovery_plan) for integration with meta-ads-recommendation — this is reasonable, but you should confirm how long session context persists and which other skills or humans can access it.

Assessment

This skill appears coherent and limited to reading Meta Ads data. Before enabling it, confirm you will provide a read-only Meta access token (ads_read) and the correct ad account id. Prefer short-lived tokens and avoid granting broader scopes. Note the skill stores brief diagnosis text in session context (primary_root_cause and recovery_plan) — verify your environment's session retention and who can read those keys. The skill's source is listed as unknown (homepage points to a blog); because it is instruction-only and requires no install, the technical risk is low, but treat the access token like any credential: only provide tokens you trust the agent to use and rotate them if you later revoke access.

Required Credentials

Credential	Where to Get	Used For	OAuth Scope
META_ACCESS_TOKEN	Meta Developer Console → Graph API Explorer → Generate Token	Fetching campaign performance data	ads_read (read-only)
META_AD_ACCOUNT_ID	Ads Manager URL: adsmanager.facebook.com/act_XXXXXXXXX	Identifying which account to query	—

When to Use

Triggered by meta-ads-daily-pulse flagging a week-over-week drop > 20%, or when user reports "performance suddenly dropped." Not for gradual decline over weeks (that's creative fatigue territory).

---

Requirements

• account_id (required) — your META_AD_ACCOUNT_ID (format: act_XXXXXXXXX)
• campaign_id or ad_id of the declining entity (required) — find in Meta Ads Manager URL, or via GET /act_{AD_ACCOUNT_ID}/campaigns?fields=id,name
• date_range: last_7d (default)

---

Step 1: Establish the Drop

Confirm the drop with a Performance Snapshot mini-table:

Metric	Last Week	This Week	WoW Change
Impressions
CPM
CTR
Frequency
CVR
CPA
ROAS

Confirm it's real: WoW drop must be > 20% on at least 2 metrics to qualify as a "drop" (not normal fluctuation).

---

Step 2: Root Cause Analysis

Based on the metric pattern, identify the top 1-3 most likely root causes.

Use this decision tree:

Pattern	Likely Root Cause
CTR down, frequency up	Creative fatigue
CTR down, frequency stable	Creative burnout or audience mismatch
CTR stable, CVR down	Landing page issue or offer problem
CTR up, CVR down	Landing page can't handle higher volume
Impressions down, CPM up	Competition increased, bid not competitive
Frequency up, ROAS down	Retargeting audience exhausted
All metrics down	External factor (seasonality, iOS, pixel issues)

For each root cause, write 1-3 short sentences explaining what the data shows, why it points to this cause, and what other evidence supports or contradicts it.

---

Step 3: Recovery Plan

Format:

Immediate (next 24 hours):

• [Specific action: pause, scale down, refresh, shift budget]
• Why this helps now

Short-term (this week):

• [New creative, audience expansion, placement changes]
• What to test and why

Prevention (ongoing):

• [Rotation schedule, budget cap rules, monitoring thresholds]
• How to catch this earlier next time

---

Step 4: Output Format

Title: Summary
Declining campaign: [Name]
Performance Snapshot: [mini-table above]

Title: Root Cause Analysis
[1-3 root causes with supporting evidence]

Title: Recovery Plan
Immediate: [actions]
Short-term: [actions]
Prevention: [actions]

---

Rules

• Root cause must be supported by data — do not speculate without evidence
• If data is insufficient (e.g., < 3 days since change), say so and recommend waiting
• This is diagnosis only — specific action recommendations route to meta-ads-recommendation
• One immediate action maximum — don't overwhelm the user

---

Session Context — What This Skill Writes

After completing diagnosis, store the following in session context:

Key	Description	Example
primary_root_cause	The most likely cause of the drop	"Creative fatigue — frequency 4.8, CTR dropped 38% WoW"
recovery_plan	Immediate + short-term + prevention actions	"Rotate new creative within 24h; set frequency cap at 3"

meta-ads-recommendation reads these keys to produce the structured recovery action plan.