mbfinotti/advertising-skills / skills/ad-budget-pacing
ad-budget-pacing
VerifiedTrack daily and weekly spend against a single campaign or account budget and flag under-pacing or over-pacing before it hurts results, reporting the pacing ratio, projected period spend, and the corrective daily spend behind every alert. Use whenever the user mentions budget pacing, spend tracking, burn rate, spend vs budget, projected month-end spend, underspending or overspending, or asks whether a campaign is on pace - even if they never say 'pacing'. Covers any ad platform, B2B and B2C, calendar-month or fixed-date flights. It flags and recommends; it never changes budgets or bids. Do NOT use to plan a scale-up (mbfinotti/advertising-skills@paid-media-scaling) or to set CAC/ROAS thresholds (mbfinotti/advertising-skills@ad-spend-guardrails).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 28.1 KB |
| evals/evals.json | config | 23.3 KB |
| references/pacing-report-example.md | markdown | 1.6 KB |
| references/platform-delivery-notes.md | markdown | 1.5 KB |
evals/evals.json
View on GitHub{
"skill_name": "ad-budget-pacing",
"evals": [
{
"id": 1,
"prompt": "I run paid search at Brightpath Legal, a B2B legal-intake software company. Our Google Ads campaign has a $24,000 budget for September - calendar month, and it's a target, not a contractual commitment. Through September 18 we've spent $10,800, and the trailing 7-day average is $560/day against an $800 daily budget. The account has run since spring with no seasonality and pretty even weekday/weekend delivery. Nobody has touched settings in over two weeks and I'm looking at yesterday's finalized numbers. Search impression share lost to rank is 38% and lost to budget is 2%. I'm clearly behind - should I raise the daily budget from $800 to $1,100 to catch up before month end? Give me the full pacing picture and what to change.",
"expected_output": "A pacing report that computes the full arithmetic (ratio 0.75, projection $18,000, required daily $1,100, adjust +$540/day), passes the false-alarm gate, reads the impression-share pair as a rank/bid constraint, refuses the budget raise, and recommends a bid-side change packet handed to a named owner.",
"files": [],
"expectations": [
"Computes the pacing ratio as approximately 0.75, from $10,800 spent against a $14,400 expected-to-date (18 of 30 days of $24,000).",
"Reports a projected period spend of $18,000 if nothing changes.",
"Reports the required daily spend of $1,100 over the 12 remaining days alongside the projection, not the projection alone.",
"Reports a signed corrective figure of approximately +$540/day, the gap between the $1,100 required daily and the $560 trailing 7-day average.",
"Classifies the deviation as urgent (ratio below 0.85) while labelling the on-pace/urgent bands a practitioner convention to recalibrate against this account's history, not a platform rule.",
"States an explicit false-alarm gate result before alerting, confirming the deviation is not explained by a first/last partial day, a trivial denominator, a recent budget edit, or intra-day figures.",
"Reads the 38% impression share lost to rank against 2% lost to budget as bid competitiveness or quality being the binding constraint, not budget.",
"Advises against raising the daily budget from $800 to $1,100, stating that adding budget will not close a rank-constrained gap.",
"Recommends a bid-side remedy (bid or target adjustment) as the corrective action instead of a budget change.",
"Shapes the recommendation as a change packet showing current and proposed values with a rationale.",
"The change packet includes a verification date and a rollback trigger.",
"Names a specific owner role or person to execute the change and explicitly hands off rather than executing or promising to execute the change itself.",
"Keeps the correction to the smallest reversible change: a single variable and a modest step, not a campaign restructure."
]
},
{
"id": 2,
"prompt": "Quick sanity check. I manage Google Ads for Nordic Sleepwear, a B2C ecommerce bedding brand. Our October budget is $15,500 and the campaign daily budget is $500. Yesterday, October 9, Google spent $970 - nearly double the daily budget. Total spend through October 9 is $4,410. My plan is to cut the daily budget to $400 to compensate and file for a refund of the $470 overage. Can you check the pacing and confirm the plan?",
"expected_output": "A report that judges spend cumulatively (ratio 0.98, on pace), explains Google's documented 2x daily overdelivery and 30.4x monthly billing cap, suppresses the alert under the overdelivery gate check, ships the report with an ON PACE (deviation suppressed) status, and declines both the budget cut and the refund claim.",
"files": [],
"expectations": [
"Judges cumulative spend against the prorated period budget ($4,500 expected by day 9 of 31) rather than judging yesterday's $970 against the $500 daily budget.",
"Computes the cumulative pacing ratio as approximately 0.98 and concludes the campaign is on pace.",
"States that Google may deliberately spend up to 2x the average daily budget in a single day.",
"States Google's monthly billing cap of 30.4x the average daily budget, with overdelivery beyond it credited.",
"Concludes no refund claim is needed because overdelivery past the cap is credited rather than billed, distinguishing served from billed spend.",
"Suppresses the alert under the platform-overdelivery gate check and records the suppression reason in the report.",
"Still delivers a full report despite the suppression, with a status equivalent to ON PACE (deviation suppressed).",
"Makes no corrective recommendation while suppressed, and specifically does not endorse cutting the daily budget to $400.",
"States that single-day overdelivery is designed platform behaviour and that only cumulative deviation counts.",
"Warns that the proposed budget edit would itself force the delivery system to relearn, adding volatility rather than fixing anything.",
"Includes report header fields (campaign, period, budget) and a status line rather than answering in loose prose."
]
},
{
"id": 3,
"prompt": "Monday morning check-in on Ferrostat Systems' LinkedIn lead-gen campaign - we sell B2B industrial sensors. The September budget is $18,000 for the calendar month. Today is Monday September 14 and finalized spend through Sunday the 13th is $6,700, trailing 7-day average $610/day. The account delivers almost entirely on weekdays and we have three full months of delivery history. We also have just 4 leads so far against a 25-lead monthly plan, and our sales cycle means conversions typically report about three weeks late. My quick math says we're 14% behind budget and way behind on leads - should I push bids up today to catch up? Walk me through where we actually stand.",
"expected_output": "A both-curves report showing the flat calendar ratio 0.86 against a business-day ratio 0.91, judging the account on pace on the weighted curve, explaining the Monday calendar-curve artifact, refusing to pace against lagged conversions, and declining the bid increase.",
"files": [],
"expectations": [
"Computes the flat-curve expected-to-date of $7,800 (13 of 30 calendar days) and a flat pacing ratio of approximately 0.86.",
"Computes a business-day expected-to-date of approximately $7,360, from 9 elapsed business days out of 22 in the month.",
"Computes the business-day pacing ratio as approximately 0.91, inside the 0.90-1.10 on-pace band.",
"Presents both curves side by side in one metrics comparison rather than reporting only one.",
"Bases the alert decision on the business-day curve and concludes the campaign is on pace, firing no under-pacing alert.",
"Explains that a weekday-skewed B2B account reads structurally behind on a calendar-day curve after every weekend, which is why the Monday check looks 14% behind.",
"Advises against pushing bids up today to catch up.",
"Refuses to judge pacing on the 4 period-to-date leads, citing the multi-week B2B conversion lag that makes them incomplete by construction, and paces against the spend trajectory instead.",
"Derives the day weights or business-day expectation from the account's own three months of delivery history rather than a generic template.",
"Labels the 0.90-1.10 on-pace band a practitioner convention to recalibrate against this account's history, not a platform rule.",
"Ships a report with a status line and an owner even though the verdict is an all-clear.",
"Reports the required daily spend of approximately $665 over the 17 remaining days and the small corrective figure of roughly +$55/day against the $610 trailing average."
]
},
{
"id": 4,
"prompt": "We're Meridian Outdoors, a DTC camping gear brand. We signed an insertion order with Alpine Media Group: 8 million guaranteed impressions across a six-week flight, October 5 to November 15. We just closed week four and delivery sits at 4.9M impressions, about 1.225M a week. Alpine never said a word about being behind - our analyst caught it. Their account rep just offered us a credit for whatever ends up undelivered. Taking the money seems clean and easy. Should we accept, and how should we handle the rest of the flight?",
"expected_output": "An IO under-delivery response that ranks accelerate ahead of make-good ahead of credit, recommends acceleration to roughly 1.55M impressions/week while runway remains, cites the IAB/4A's make-good and credit terms and the seller's notification duty, and installs a mid-flight IO checkpoint with an owner.",
"files": [],
"expectations": [
"Identifies the guaranteed IO buy type as changing both the target pacing curve and the available remedies, distinct from an auction buy.",
"Notes the standing trader practice of pacing a guaranteed IO slightly ahead of even delivery, so 4.9M against a 5.33M prorated position is genuinely behind for this buy type.",
"Computes the required remaining rate: roughly 3.1M impressions over the final two weeks, about 1.55M/week versus the current 1.225M/week (an acceleration of roughly a quarter to a third).",
"Ranks the three remedies with acceleration first, make-good second, and credit last.",
"Recommends accelerating delivery while runway remains rather than accepting the offered credit.",
"Explains that acceleration is a delivery setting already owned, reversible inside the flight, and triggers no negotiation or contract review.",
"Explains that the credit returns money rather than the audience the campaign was bought for, and closes the flight instead of fixing it.",
"Cites the 4A's/IAB Standard Terms (v3.0) remedy sequence: the parties negotiate a make-good flight, and only if that fails may the buyer take a credit.",
"Cites the IAB Direct Buy Addendum's seller duty to promptly notify the buyer of material under-delivery, so Alpine's silence breached a disclosure obligation.",
"States the escalation condition: the make-good becomes the lead remedy once acceleration can no longer close the gap in the remaining runway.",
"Advises notifying and escalating with the publisher early rather than waiting until the flight ends.",
"Recommends a mid-flight IO delivery checkpoint, states that it outranks the other check cadences on a guaranteed buy because it is contractually load-bearing, and names an owner such as ad ops."
]
},
{
"id": 5,
"prompt": "I handle Meta ads for Juniper Financial. November budget is $9,000 for the calendar month. Eight days ago I raised the daily budget by 18% - I deliberately kept it under the 20% threshold that resets learning. Delivery got choppy anyway, so two days ago I cut it back 15%. This morning, November 11, the dashboard shows $3,850 spent, which by my math is 17% hot. I want to email the client an over-pacing alert today and probably make one more downward budget edit to rein it in. Can you write up the alert and tell me how big the cut should be?",
"expected_output": "A response that debunks the 20% learning-reset figure as undocumented folklore, suppresses the over-pacing alert because two budget edits landed inside the relearning window and the figure is intra-day, ships the report with the suppression reason, and advises against a third edit.",
"files": [],
"expectations": [
"Corrects the 20% claim: the figure appears in no Meta documentation and is folklore; Meta's actual wording ties reset risk to the unquantified magnitude of the change.",
"Does not endorse keeping edits under 20% as a documented-safe pattern, while allowing that treating large edits cautiously is sound risk management.",
"Withholds the over-pacing client alert because the two recent budget edits landed inside the relearning window, so the post-edit volatility is the edits, not a pacing problem.",
"Flags that the $3,850 figure is intra-day: no alert should fire on this morning's live dashboard numbers, which lag and get restated; yesterday's finalized figures are the basis.",
"Computes the ratio of approximately 1.17 from $3,850 against the $3,300 expected by day 11, but reports it as suppressed rather than as an actionable over-pacing alert.",
"Advises waiting out the settle window before judging pacing on this account.",
"Advises against the third corrective edit now, because correcting through a relearning window makes the correction's own volatility read as a new anomaly inviting yet another correction.",
"Still ships a report with the suppression reason recorded rather than replying with either the requested alert or nothing.",
"Notes the pacing record is not immutable - spend gets restated and invalid-traffic credits can move history - so figures should be date-stamped and re-pulled before any escalation.",
"Frames any eventual correction as the smallest reversible change: one variable, a modest step, edits bundled rather than dripped.",
"Does not draft or recommend sending a client-facing over-pacing alert today."
]
},
{
"id": 6,
"prompt": "Our agency, Calder & Moss, runs paid social for Bexley Home under a contract that commits us to spending the full $40,000 October media budget - a hard commitment, the client is billed for it either way. Through October 25 we've spent $26,000, and the trailing 7-day average is $1,050/day. My plan: push the daily budget to $2,400/day for the final six days, which by my math lands us almost exactly on $40k. Sanity-check the math and the plan before I set it tomorrow.",
"expected_output": "A report that verifies the arithmetic (required daily ~$2,333, projection ~$32,240, adjust +$1,283/day) but rejects the end-of-period dump as a failed pace, citing the worst-inventory cost, the final-week ~5pp criterion, the 95-105% utilization band, and the relearning cost of one cliff edit, then recommends an immediate ramp as a change packet with an owner.",
"files": [],
"expectations": [
"Computes the required daily spend as approximately $2,333 over the 6 remaining days, confirming the user's $2,400 figure is arithmetically close.",
"Computes the projected period spend of approximately $32,240 (roughly 81% utilization) if nothing changes.",
"Reports the corrective figure of approximately +$1,283/day against the $1,050 trailing 7-day average.",
"Does not simply validate the plan: warns that an end-of-period spend dump buys the worst inventory at the worst prices.",
"States that a period landing on budget via a last-days surge is a failed pace that hit its number.",
"Cites the no-dump success criterion: final-week spend share within about 5 percentage points of the expected curve's share.",
"References the 95-105% utilization band for a hard-commitment budget, labelled a convention, noting a smoother ramp landing inside the band can beat hitting exactly $40,000 via a dump.",
"Warns that the single large budget jump itself forces delivery relearning, and recommends starting the increase immediately with daily recomputation of the required daily and corrective figures so the correction stays continuous instead of a cliff.",
"Shapes the recommendation as a change packet with current and proposed values, rationale, a verification date, and a rollback trigger.",
"Names an owner and hands off, rather than executing or promising to execute the budget change.",
"Notes that the $40,000 commitment is reconciled at period end on billed cost, not served cost."
]
}
],
"trigger_queries": [
{ "query": "Is our Google Ads campaign on pace to spend its $12k budget by end of month?", "should_trigger": true },
{ "query": "We're 60% through the month but the campaign has only spent 40% of its budget - what do I do?", "should_trigger": true },
{ "query": "What's our projected month-end spend on Meta if nothing changes?", "should_trigger": true },
{ "query": "My LinkedIn campaign keeps underspending its budget, is that a problem?", "should_trigger": true },
{ "query": "Set up a burn rate check on our paid search account", "should_trigger": true },
{ "query": "The flight ends Nov 15 and we've only delivered half the insertion order - help", "should_trigger": true },
{ "query": "How far ahead or behind plan is our ad spend right now?", "should_trigger": true },
{ "query": "Facebook spent almost double the daily budget yesterday, should I panic?", "should_trigger": true },
{ "query": "I need a weekly digest showing which campaign budgets are running hot or cold", "should_trigger": true },
{ "query": "Are we going to hit the $50k media commitment by the end of the quarter?", "should_trigger": true },
{ "query": "What should a spend-vs-budget alert actually fire on?", "should_trigger": true },
{ "query": "My boss wants to know if the campaign will use up its budget before the 30th", "should_trigger": true },
{ "query": "TikTok campaign is overspending, do I cut the budget now or wait it out?", "should_trigger": true },
{ "query": "What daily spend do we need from tomorrow to land this flight exactly on budget?", "should_trigger": true },
{ "query": "Our vendor dashboard says pacing is 112% - is that bad?", "should_trigger": true },
{ "query": "An underspend alert fired on our DSP this morning, is it real or noise?", "should_trigger": true },
{ "query": "How do I tell whether a budget deviation is worth acting on?", "should_trigger": true },
{ "query": "We always end up dumping the leftover budget in the last week of the month, how do we stop that?", "should_trigger": true },
{ "query": "Compare actual campaign spend to where it should be by day 20", "should_trigger": true },
{ "query": "New search campaign barely spent anything in its first 3 days, is something broken?", "should_trigger": true },
{ "query": "Check whether the October ad budget will actually get used up", "should_trigger": true },
{ "query": "The client retainer includes $30k of media a month - I need to prove we're spending it evenly", "should_trigger": true },
{ "query": "Campaign spend is lumpy - some days double, some days nothing. Normal?", "should_trigger": true },
{ "query": "Am I going to blow through the quarterly ad budget early at this rate?", "should_trigger": true },
{ "query": "Catch under-delivery on our guaranteed IO before the flight closes", "should_trigger": true },
{ "query": "How much should we adjust daily spend to get back on track for the month?", "should_trigger": true },
{ "query": "Our B2B account looks behind plan every Monday morning - what's up with that?", "should_trigger": true },
{ "query": "Build me a morning pacing check routine for the ad account", "should_trigger": true },
{ "query": "Did we really overspend the campaign budget or is that just how the platform delivers?", "should_trigger": true },
{ "query": "The media plan promised even delivery but actual spend is all over the place", "should_trigger": true },
{ "query": "Should I worry that the campaign has spent only 60% of budget with 5 days left?", "should_trigger": true },
{ "query": "I need a spend-versus-budget slide for the client QBR next week", "should_trigger": true },
{ "query": "Mid-flight numbers say we'll finish 20% under the committed spend - options?", "should_trigger": true },
{ "query": "Keep an eye on the Google Ads budget so month-end doesn't surprise anyone", "should_trigger": true },
{ "query": "How should I split $60k across Google, Meta, and LinkedIn next quarter?", "should_trigger": false },
{ "query": "Set a maximum allowable CAC and a kill-switch threshold for our paid media", "should_trigger": false },
{ "query": "Our winning Meta campaign is ready to scale - how fast can we ramp the budget without breaking it?", "should_trigger": false },
{ "query": "Is a $210 CAC acceptable for a $79/month SaaS product?", "should_trigger": false },
{ "query": "Should we move from manual CPC to target ROAS bidding on this account?", "should_trigger": false },
{ "query": "Why did our ROAS drop 40% over the last two months?", "should_trigger": false },
{ "query": "Meta reports 120 conversions, GA4 shows 70, the CRM has 55 - reconcile these", "should_trigger": false },
{ "query": "Verify our conversion pixel fires exactly once before launch", "should_trigger": false },
{ "query": "Which of our 30 campaigns should we merge to escape learning limited?", "should_trigger": false },
{ "query": "Is this ad creative wearing out or is the auction just pricier now?", "should_trigger": false },
{ "query": "Design a creative test plan with per-cell budgets for four new concepts", "should_trigger": false },
{ "query": "Mine our search terms report and build negative keyword lists", "should_trigger": false },
{ "query": "Which paid channels fit a $5k/month budget for a B2C mobile app?", "should_trigger": false },
{ "query": "Design a retargeting ladder with per-stage frequency caps", "should_trigger": false },
{ "query": "Which customers should seed our lookalike audience?", "should_trigger": false },
{ "query": "Audit the landing page our paid traffic goes to", "should_trigger": false },
{ "query": "What monthly ad budget should we set for the new product launch?", "should_trigger": false },
{ "query": "How much of the marketing budget should go to brand versus performance?", "should_trigger": false },
{ "query": "Alert me whenever campaign CPA goes above $80", "should_trigger": false },
{ "query": "Forecast next year's ad spend for the finance planning cycle", "should_trigger": false },
{ "query": "Our AWS bill is tracking 30% over the monthly cloud budget - set up cost alerts", "should_trigger": false },
{ "query": "Track my personal monthly budget and flag when I overspend on groceries", "should_trigger": false },
{ "query": "Are we burning through the startup's runway too fast?", "should_trigger": false },
{ "query": "Sprint burndown shows we're behind pace - help me replan the sprint", "should_trigger": false },
{ "query": "Keep the engineering project on schedule and flag when milestones slip", "should_trigger": false },
{ "query": "Pace my marathon training so I can break four hours", "should_trigger": false },
{ "query": "How should I pace content publishing across the quarter?", "should_trigger": false },
{ "query": "We're about to exceed our email platform's monthly sending quota - manage it", "should_trigger": false },
{ "query": "Draft the make-good clause for our podcast sponsorship contract", "should_trigger": false },
{ "query": "Why is the campaign stuck in learning limited and what bid change fixes it?", "should_trigger": false },
{ "query": "Build next year's media plan with a month-by-month budget breakdown", "should_trigger": false },
{ "query": "Rebalance spend between our five channels against the shared quarterly budget", "should_trigger": false },
{ "query": "My Google Ads account was suspended for policy violations - get spend running again", "should_trigger": false },
{ "query": "Estimate the budget we'd need to reach 10,000 installs next month", "should_trigger": false }
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |