Skip to content

mbfinotti/advertising-skills / skills/ad-account-diagnostic

ad-account-diagnostic

Verified

Diagnose the root cause of an underperforming paid ad account - why the ads stopped working, why CPA went up, why ROAS dropped - instead of defaulting to 'increase the budget'. Weighs tracking, account structure, targeting, creative, bidding and budget, offer, and external forces, and returns a prioritised verdict with evidence and confidence. Covers B2B and B2C on search, paid social, video, and native. Use whenever the user mentions an ad account audit, a campaign structure review, wasted ad spend, rising cost per lead, or says their ads used to work - even if they never say 'diagnostic'. Diagnosis only, and it stops at the click: post-click page problems are mbfinotti/advertising-skills@paid-landing-page-audit and creative decay is mbfinotti/advertising-skills@ad-creative-fatigue.

FileKindSize
SKILL.mdskill md31.8 KB
evals/evals.jsonconfig39.5 KB
references/examples.mdmarkdown11.3 KB
references/layer-evidence.mdmarkdown8.1 KB
references/metric-decomposition.mdmarkdown7.1 KB

evals/evals.json

View on GitHub
{
  "skill_name": "ad-account-diagnostic",
  "evals": [
    {
      "id": 1,
      "prompt": "We run Velora Skin, a DTC skincare brand doing about $45K/month on Meta. Our ROAS fell from 2.9 to 1.6 over the last 12 days and the whole team agrees the creatives are burnt out - they are 9 weeks old and we have been meaning to refresh anyway. Can you confirm the fatigue read and help us decide which ads to kill first? Data from the last 12 days vs our 60-day baseline: CPM +3%, CTR -2%, reported CVR -38%. The drop shows up in every campaign - cold, retargeting, even brand - all starting the same Tuesday. Meta reported 348 purchases in the window; our Shopify order table shows 645 paid-attributed orders, and revenue is only about 5% below normal (the gap between Meta and Shopify normally runs around 8%). We also migrated checkout to a new subdomain that same week. Budget unchanged.",
      "expected_output": "A diagnosis that refuses the creative-fatigue read, reconciles platform vs backend first, records a tracking FAIL from the ~46% reconciliation gap tied to the checkout migration, screens every layer with four states, and hands the fix to a conversion-tracking workflow with a prediction and re-check date.",
      "files": [],
      "expectations": [
        "Compares Meta-reported purchases against the Shopify order figures (reconciliation) before diagnosing any other layer.",
        "Identifies the reported-vs-backend gap (roughly 46%, against the ~8% historical norm) as beyond the roughly-40% stop threshold and records a measurement/tracking FAIL.",
        "The verdict names measurement/tracking as the root cause, not creative fatigue.",
        "Declines to confirm the fatigue read and does not recommend killing or refreshing creatives as the fix.",
        "Cites the drop appearing uniformly across cold, retargeting, and brand campaigns on a single start date as a tracking signature, noting fatigue does not synchronise across unrelated audiences on one date.",
        "Connects the break to the checkout migration to a new subdomain in the same week.",
        "Uses the backend evidence (revenue only ~5% down versus a 38% reported CVR drop) to show demand is intact and the signal is broken.",
        "Uses the decomposition (CPM and CTR flat vs the 60-day baseline, CVR the only moved link) to rule out the auction and the ad before naming the cause.",
        "Presents a per-layer screen giving each layer one of four states (pass, FAIL, unknown, not applicable) rather than only naming the winning cause.",
        "Marks the creative layer pass with evidence (CTR flat against its own baseline).",
        "Avoids issuing verdicts on downstream layers through the broken signal, for example marking bidding unknown or deferring it until after the fix.",
        "Hands the tracking repair to a dedicated conversion-tracking fix workflow or owner instead of treating the diagnosis as the fix.",
        "States a prediction: reported CVR and ROAS recover toward baseline within roughly one lag-mature week once the purchase event fires again.",
        "Sets a re-check date one full comparison window (lag-mature) after the fix ships."
      ]
    },
    {
      "id": 2,
      "prompt": "I run growth at NorthPeak Analytics, a B2B data-quality SaaS. We spend about $30K/month on LinkedIn and Google. Our dashboard looks great - CPL is down 28% quarter over quarter to $62 - but sales keeps escalating that the leads are garbage. I pulled the CRM: lead-to-SQL rate went from 12% last quarter to 4% this quarter, worst in exactly the campaigns we shifted budget into. The campaigns optimize to our gated whitepaper form fill, which reconciles fine against the CRM (within a few percent). My plan is to tighten the audience targeting - the broad audiences are probably pulling in junk. Can you audit the account and help me tighten targeting?",
      "expected_output": "A diagnosis that refuses targeting tightening as the first move, names the raw form-fill optimization event as a structure-layer FAIL, judges the account on cost per SQL over B2B-length windows, and puts the CRM-outcome feedback loop at the top of the fix queue with owner, effort, compliance note, and prediction.",
      "files": [],
      "expectations": [
        "Does not adopt targeting tightening as the first fix, identifying the audience drift as a symptom of the optimization event rather than an independent cause.",
        "Names the optimization event (raw whitepaper form fill) as the root cause, recorded as a structure-layer FAIL.",
        "Explains the platform is doing exactly what it was asked: finding people who fill forms cheaply, in volume.",
        "Judges the account on cost per SQL (or cost per closed-won) rather than CPL, showing cost per SQL rose while CPL fell.",
        "Uses the CRM join (12% to 4% lead-to-SQL) as the carrying evidence, with the form-fill reconciliation noted as passing tracking.",
        "Uses the concentration of the SQL-rate collapse in the campaigns that received the shifted spend as localisation evidence.",
        "The top-ranked fix is feeding CRM outcomes (SQL or closed-won) back to the platforms and optimizing to a qualified event, ahead of any targeting change.",
        "Evaluates over B2B-length windows (roughly 90-day or 4-6 week minimum reads), not week-over-week.",
        "Flags that pushing CRM outcomes into ad platforms triggers a consent and data-processing review before the wiring ships.",
        "Presents the per-layer screen with four states; targeting is not marked FAIL as an independent cause.",
        "Predicts the post-fix shape: CPL rises while the lead-to-SQL rate and cost per SQL recover, over one to two mature windows.",
        "Assigns an owner and an order-of-magnitude effort to the top fix (roughly a couple of days of marketing-ops/CRM wiring).",
        "Recommends no budget increase and defers any targeting redesign until the event fix has been judged at maturity."
      ]
    },
    {
      "id": 3,
      "prompt": "Harbor & Finch is a two-partner immigration law firm. We run Google Ads at about $7K/month and normally get 10-12 consultation requests a week. Last week we got 6. Nine days ago we raised the daily budget 50% because we wanted more volume. We have no access to the CRM data right now (the office manager owns it and is on leave). My partner wants to switch the bidding to manual CPC today, or alternatively double the budget to compensate for the drop. Which of the two should we do? We need a decision today.",
      "expected_output": "A refusal to pick either fix: an insufficient-evidence verdict citing the learning reset from the +50% edit, attribution-lag immaturity, and sub-noise conversion volume, with gate math for what clears it, an edit freeze, unknown layer states, low confidence due to unverified reconciliation, and a mature-window re-check date.",
      "files": [],
      "expectations": [
        "The verdict is insufficient evidence: no root-cause layer is named on this data.",
        "Refuses both proposed moves (the manual-CPC switch and the budget doubling) rather than picking one of them.",
        "Identifies the +50% budget change nine days ago as a significant edit that reset the learning phase.",
        "Explains that the most recent week under-reports because of attribution lag, so a trailing window looks like decline by construction.",
        "Notes that roughly 6 conversions is far below any read that clears the noise band, and below the ~30-conversion evaluation reference for automated bidding.",
        "States the gate math: roughly how many more days or conversions are needed at current volume before a verdict is possible.",
        "Recommends freezing further edits until a lag-mature window has accumulated.",
        "Issues no quantified performance prediction on this data, saying why.",
        "Sets a re-check date at a mature window, roughly two or more weeks after the edit.",
        "Records reconciliation as unverified due to the missing CRM access and caps stated confidence accordingly (low).",
        "Uses unknown states for the layers this data cannot power, instead of marking them clean.",
        "Recommends obtaining CRM or backend read access before the next diagnostic run.",
        "Explains that 20-50% day-to-day swings during learning are expected volatility, not evidence of a defect."
      ]
    },
    {
      "id": 4,
      "prompt": "I manage paid search for Brightside HVAC, a regional home-services company. Our search impression share fell from 71% to 54% over six weeks and my boss's read is that we are being outspent, so he asked me to model a 40% budget increase. The columns I pulled: Search lost IS (budget) = 4%, Search lost IS (rank) = 42%. CPA is stable at $58, and on 11 of the last 30 days we did not even spend the full daily budget. How much should we raise the budget - is 40% enough, or should we go higher?",
      "expected_output": "A refusal to size a budget raise: the lost-impression-share split shows rank, not budget, is the constraint; the unspent budget corroborates it; a 40% single-step edit would reset learning; the fix points at rank components via handoff, with the condition under which budget would have been the right answer stated.",
      "files": [],
      "expectations": [
        "Does not answer with a budget-increase amount; declines to size a raise on this evidence.",
        "Splits the impression-share loss into lost-to-budget versus lost-to-rank before making any recommendation.",
        "Identifies rank (42% lost-to-rank versus 4% lost-to-budget) as the binding constraint.",
        "States that increasing the budget will not recover impression share lost to rank.",
        "Uses the unspent daily budget (11 of the last 30 days) as corroborating evidence that budget is not the cap.",
        "Notes that a single-step budget increase beyond roughly 20% counts as a significant edit and resets learning.",
        "Points the fix at rank components (bid and quality/relevance), handed to a bidding/quality workflow or owner rather than executing a bid change itself.",
        "Reads the pattern through decomposition first (volume down while efficiency stable means delivery constrained) before naming the layer.",
        "Verifies, or explicitly conditions the bidding read on, measurement/tracking passing first.",
        "Presents the layer screen with the bidding/budget finding carrying the impression-share-split evidence.",
        "States a prediction tied to the rank fix (impression share recovers only if rank improves) with a re-check window.",
        "Names the condition under which budget would have been the right answer (lost-to-budget dominating with efficiency holding at the margin) and shows this data does not meet it."
      ]
    },
    {
      "id": 5,
      "prompt": "We just took over paid social for PetPal Box, a dog-toy subscription box, from another agency. Their handover doc says: 'CPMs are up industry-wide going into Q4, auction inflation, ride it out.' CPA is up 30% and my CEO wants me to confirm the market story in writing. Blended CPM is +34% vs the prior 60 days. When I break it down: our main prospecting ad set (a narrow stacked-interest audience) is +85% CPM with frequency up from 2.1 to 4.8 while unique reach has been flat for a month; the other four ad sets are +2 to +6% CPM. Can you confirm it's external so I can send the note?",
      "expected_output": "A refusal to confirm the market story: the breakdown shows the CPM rise concentrated in one saturated narrow ad set (frequency up, reach flat), which points internal to targeting; external requires uniform elevation and is a diagnosis of exclusion; the corrected note attributes only the small uniform residual to the market.",
      "files": [],
      "expectations": [
        "Declines to confirm the external/market story as written.",
        "Treats the inherited agency narrative as unverified until the data independently reproduces it, rather than as the hypothesis to confirm.",
        "Reads the breakdown rather than the blended +34% account-level average.",
        "Identifies the concentration (one ad set at +85% while siblings sit at +2-6%) as evidence of an internal, targeted cause.",
        "States the rule: external elevation shows up roughly uniformly across every campaign and audience, while concentrated elevation points internal.",
        "Reads frequency rising from 2.1 to 4.8 with flat unique reach as audience saturation.",
        "Names targeting (narrow-audience saturation) as the layer behind the concentrated CPM rise.",
        "Treats external as a diagnosis of exclusion that cannot be claimed while an internal layer FAILs.",
        "Compares against the account's own history rather than category or industry CPM claims.",
        "Runs, or explicitly conditions the verdict on, the tracking/reconciliation check before the targeting call.",
        "Hands the audience redesign to a targeting workflow or owner rather than designing the new audiences inside this diagnosis.",
        "States a prediction (that ad set's CPM and frequency normalise once the audience is broadened or rotated) and sets a re-check date.",
        "Provides the corrected note for the CEO: mostly internal saturation, with at most the small uniform +2-6% residual attributable to the market."
      ]
    },
    {
      "id": 6,
      "prompt": "Our analyst at Cobalt Gear (outdoor equipment ecommerce) built a performance report. He summed conversions from Meta (7-day click), Google Ads (30-day click), and GA4 (last-click) into one total column, and it shows total conversions down 22% this month vs last month. One thing worth mentioning: on the 12th of this month we changed Meta's attribution setting from 7-day click to 1-day click. Based on the report, which campaigns should we kill? I want to cut the bottom 20% this week.",
      "expected_output": "A refusal to kill campaigns off the summed total: summing across differing attribution windows and models is a category error, the mid-month settings change invalidates the comparison and mechanically deflates the number, sources must be reported side by side and reconciled against the order table, and the comparability requirements for a clean rebuild are specified.",
      "files": [],
      "expectations": [
        "Refuses to rank or kill campaigns based on the summed total.",
        "Identifies summing conversions across differing attribution windows and models as invalid - a category error, not a comparable total.",
        "Identifies the mid-month Meta setting change (7-day to 1-day click) as invalidating the month-over-month comparison on its own.",
        "Explains that part of the reported -22% is mechanical, produced by the shorter attribution window rather than by performance.",
        "Recommends reporting the three sources side by side until their definitions reconcile, instead of blending them.",
        "Notes each platform self-attributes, so platform claims cannot be summed with each other or with GA4.",
        "Recommends reconciling against the backend order table as the source of truth.",
        "Specifies the comparability requirements for the rebuilt comparison: equal window lengths, equal attribution-lag maturity, matched day-of-week composition.",
        "Notes the most recent days under-report due to attribution lag, so a month ending now reads artificially low.",
        "Issues no kill list; the verdict is insufficient evidence (or equivalent) pending a clean comparison.",
        "States exactly what would clear the gate: per-source side-by-side exports on consistent settings plus the backend join.",
        "Sets the re-check for when a clean, lag-mature comparison exists."
      ]
    },
    {
      "id": 7,
      "prompt": "I lead marketing (team of 2) at Fernway Travel, a tour operator. An audit of our ad account surfaced four things: (1) the purchase event fires twice on every booking - confirmed, the platform counts almost exactly double our booking system; (2) we run 14 campaigns and 11 of them get fewer than 10 conversions a month each; (3) our creatives are 5+ months old, and we have a creative studio on retainer with idle capacity; (4) two campaigns consistently underspend their budgets. Constraints: engineering has zero availability this quarter (confirmed by the CTO), we have no CRM - bookings live in a booking system with no export and IT says maybe next year - and the CEO wants visible action this week. Give me the quick wins first, in order.",
      "expected_output": "A ranked plan by outcome-per-effort, not cheapest-first: the double-fire tracking fix ranked first and escalated past the engineering freeze rather than demoted, the CRM-outcome rung deleted with its revival condition, consolidation of sub-volume campaigns handed off, creative promoted because of the retained studio, budget moves last, every finding tagged with severity, confidence, outcome, effort, and owner.",
      "files": [],
      "expectations": [
        "Rejects the cheapest-first quick-wins ordering and ranks by outcome bought per unit of effort.",
        "The double-firing tracking fix is ranked first despite engineering being unavailable.",
        "Handles the engineering constraint on the tracking fix as an escalation to whoever can lift it (CTO/CEO), not as a demotion or deletion, because it is the confirmed root-cause defect.",
        "States that every other fix's results will be measured through the doubled signal until the tracking fix ships, making downstream reads untrustworthy.",
        "Recommends consolidating the 11 sub-volume campaigns (below learning-volume gates), handed off as a consolidation plan rather than executed inside this diagnosis.",
        "Notes consolidation costs a learning window of volatility, setting that expectation against the CEO's this-week demand.",
        "Promotes the creative work above its default rank because the retained studio with idle capacity collapses its effort cost, and says that is the reason.",
        "Ranks budget and underspend moves last, with the reason: near-zero outcome while upstream layers fail, and significant edits reset learning.",
        "The offline/CRM-outcome feedback rung is deleted rather than parked at the bottom, naming the constraint (no CRM or export) and the revival condition (when an export exists).",
        "Tags each finding with severity, confidence, outcome bought, effort, and owner.",
        "Expresses effort as an order of magnitude (hours, a week, a quarter, a standing job), not currency or precise estimates.",
        "Provides a CEO-visible action for this week without letting the visibility demand reorder the queue.",
        "Hands each finding to its owner or follow-on workflow in rung order.",
        "States a prediction for the top fix, for example platform-reported conversions falling by roughly half toward booking-system truth once deduplication ships."
      ]
    },
    {
      "id": 8,
      "prompt": "Lumen Desks - we sell standing desks direct-to-consumer, about $80K/month across Google and Meta. ROAS slid from 3.4 to 2.1 over three weeks. My plan is to restructure the account (it has grown messy) and refresh the creatives, but sanity-check me before I start. The numbers: CPM flat (+1%), CTR flat (-1%), search impression share stable at 68%, but CVR is -41% starting March 3. On March 3 our in-house web team (they sit next to me) shipped a new product-page template and a 12% price increase. Platform-reported purchases are within 7% of our order system, same as always.",
      "expected_output": "A diagnosis that passes tracking on the stable 7% reconciliation, localises the failure past the click via the CVR-only decomposition, ties it to the March 3 release and price change as separate hypotheses, advises against the restructure and creative refresh, promotes offer-and-downstream to the top of the queue because the owners are in-house, and hands off at the click boundary.",
      "files": [],
      "expectations": [
        "Uses the ~7% reconciliation gap matching the historical norm to pass measurement/tracking before reading other layers.",
        "The decomposition isolates CVR as the only moved link, with CPM, CTR, and impression share flat.",
        "Concludes the failure sits past the click (offer and downstream), tied to the March 3 release and price change, not account structure and not creative.",
        "Advises against the planned restructure and creative refresh because no evidence implicates those layers.",
        "States that this diagnosis stops at the click and hands the page and offer work to a post-click/landing-page audit and the page owners.",
        "Promotes offer and downstream to the top of the fix queue, citing the promotion conditions: CVR collapsed while CPM, CTR, and impression share held, and the page owners are in-house.",
        "Separates the two March 3 candidates - the template change and the 12% price increase - as distinct hypotheses to isolate, not one blob.",
        "The layer screen marks structure, targeting, and creative pass with the flat-metric evidence attached.",
        "Recommends checking backend conversion on the paid path specifically, noting that unchanged CVR from other traffic sources is not a full rule-out.",
        "Recommends no budget or bid changes.",
        "Recommends testing one falsifiable hypothesis at a time (for example isolating the template from the price change) rather than stacking fixes.",
        "States a prediction (paid CVR recovers toward baseline if the page/offer fix ships) and a re-check one mature window later.",
        "Presents the verdict in a complete structured block covering window, volume/reconciliation, decomposition, localisation, layer screen, confidence, verdict, evidence, findings, prediction, handoff, and re-check."
      ]
    },
    {
      "id": 9,
      "prompt": "New CMO here at Juniper Wellness, a DTC supplements brand. Our Meta ROAS is 2.4; the industry benchmark report I bought says supplements average 3.5, and benchmark CTR is 1.6% versus our 0.9%. Clearly the account is underperforming badly. I need a full audit that identifies everything that's broken so I can present the fix list to the board next week. Extra data: our ROAS has been between 2.3 and 2.5 for 12 straight months, CTR around 0.9% the whole time, contribution margin is 55%, and blended MER is steady at 2.1. Nothing in the account changed recently.",
      "expected_output": "An audit that refuses the benchmark as baseline: the account is judged against its own 12-month history and a margin-derived break-even ROAS of roughly 1.8, concluding no defect is established; no fix list is manufactured for the board, blended MER against break-even replaces raw platform ROAS as the truth read, and the growth-versus-defect distinction is made explicit.",
      "files": [],
      "expectations": [
        "Refuses the industry benchmark as the baseline and judges the account against its own 12-month history.",
        "States why benchmarks mislead: different mix, geography, and definitions - directional context only.",
        "Derives a break-even ROAS from the 55% contribution margin (roughly 1/0.55, about 1.8) and judges the 2.4 ROAS against it as above break-even.",
        "Concludes no defect is established: stable metrics against the account's own history plus above-break-even economics do not support a broken-account verdict.",
        "Does not manufacture a fix list to close the benchmark gap - no creative, targeting, or bidding overhaul recommended off the benchmark deltas.",
        "Resists the audit-for-the-board pressure explicitly: findings require account evidence, not a count of red flags to fill a deck.",
        "Recommends blended MER judged against the margin-derived break-even as the truth read, over raw platform-reported ROAS.",
        "Notes platform-reported ROAS is claimed revenue, not evidence of incremental revenue.",
        "The layer screen shows pass states with evidence rather than invented FAILs.",
        "Frames the board answer as growth versus defect: wanting better than 2.4 is an improvement program, not a defect repair, and the diagnostic will not invent a defect to justify one.",
        "Recommends product-level contribution-margin reads as where a real opportunity review would start, since blended figures can hide margin-destroying products.",
        "Sets a monitoring baseline and re-check rather than a fix plan."
      ]
    },
    {
      "id": 10,
      "prompt": "Arcline Software, a B2B workflow SaaS. Our CPA rose 45% over the last six weeks with no single day where it broke - it just drifted up. Spend is flat. I can only export campaign-level daily data; the ad-set and ad breakdowns are blocked by our agency's portal. No CRM access either - the data team says maybe next month. Also worth mentioning: we swapped the cookie consent banner about five weeks ago. I don't need anything fancy, just go through each area and tell me yes or no: tracking fine? structure fine? targeting fine? creative fine? bids fine?",
      "expected_output": "A per-layer screen that refuses the yes/no format: four states with unknowns left unknown, confidence capped due to the unreachable backend, the consent-banner swap flagged as the first tracking suspect, the gradual no-break-date drift read as the structural-erosion pattern, the exact missing access named, concrete export steps and formulas supplied, and no fixes recommended yet.",
      "files": [],
      "expectations": [
        "Declines the yes/no format and answers per layer in four states (pass, FAIL, unknown, not applicable).",
        "Layers the available data cannot power are marked unknown and explicitly not treated as clean.",
        "States that with the backend unreachable every finding carries at most medium confidence, and says so in the verdict itself.",
        "Flags the consent-banner swap five weeks ago as a tracking-layer suspect that must be reconciled before other layers are read.",
        "Reads the gradual, no-break-date CPA drift as the structural-erosion/fragmentation pattern, distinct from a single-event cause.",
        "Names the exact missing access that would clear each unknown: a CRM or backend export, and ad-set plus ad-level breakdowns.",
        "States that localisation cannot complete at campaign-only granularity, and what the finer breakdown would unlock.",
        "Asks for, or explicitly requires, the change and edit log - what changed and exactly when - before any verdict.",
        "Provides concrete export steps and spreadsheet formulas for the user to run, including the delta formula (current - baseline) / baseline.",
        "Does not issue a definitive single-layer root-cause verdict on this data.",
        "Tags per-layer entries with severity and confidence as separate fields.",
        "Emits a compact state block (baselines, screen states, open unknowns, re-check date) the user can carry into the next session.",
        "Recommends no fixes - no budget, bid, creative, or structural changes - before the unknowns are resolved."
      ]
    }
  ],
  "trigger_queries": [
    { "query": "our google ads suddenly stopped converting last month, can you figure out why", "should_trigger": true },
    { "query": "audit my ad account", "should_trigger": true },
    { "query": "CPA has doubled since January and nothing obvious changed", "should_trigger": true },
    { "query": "why did our ROAS drop from 3.2 to 1.9", "should_trigger": true },
    { "query": "our facebook ads used to print money, now they barely break even", "should_trigger": true },
    { "query": "run a full paid media account audit for our ecommerce store", "should_trigger": true },
    { "query": "cost per lead keeps creeping up every month and I can't tell why", "should_trigger": true },
    { "query": "the agency wants more budget but performance keeps getting worse", "should_trigger": true },
    { "query": "something is wrong with our ad account, results fell off a cliff two weeks ago", "should_trigger": true },
    { "query": "we're wasting ad spend somewhere, help me find where", "should_trigger": true },
    { "query": "review our campaign structure, I think something is off", "should_trigger": true },
    { "query": "diagnose why our meta ads performance degraded", "should_trigger": true },
    { "query": "our ads stopped working and I don't know if it's the creative or the targeting", "should_trigger": true },
    { "query": "conversions dropped 40% overnight and platform support is useless", "should_trigger": true },
    { "query": "why is my cost per acquisition rising when we haven't touched anything", "should_trigger": true },
    { "query": "boss wants to know why leads got so expensive this quarter", "should_trigger": true },
    { "query": "we spend $60k a month on paid and results keep sliding, where do I even start", "should_trigger": true },
    { "query": "is our ad account broken or is it just the market", "should_trigger": true },
    { "query": "everyone says raise the budget, but I want to know what's actually wrong first", "should_trigger": true },
    { "query": "linkedin ads worked great in Q1, dead in Q3, help me work out what changed", "should_trigger": true },
    { "query": "can you do a health check on our ppc account", "should_trigger": true },
    { "query": "our new marketing hire says the whole account is set up wrong, can you verify", "should_trigger": true },
    { "query": "why would ROAS fall when we changed nothing", "should_trigger": true },
    { "query": "figure out whether our performance drop is seasonal or something we broke", "should_trigger": true },
    { "query": "our cost per demo went from $180 to $420, walk me through finding the cause", "should_trigger": true },
    { "query": "second opinion on our paid search account, the numbers look worse every week", "should_trigger": true },
    { "query": "should I be worried that CPM is up 30% across the whole account", "should_trigger": true },
    { "query": "our ads suddenly got expensive, tell me if it's us or the auction", "should_trigger": true },
    { "query": "the dashboard says our campaigns are fine but revenue from ads keeps falling", "should_trigger": true },
    { "query": "inherited an underperforming ads account at my new job, where do I start", "should_trigger": true },
    { "query": "conversion volume halved but spend stayed flat, what happened", "should_trigger": true },
    { "query": "our shopify store's paid traffic stopped converting, need to know the root cause", "should_trigger": true },
    { "query": "before we rebuild everything, can you diagnose what's actually failing in the account", "should_trigger": true },
    { "query": "the google rep keeps pitching fixes but the account has been declining for months, can you look at it properly", "should_trigger": true },
    { "query": "why do our ads perform worse every month even though we keep optimizing", "should_trigger": true },
    { "query": "our lead gen campaigns collapsed right after the site relaunch, is it related", "should_trigger": true },
    { "query": "CPL up 3x in six weeks, need answers before the board meeting", "should_trigger": true },
    { "query": "what's tanking our ad performance, creative fatigue or audience burnout?", "should_trigger": true },
    { "query": "I think the algorithm broke our campaigns, can you check", "should_trigger": true },
    { "query": "paid social results dropped and my CMO wants a root cause by friday", "should_trigger": true },
    { "query": "our account's efficiency has been eroding slowly for six months", "should_trigger": true },
    { "query": "did our ads stop working because of the iOS privacy changes or did we mess something up", "should_trigger": true },
    { "query": "help me figure out why the campaigns that used to be profitable aren't anymore", "should_trigger": true },
    { "query": "spent double this month for the same number of sales, why", "should_trigger": true },
    { "query": "what's wrong with my adwords account", "should_trigger": true },
    { "query": "our b2b ads generate tons of leads but sales says they're all junk", "should_trigger": true },
    { "query": "impressions are steady but conversions keep sliding, diagnose it for me", "should_trigger": true },
    { "query": "we doubled budget and got fewer conversions, make it make sense", "should_trigger": true },
    { "query": "why are we suddenly losing money on ad spend after two profitable years", "should_trigger": true },
    { "query": "my ecommerce ads went from 4x to 1.5x return, need a structured diagnosis", "should_trigger": true },
    { "query": "our campaigns never leave the learning phase and performance is all over the place, what's the underlying issue", "should_trigger": true },
    { "query": "prospecting campaigns are fine but retargeting collapsed, what would cause that", "should_trigger": true },
    { "query": "can you review why our ad results don't match last year despite bigger budgets", "should_trigger": true },
    { "query": "performance dropped right after we restructured the account, was it the restructure or something else", "should_trigger": true },
    { "query": "tell me if we actually need new creatives or if something else is broken", "should_trigger": true },
    { "query": "the account is bleeding money and the team keeps guessing at fixes, need a real diagnosis", "should_trigger": true },
    { "query": "why is our cost per click fine but our cost per sale terrible now", "should_trigger": true },
    { "query": "quarterly review time: figure out what degraded in our paid accounts", "should_trigger": true },
    { "query": "give me a root cause analysis of our declining ad performance", "should_trigger": true },
    { "query": "my ads worked until the consent banner update, now the results look awful, what's really going on", "should_trigger": true },
    { "query": "audit our wasted ad spend and tell me what's actually causing it", "should_trigger": true },
    { "query": "check that our conversion pixel fires correctly before we launch next week", "should_trigger": false },
    { "query": "meta says 320 purchases but shopify shows 210, explain the gap", "should_trigger": false },
    { "query": "which of our 30 campaigns should we merge so they exit learning faster", "should_trigger": false },
    { "query": "is this specific ad worn out? its CTR has been dropping for 3 weeks", "should_trigger": false },
    { "query": "build a negative keyword list from this search terms report", "should_trigger": false },
    { "query": "design the audience targeting plan for our new product launch", "should_trigger": false },
    { "query": "how should I split $50k a month between google, meta and tiktok", "should_trigger": false },
    { "query": "our winning campaign is ready to scale, how fast can I raise the budget", "should_trigger": false },
    { "query": "should we use target CPA or maximize conversions for this new campaign", "should_trigger": false },
    { "query": "are we on track to spend the monthly budget or are we under-pacing", "should_trigger": false },
    { "query": "audit the landing page our ads send traffic to", "should_trigger": false },
    { "query": "write 10 ad copy variants for our spring sale", "should_trigger": false },
    { "query": "compute our CAC from this spend data and tell me if it's healthy", "should_trigger": false },
    { "query": "set maximum CAC and minimum ROAS guardrails for the marketing org", "should_trigger": false },
    { "query": "which ad platforms should a b2b devtools startup even be on", "should_trigger": false },
    { "query": "score these five video ad hooks and tell me which deserve budget", "should_trigger": false },
    { "query": "design an a/b test plan for our new creative concepts", "should_trigger": false },
    { "query": "build a retargeting sequence from our funnel data", "should_trigger": false },
    { "query": "which customers should seed our lookalike audience", "should_trigger": false },
    { "query": "write ugc scripts for our skincare product", "should_trigger": false },
    { "query": "set up a competitor ad swipe file for the team", "should_trigger": false },
    { "query": "write a job description for a senior media buyer", "should_trigger": false },
    { "query": "how do I move from ppc specialist to head of growth", "should_trigger": false },
    { "query": "what newsletters and podcasts should a media buyer follow", "should_trigger": false },
    { "query": "write a creative brief for our video editor", "should_trigger": false },
    { "query": "map the buying committee for our enterprise abm ads", "should_trigger": false },
    { "query": "should we run our CEO's linkedin posts as paid ads", "should_trigger": false },
    { "query": "adapt our ad copy for AI chat assistant placements", "should_trigger": false },
    { "query": "which ad formats fit an app install objective", "should_trigger": false },
    { "query": "the platform numbers and GA4 never match, quantify how much is timing vs definitions", "should_trigger": false },
    { "query": "plan the migration so merging our ad sets doesn't reset learning", "should_trigger": false },
    { "query": "why did organic traffic drop 40% after the google update", "should_trigger": false },
    { "query": "audit our site's SEO, rankings fell hard this month", "should_trigger": false },
    { "query": "diagnose why our email open rates collapsed", "should_trigger": false },
    { "query": "our website conversion rate dropped, run a CRO audit", "should_trigger": false },
    { "query": "our churn spiked last quarter, find the root cause", "should_trigger": false },
    { "query": "sales pipeline dried up, diagnose our outbound motion", "should_trigger": false },
    { "query": "our app store conversion rate is falling, what's wrong", "should_trigger": false },
    { "query": "figure out why our SaaS trial-to-paid rate dropped", "should_trigger": false },
    { "query": "audit our google analytics setup for gaps", "should_trigger": false },
    { "query": "my google ads account got suspended, how do I appeal", "should_trigger": false },
    { "query": "help me structure a brand new ad account from scratch", "should_trigger": false },
    { "query": "what's the industry benchmark CTR for facebook ads in fashion", "should_trigger": false },
    { "query": "forecast next quarter's ad performance for the budget plan", "should_trigger": false },
    { "query": "build the media plan for our product launch", "should_trigger": false },
    { "query": "how do I set up enhanced conversions in google ads", "should_trigger": false },
    { "query": "write the monthly client report for our ppc account", "should_trigger": false },
    { "query": "reduce our AWS bill, cloud costs doubled", "should_trigger": false },
    { "query": "diagnose why our kubernetes pods keep crashing", "should_trigger": false },
    { "query": "review my resume for a performance marketing role", "should_trigger": false },
    { "query": "how many conversions does smart bidding need before I switch to tROAS", "should_trigger": false },
    { "query": "set the right frequency caps for each retargeting stage", "should_trigger": false },
    { "query": "pick which of these two hero images we should test first", "should_trigger": false },
    { "query": "translate our ad copy for the german market", "should_trigger": false },
    { "query": "what UTM naming convention should we use across campaigns", "should_trigger": false },
    { "query": "design a geo holdout to measure incrementality of our brand search campaigns", "should_trigger": false },
    { "query": "negotiate better rates with our ad agency", "should_trigger": false },
    { "query": "our competitor launched aggressive ads, build a counter campaign", "should_trigger": false },
    { "query": "how much budget do we need to hit 500 leads a month", "should_trigger": false },
    { "query": "clean up the duplicate conversion actions in google ads for me", "should_trigger": false },
    { "query": "explain why meta's attribution changed after iOS 14", "should_trigger": false }
  ]
}
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall