Monitor paid-ad account pacing, delivery, performance, creative fatigue, tracking, policy, and data quality across supported platforms. Use for daily or weekly checks, anomaly review, budget pacing, post-launch verification, or campaign monitoring.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add AgriciDaniel/claude-ads --skill ads-monitor --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ads Monitor?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/agricidaniel-ads-monitor)More formats (shields.io, HTML) on the badges page.
---
name: ads-monitor
description: "Monitor paid-ad account pacing, delivery, performance, creative fatigue, tracking, policy, and data quality across supported platforms. Use for daily or weekly checks, anomaly review, budget pacing, post-launch verification, or campaign monitoring."
---
# Paid Media Monitoring
1. Load two or more normalized snapshots with compatible account, timezone,
currency, metric, and attribution definitions.
2. Validate data freshness and finalization windows before comparing periods.
3. Separate expected learning, seasonality, reporting latency, and planned changes
from unexplained anomalies.
4. Evaluate pacing, delivery, conversion quality, unit economics, creative fatigue,
tracking health, policy status, and changed account objects.
5. Return observations, confidence, likely causes, required investigation, and
decision thresholds. Do not mutate the account.
6. Persist a versioned monitoring bundle and link detected failures to regression
or follow-up tasks.
Do not alert on percentage changes with trivial denominators or incomparable
windows. State when evidence cannot distinguish noise from a material change.
No comments yet. Be the first to comment!