SkillAgentSearch skills...

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. Platform: Google and Meta.

Install / Use

npx skills add irinabuht12-oss/marketing-skills --skill pacing-monitor

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Operations

Supported Platforms

Universal

Tags

Our assessment of pacing-monitor

pacing-monitor scores 83/100 on our quality scale, 593rd of 746 Operations skills we index.

Its SKILL.md is 2.8 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 7,761 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
17/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 20 days ago, so pacing-monitor is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

Review

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The skill instructs the agent to add a third-party MCP connector at https://connector.get-ryze.ai/mcp, routing sensitive Google/Meta ad account data through an unofficial external service.

AI review: risky

  • The skill instructs the agent to add a third-party MCP connector at https://connector.get-ryze.ai/mcp, routing sensitive Google/Meta ad account data through an unofficial external service.
  • It includes a CLI command (`claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp`) for the agent to run, which installs/authorizes that external connector.
  • It requests broad read access to Google Ads, Meta Ads, GA4, and Search Console, expanding the agent's trust boundary beyond the user's own infrastructure.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

pacing-monitor compared with similar skills

All 4 of these similar skills score higher than pacing-monitor; compare them before choosing.

SkillScoreStarsUpdatedFormat
pacing-monitor (this skill)by irinabuht12-oss837.8k20d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install pacing-monitor?
Run npx skills add irinabuht12-oss/marketing-skills --skill pacing-monitor. The install tabs above show the steps for each supported agent.
Which AI agents does pacing-monitor work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is pacing-monitor safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The skill instructs the agent to add a third-party MCP connector at https://connector.get-ryze.ai/mcp, routing sensitive Google/Meta ad account data through an unofficial external service. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is pacing-monitor still maintained?
The repository was last updated 20 days ago, so pacing-monitor is actively maintained.

name: pacing-monitor description: 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. metadata: platform: Google and Meta

27/ Pacing Monitor — Google + Meta

What it does

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.

How it works

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.

Practical example

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.

What you get back

  • Overall account pacing vs target with projected end-of-month spend
  • Campaign-by-campaign pacing status (on track, overspending, underspending)
  • Exact daily budget needed for each campaign to hit monthly target
  • Flags for campaigns limited by budgets, bids, or audience size that can't scale to meet target
  • Historical pacing patterns showing if your account typically front-loads or back-loads spend in a month

When to use it

  • Weekly pacing checks, ideally every Monday and mid-week
  • When clients have strict monthly budgets that can't be exceeded
  • During heavy spend periods (holiday, promotions) where daily oversight matters more
  • End of month when you need to throttle or accelerate to land on target

Data access (Ryze MCP)

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:

  • claude.ai / Claude Desktop: Settings → Connectors → Add custom connector → https://connector.get-ryze.ai/mcp
  • Claude Code: claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp
  • Cursor: Settings → MCP → add the same URL

Setup guide: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp

Related Skills

View on GitHub
GitHub Stars7.8k
CategoryOperations
Updated20d ago
Forks579

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium