Tracks daily spend against monthly budget targets across all campaigns and accounts. Tells you exactly where you'll land at current pace, flags campaigns that are over or underspending, and calculates the daily budget adjustments needed to hit your target by month end. Platform: Google and Meta.
npx skills add https://github.com/irinabuht12-oss/marketing-skills --skill pacing-monitor
Tracks daily spend against monthly budget targets across all campaigns and accounts. Tells you exactly where you'll land at current pace, flags campaigns that are over or underspending, and calculates the daily budget adjustments needed to hit your target by month end.
Claude takes your current month-to-date spend, remaining days in the month, and monthly budget targets, then projects end-of-month spend at the current run rate. It accounts for weekday vs weekend spend patterns and flags any campaigns that need immediate budget adjustments to stay on track.
It's the 14th of the month. Your total monthly target is $120K across 6 campaigns. Current MTD spend is $52K. At the current daily rate, you'll end at $111K — $9K under target. But the underspend isn't evenly distributed: Campaign A is pacing 15% over target and will overshoot by $3,200, while Campaign D is pacing 40% under because it's limited by bid caps. Claude calculates that Campaign D needs its daily budget increased from $800 to $1,350 and bid caps loosened by 20% to catch up, while Campaign A should be pulled back from $2,100/day to $1,800/day.
This skill works best with live account data. Connect the free Ryze MCP once and Claude reads your Google Ads, Meta Ads, GA4 and Search Console directly:
https://connector.get-ryze.ai/mcpclaude mcp add ryze --transport http https://connector.get-ryze.ai/mcpSetup guide: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp
Take irinabuht12-oss/pacing-monitor from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.