mbfinotti/advertising-skills / skills/ad-spend-guardrails
ad-spend-guardrails
VerifiedSet the organisation's top-level paid-media spend guardrails as written policy - maximum allowable CAC, minimum ROAS/MER floor, kill-switch thresholds, counter-metrics, who owns them and who may override them - each derived from contribution margin, payback, and cash runway rather than inherited from a dashboard. Use whenever the user asks what CAC they can afford, mentions a ROAS floor, spend guardrails, a kill switch, when to stop spending, or who approves a budget increase - even if they never say 'guardrails'. Covers B2B and B2C. Do NOT use to judge whether current CAC/ROAS is actually good (mbfinotti/advertising-skills@cac-roas-benchmark) or to monitor daily pacing (mbfinotti/advertising-skills@ad-budget-pacing).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 31.0 KB |
| evals/evals.json | config | 25.5 KB |
| references/worked-guardrail-policies.md | markdown | 10.6 KB |
evals/evals.json
View on GitHub{
"skill_name": "ad-spend-guardrails",
"evals": [
{
"id": 1,
"prompt": "I run Maribel Home Goods, a DTC home fragrance brand. AOV is $68 and our contribution margin after COGS and shipping is 45%. We spend about $60K/month on Meta and Google. Our CFO asked me for an official ROAS target to put in the annual plan - everyone online says 4x is the standard to aim for. Can you write up the target for us?",
"expected_output": "A guardrail derivation from the company's own 45% margin, with 4x named as folklore, three separate threshold layers with distinct consequences, a marginal scaling ceiling, a cash cap question, and a counter-metric pairing - not a single benchmark-quoted ROAS number.",
"files": [],
"expectations": [
"Derives break-even ROAS from the stated margin as 1 divided by 0.45, roughly 2.2x, rather than adopting 4x.",
"Names 4x ROAS as folklore with no traceable author, not a measured standard.",
"Explains that 4x is simply break-even at a 25% contribution margin retroactively declared a target.",
"Keeps the 4x rule visible next to the business's own break-even instead of endorsing it or silently deleting it.",
"Proposes three distinct numbers: a break-even floor, a target floor, and a hard floor / kill-switch level.",
"Assigns each layer its own consequence: stop always at break-even, investigate at target, automatic halt plus escalation at the hard floor.",
"Warns that publishing a single ROAS number gets read as all three layers at once, producing both over-reaction to one bad day and tolerated slow bleeds.",
"States break-even allowable CAC as contribution per order, about $30.60 ($68 x 45%).",
"Asks for cash runway and burn, or states a cash cap as an absolute monthly spend number that binds regardless of efficiency.",
"Recommends the scaling ceiling be set on marginal efficiency, with the blended figure reserved for the monthly report.",
"Asks which ROAS variant is meant, or warns against setting the guardrail on platform-reported ROAS in favour of business-level outcomes.",
"Asks clarifying interview questions, including what guardrails already exist, before finalizing numbers rather than delivering a finished target immediately.",
"Pairs the proposed ROAS/MER floor with a counter-metric such as new-customer share to expose retargeting and branded-search gaming."
]
},
{
"id": 2,
"prompt": "We're Kestrel Data, B2B SaaS, $24K ACV at 62% gross margin, average sales cycle around 75 days. Cost per SQL on LinkedIn doubled over the past two weeks and our CMO wants an automatic rule in place: any channel that runs above 3x our target CPA for three days straight gets shut off. Can you write that rule up properly so we can put it in our ops doc?",
"expected_output": "A kill-switch design that rejects the three-day window as inside the conversion lag, flags 3x-CPA as untraceable folklore, and delivers streak plus rate conditions, an evidence gate, a written restart condition, three outcomes, pipeline-stage evidence, and a derived allowable CAC.",
"files": [],
"expectations": [
"Refuses a three-day kill window as shorter than the conversion lag, setting a minimum evidence window of 4-6 weeks or longer given the 75-day cycle.",
"Explains that cost per SQL or CAC read on a short window counts this period's spend against an earlier period's customers, so the two-week spike may be lag rather than economics.",
"Flags the 3x-CPA kill rule as untraceable folklore and declines to present it as a benchmark.",
"Anchors any spend-based gate to attributed practitioner guidance (such as no activation by $500-1,000 of spend, or 3-4x CPA of spend before judging), labeled as guidance rather than measurement.",
"Designs two independent halt conditions: a consecutive-period streak condition and a budget-burn rate condition, either firing alone.",
"Includes both a per-period cap and a rolling cumulative cap so a slow bleed inside daily tolerance still trips.",
"Adds an evidence gate requiring both a minimum data window and a minimum spend or conversion volume before any kill is allowed.",
"Writes the restart condition alongside the halt condition: what must be true, over what window, approved by whom.",
"Routes breaches into three outcomes - allow, review, halt - instead of forcing every breach into an immediate stop.",
"Keys the kill evidence on pipeline-stage signals such as SQL-to-closed-won, never raw lead volume.",
"Derives allowable CAC from contribution per deal, about $14,880 ($24,000 x 62%), instead of accepting the 3x-of-target framing as the ceiling.",
"Names a kill-decision owner and escalation path outside the team spending the money.",
"Specifies fail-closed handling: missing, stale, or broken data holds spend flat and blocks scaling, and is never treated as the number being fine."
]
},
{
"id": 3,
"prompt": "Torvale Supplements here - 70% gross margin. We're at $110K/month on Meta with a blended MER of 2.0. Our agency points out that break-even at our margin is about 1.4, so they say we've got tons of headroom and want to push to $150K next month. Before I approve it I want a proper guardrail written down for scaling decisions. What should it be?",
"expected_output": "A scaling guardrail set on marginal MER rather than the blended 2.0, explaining that a passing average can hide marginal spend below break-even, with three layers, a counter-metric, a cash cap, and ceiling ownership outside the agency.",
"files": [],
"expectations": [
"Sets the scaling ceiling on marginal MER/ROAS, not on the blended 2.0 figure.",
"Explains that a passing blended average can hide marginal spend below break-even, so the last dollars of the budget may already lose money while the average looks healthy.",
"Computes break-even near 1.43x from the 70% margin (1 divided by 0.70) and treats it as the floor for the marginal number.",
"Distinguishes the two roles: the marginal number authorizes the next dollar of spend, the blended number belongs in the monthly report.",
"Declines to approve the $150K step on the blended figure alone and requires a marginal-efficiency read (such as MER on the last tranche of spend) as the scaling gate.",
"Structures the policy as three layers with three separate consequences rather than a single floor.",
"Pairs the MER guardrail with a counter-metric such as new-customer share of orders.",
"Caps the guardrail set at two or three metrics.",
"Asks for runway and burn, or states an absolute monthly cash cap next to the efficiency floors.",
"Places ceiling ownership outside the agency spending the money, on separation-of-duties grounds.",
"Includes a re-baselining cadence (quarterly) plus named event triggers such as margin, pricing, or measurement changes.",
"Shows the arithmetic behind every threshold so a finance reader can audit it."
]
},
{
"id": 4,
"prompt": "Plumeria Skincare. Honestly we don't know our contribution margin precisely - somewhere between 50 and 60% probably? Also Meta reports about 40% more revenue than Shopify does, and we never figured out why. We just need a sensible CAC ceiling and a ROAS floor to start operating with - nothing fancy, just give us starter numbers.",
"expected_output": "A refusal to hand over starter numbers: margin is named as unconfirmed, the 40% measurement gap gates the exercise, no guardrail is set on platform-reported ROAS, and any interim figure is derived, labeled provisional, and sourced from business-level outcomes.",
"files": [],
"expectations": [
"Declines to fill the unknown margin with a plausible number, naming it estimated or missing and giving any policy a provisional status.",
"Gates on measurement: the 40% platform-versus-store revenue gap must be resolved before guardrails are set on that feed.",
"Refuses to set a kill-switch or floor on platform-reported ROAS while the conversion feed is untrusted.",
"Explains why: a guardrail on an untrusted metric fires on data-quality noise and manufactures confident wrong decisions.",
"Asks how confident the business is in its margin (a guess, finance-reviewed, or per-SKU) or otherwise interviews to pin the input down.",
"Does not substitute a published benchmark (4x ROAS, 3:1 LTV:CAC, 12-month payback) as the starter number.",
"Any interim number offered shows its derivation and is labeled provisional or estimated, never presented as measured.",
"Recommends business-level accepted outcomes (store orders or CRM) as the guardrail data source rather than platform claimed revenue.",
"Notes that platform numbers report claimed rather than caused revenue and push spend toward retargeting and brand search.",
"Specifies fail-closed behavior while the feed is broken: hold spend flat rather than scale.",
"Labels inputs measured, estimated, or missing in any drafted policy skeleton.",
"Asks the user questions before proposing thresholds instead of assuming the missing facts."
]
},
{
"id": 5,
"prompt": "At Bramwell Software our Head of Growth wrote our ad spend rules last year: she set the CAC ceiling at $310, she approves any overage herself, and we haven't breached it once in three quarters, so the rules clearly work. Our CFO wants the whole thing formalized into an official policy before the next board meeting. Can you turn what we have into the formal version? Anything worth adjusting while we're at it?",
"expected_output": "A governance rewrite that moves ceiling ownership away from the spender, treats three zero-breach quarters as a review trigger rather than proof of success, audits the $310 derivation, adds an escalation ladder with named approvers, a logged exception process, and policy-level KPIs.",
"files": [],
"expectations": [
"Flags that the Head of Growth both spends the budget and approves her own overages, and moves ceiling ownership or approval to a separate role.",
"States the principle: whoever spends the money cannot raise their own ceiling, otherwise it is a preference rather than a control.",
"Treats three zero-breach quarters as a review trigger for a sandbagged or mis-set ceiling, not as evidence the rules work.",
"Checks headroom: persistent distance between actual efficiency and the $310 ceiling would mean the ceiling is throttling profitable growth or was set too loose.",
"Audits how the $310 ceiling was derived and requires it traced to contribution margin, payback, or cash rather than accepting it as-is.",
"Requires an escalating approval ladder by severity, each tier naming a real, notified person.",
"Rewrites exceptions as explicit, time-boxed, justified, and logged, including denied ones, and calls out standing self-approval as a new ceiling nobody agreed to.",
"Rejects vague override rationales such as 'timing' or 'one-time' as insufficient justification.",
"Splits the single $310 ceiling into break-even, target, and hard floors, each with its own consequence.",
"Adds a re-baselining cadence (quarterly) plus named event triggers such as pricing, margin, or measurement changes.",
"Proposes judging the policy itself with KPIs read off the breach log, such as breach response rate, override concentration, headroom, or zero-breach quarters.",
"Ends with an explicit approval gate: nothing finalized without sign-off, recording who approved the policy and when."
]
},
{
"id": 6,
"prompt": "Ostrena, we sell DTC coffee gear, roughly $85K/month across Meta and Google. Two years ago we put a strict 2.8x ROAS bar on absolutely everything, and our media buyer's complaint is that we haven't successfully launched a new channel or audience since - every new thing dies within a week of launch. We do have an in-house analyst who already tracks marginal returns weekly. Time to rework our spend rules. What should they look like?",
"expected_output": "An explicit brainstorming pass over the three guardrail architectures with the ranking said out loud, the portfolio model promoted because the efficiency bar strangled testing and the analyst collapses its effort cost, a ring-fenced exploration budget with spend-based rules, and a re-derived break-even replacing the unexamined 2.8x.",
"files": [],
"expectations": [
"Presents all three guardrail architectures - single break-even floor, tiered ladder, and portfolio with ring-fenced exploration - before drafting numbers.",
"States the ranking out loud across axes (efficiency, value in false stops avoided and learning kept, effort) rather than presenting one option.",
"Promotes the portfolio model above its default rank because the efficiency bar has already strangled testing.",
"Uses the in-house analyst who already tracks marginal returns to argue the portfolio model's effort cost collapses for this account.",
"Ring-fences an exploration budget as a declared share of spend with its own separate kill rules, exempt from the main floor.",
"Gives exploration tests spend-based judgment rules (hypothesis, decision date, spend cap) instead of the production 2.8x bar.",
"Names the failure mode explicitly: testing held to the production efficiency bar quietly stops testing.",
"Asks where the 2.8x figure came from and re-derives break-even from the business's own margin, asking for the margin if unknown, rather than keeping 2.8x unexamined.",
"Flags that one flat threshold across all channels and audiences starves prospecting, which always looks worse than retargeting.",
"Argues the strongest case against its own recommended architecture before presenting it.",
"Waits for the user's choice of architecture rather than unilaterally imposing one.",
"Asks whether the mandate is a one-off fix or a compounding asset, and what effort ceiling exists for a standing review, before or while ranking.",
"Pairs whatever efficiency guardrail replaces the 2.8x bar with a counter-metric that exposes gaming."
]
},
{
"id": 7,
"prompt": "Two-founder bootstrapped SaaS called Lanternfish HQ. One plan at $49/month, 80% gross margin, about 9 new customers a month from ads on roughly $400/month spend, 15 months of runway. An investor friend told me our CAC payback needs to be under 5 months because that's what his portfolio companies target. What CAC ceiling should we set?",
"expected_output": "A refusal to set a hard CAC ceiling at this volume, replaced by an activation threshold, with payback derived from monthly gross profit, the investor's rule rejected via cost-of-capital reasoning, a cash cap, and a single-floor architecture given no second approver exists.",
"files": [],
"expectations": [
"Flags roughly 9 conversions a month as below meaningful volume and declines to set a hard CAC ceiling now.",
"Sets an activation threshold instead: a spend level or conversion count at which the CAC policy switches on.",
"Computes monthly gross profit per customer as about $39.20 ($49 x 80%) and frames payback as CAC divided by monthly gross profit.",
"Asks for or accounts for retention to churn-adjust payback (CAC divided by monthly gross profit times annual retention).",
"Declines to inherit the investor's under-5-month rule as this business's target.",
"Explains payback tolerance through cost of capital rather than stage labels or someone else's portfolio.",
"Notes that a bootstrapped business facing near-zero capital cost can sustain a longer payback, up to around 24 months where the math supports it, while venture-funded companies face roughly 35-50% implied equity cost.",
"Notes that payback under about 3 months usually signals underinvestment rather than health.",
"States a cash cap as an absolute monthly number derived from the 15-month runway, sitting next to any efficiency guidance.",
"Shows the arithmetic behind every number proposed so it can be audited.",
"Labels inputs measured, estimated, or missing rather than guessing the gaps.",
"Does not adopt 3:1 LTV:CAC or a 12-month payback rule as the answer; any such rule mentioned is labeled a heuristic with its origin.",
"Recommends the single hard-floor architecture, or names the escalation ladder as deleted, because a two-founder account has no second approver or review chair."
]
}
],
"trigger_queries": [
{ "query": "What's the maximum CAC we can afford before ads lose us money?", "should_trigger": true },
{ "query": "Help me set a ROAS floor for our paid campaigns", "should_trigger": true },
{ "query": "We need a kill switch rule for when to stop ad spend", "should_trigger": true },
{ "query": "Who should be allowed to approve going over our CAC target?", "should_trigger": true },
{ "query": "My CFO wants a written policy for ad spend limits", "should_trigger": true },
{ "query": "At what point should we just turn the ads off?", "should_trigger": true },
{ "query": "Set spend guardrails for our Meta and Google accounts", "should_trigger": true },
{ "query": "How do I figure out what CAC target to give my agency?", "should_trigger": true },
{ "query": "Is 3:1 LTV to CAC the right target for us to adopt?", "should_trigger": true },
{ "query": "Our agency wants to double the budget - what rule decides whether they're allowed?", "should_trigger": true },
{ "query": "Write a policy for when we pause a campaign and who signs off", "should_trigger": true },
{ "query": "How much can we pay for a customer at 55% margin?", "should_trigger": true },
{ "query": "What payback period should we tolerate on ad spend as a bootstrapped company?", "should_trigger": true },
{ "query": "Define the threshold where marketing has to stop spending without asking anyone", "should_trigger": true },
{ "query": "We keep arguing about whether our CPA target should be 40 or 60 dollars - help us set it properly", "should_trigger": true },
{ "query": "I want a break-even ROAS calculation for our store", "should_trigger": true },
{ "query": "What should our MER floor be?", "should_trigger": true },
{ "query": "Boss asked me to write the rules for when we cut ad spend", "should_trigger": true },
{ "query": "Put together spend limits the finance team can sign off on", "should_trigger": true },
{ "query": "When performance tanks, who decides to pull the plug? We need a process", "should_trigger": true },
{ "query": "Need a rule for when a campaign gets killed versus just reviewed", "should_trigger": true },
{ "query": "What counter-metrics should sit next to our ROAS target so the team can't game it?", "should_trigger": true },
{ "query": "Our board wants a max CAC number - how do I derive one?", "should_trigger": true },
{ "query": "Set an exploration budget that's exempt from our efficiency targets", "should_trigger": true },
{ "query": "How far above break-even should our target ROAS sit?", "should_trigger": true },
{ "query": "At 30% margin, what ROAS do we actually need?", "should_trigger": true },
{ "query": "Draft the escalation path for ad spend overruns", "should_trigger": true },
{ "query": "We're burning cash - what monthly ad budget cap makes sense given 10 months of runway?", "should_trigger": true },
{ "query": "My cofounder and I disagree on when to stop the ads, settle it with a rule", "should_trigger": true },
{ "query": "Help me decide what CAC is too high for a $29/month product", "should_trigger": true },
{ "query": "We paused everything after one bad week and it wrecked the account - how do we avoid that next time?", "should_trigger": true },
{ "query": "Formalize our ad spend rules so the media buyer isn't grading his own homework", "should_trigger": true },
{ "query": "What's an acceptable customer acquisition cost for us?", "should_trigger": true },
{ "query": "The CEO wants one number: spend stops when ROAS hits X. Give me X", "should_trigger": true },
{ "query": "How do I set a CPA ceiling that accounts for our 90-day sales cycle?", "should_trigger": true },
{ "query": "Our ads are profitable on average but I'm scared we're overspending at the margin - where should the ceiling be?", "should_trigger": true },
{ "query": "When is it OK to restart a channel we shut down for bad performance?", "should_trigger": true },
{ "query": "Should the testing budget follow the same ROAS bar as everything else?", "should_trigger": true },
{ "query": "Give me a spend policy template our CFO and media buyer can both live with", "should_trigger": true },
{ "query": "12-month payback keeps getting quoted at me - is that the right bar for us?", "should_trigger": true },
{ "query": "We're venture backed, Series A - how aggressive can our CAC payback target be?", "should_trigger": true },
{ "query": "Define what counts as an emergency stop for paid media and who owns it", "should_trigger": true },
{ "query": "I don't trust the 4x ROAS rule - what should we use instead?", "should_trigger": true },
{ "query": "Is a 2.5x ROAS good for ecommerce?", "should_trigger": false },
{ "query": "Our CAC jumped from $80 to $140 last month - why?", "should_trigger": false },
{ "query": "Are we on pace to spend our $50K budget this month?", "should_trigger": false },
{ "query": "Should I switch my Google campaign to target ROAS bidding?", "should_trigger": false },
{ "query": "What target CPA should I enter in the Google Ads bid strategy settings?", "should_trigger": false },
{ "query": "Our campaign is proven at $200/day - how fast can we scale it to $1000/day?", "should_trigger": false },
{ "query": "How should I split $30K between Meta prospecting and retargeting?", "should_trigger": false },
{ "query": "Meta says 210 conversions but Shopify shows 150 - which is right?", "should_trigger": false },
{ "query": "Check whether our conversion pixel fires correctly before launch", "should_trigger": false },
{ "query": "Which platform should we advertise on with a $10K budget?", "should_trigger": false },
{ "query": "Our ROAS dropped this week - is the creative fatigued?", "should_trigger": false },
{ "query": "Find the search terms wasting our ad spend", "should_trigger": false },
{ "query": "Ads get clicks but nobody converts on the landing page", "should_trigger": false },
{ "query": "We have too many campaigns - which should we merge?", "should_trigger": false },
{ "query": "How do I become a media buyer?", "should_trigger": false },
{ "query": "Interview questions for hiring a performance marketer", "should_trigger": false },
{ "query": "What's our blended CAC for Q3? Here's the spend and order data", "should_trigger": false },
{ "query": "Is my ROAS below industry benchmarks for beauty brands?", "should_trigger": false },
{ "query": "Alert me when daily spend exceeds the daily budget", "should_trigger": false },
{ "query": "Why did spend suddenly double yesterday on Meta?", "should_trigger": false },
{ "query": "Set frequency caps for our retargeting sequence", "should_trigger": false },
{ "query": "How big does our lookalike seed list need to be?", "should_trigger": false },
{ "query": "Write guardrail metrics for our A/B test so we don't ship a bad variant", "should_trigger": false },
{ "query": "What guardrails should we put on our LLM agent's tool use?", "should_trigger": false },
{ "query": "Set up AWS budget alerts so our cloud spend doesn't blow up", "should_trigger": false },
{ "query": "I need a kill switch for our feature flags if error rates spike", "should_trigger": false },
{ "query": "Should we pause the campaign during the learning phase reset?", "should_trigger": false },
{ "query": "What's a fair monthly retainer to pay our PPC agency?", "should_trigger": false },
{ "query": "Our MER was 3.1 last month - healthy or not?", "should_trigger": false },
{ "query": "Diminishing returns: which campaign gets the extra $5K?", "should_trigger": false },
{ "query": "Track our burn rate against the quarterly media budget", "should_trigger": false },
{ "query": "When should I move from manual CPC to automated bidding?", "should_trigger": false },
{ "query": "My cost per lead doubled after the iOS update - diagnose it", "should_trigger": false },
{ "query": "Build a stop-loss rule for my day trading account", "should_trigger": false },
{ "query": "What LTV:CAC ratio do VCs want to see in a pitch deck?", "should_trigger": false },
{ "query": "Estimate CAC payback for the board deck from these cohort numbers", "should_trigger": false },
{ "query": "Our exec wants a weekly spend dashboard - what should be on it?", "should_trigger": false },
{ "query": "How often should we review our negative keyword lists?", "should_trigger": false },
{ "query": "Is $45 CPA too high for B2C subscription apps?", "should_trigger": false },
{ "query": "Which campaigns are stuck in learning limited and should be merged?", "should_trigger": false },
{ "query": "Compare LinkedIn versus Google Ads for B2B lead gen", "should_trigger": false },
{ "query": "Draft brand safety guardrails for where our ads can appear", "should_trigger": false },
{ "query": "We're raising our Meta budget 20% tomorrow - will it reset learning?", "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: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |