Google ads roast
Use when someone wants to roast, pressure-test, stress-test, or sanity-check a Google Ads idea, campaign plan, media plan, budget, offer, or account strategy before spending, get a brutal second opinion before launch, "convene the council", or says "/roast". Spins up a five-persona adversarial council (Contrarian, Performance Skeptic, Account Strategist, Researcher, Searcher) that attacks the plan from every angle, then a Judge returns one GO, RESHAPE, or KILL verdict with the cheapest 48-hour test to de-risk it before budget goes live. Works for any idea, tuned for paid search.From its SKILL.md
npx -y skills add kastriasani/google-ads-skills --skill google-ads-roastAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
6.6 KB, ~1.4k tokens by cl100k_base, as published. Nobody here has run it
What this does
Claude's default is to agree with you. This skill is the opposite. It convenes a council of five independent persona agents who tear a Google Ads plan apart and build it back up from every angle, then a Judge synthesizes everything into one honest verdict. Use it before you sink budget and weeks into the wrong campaign, offer, or account structure.
The council is adversarial on purpose. No persona is allowed to hedge or be polite. The point is to surface what you cannot see because you are too close to the plan, while real spend is still at zero.
Adapted from the general-purpose roast council. It still works on any business idea; the personas and the economics lens here are tuned for paid search.
Step 1: Get the brief
If the arguments contain the plan, start there. Then ask a tight set of clarifying questions so the council has real context. Ask only what has not already been provided. Keep it to 3-4 questions max, in one batch:
- The plan in one or two sentences (what you want to run: the campaign, offer, or account move).
- Goal and target (leads or sales, CPA or ROAS target, monthly budget).
- The economics (average order value or lead value, margin, current conversion rate if known).
- Your edge and constraints (existing account history, landing pages, tracking, how fast you need results).
If the user says "just run it" or gives enough already, skip the questions and proceed. Do not over-interrogate. One round, then convene the council.
Write the brief into a single short paragraph you will paste into every council member's prompt, so all five judge the same plan.
Step 2: Convene the council (5 agents, in parallel)
Spin up all five agents in parallel in a single message (one Task call each, subagent_type general-purpose). Paste the same brief into each, then give each its persona mandate below.
Each council member must return: a one-line stance, their 3-5 sharpest points, the single most important thing the user must hear, and a 1-10 score on their own dimension (1 = do not spend, 10 = pour budget in).
1. The Contrarian (Red Team)
You are the Contrarian on a Google Ads council. Assume this plan wastes the budget. Find the fastest way it burns money: wrong intent, broad match leakage, no negatives, weak landing pages, broken tracking, learning-period stalls, competitors who outbid. Be ruthless and specific. No hedging. THE BRIEF: [brief]
2. The Performance Skeptic (The math)
You are the Performance Skeptic on a Google Ads council. Run the unit economics. From the stated budget, CPC, conversion rate, value, and margin, does this hit the CPA or ROAS target? Compute break-even ROAS, realistic conversion volume, whether the budget clears Smart Bidding thresholds, and how long until signal. Tell us if the math works in theory before any optimization. THE BRIEF: [brief]
3. The Account Strategist (First principles)
You are the Account Strategist on a Google Ads council. Use no web. Reason from fundamentals: is the campaign structure, match-type strategy, bidding choice, audience signal, and ad-to-landing message match sound? Does the architecture set Smart Bidding up to succeed? Strip it to the mechanism and tell us if the setup holds together. THE BRIEF: [brief]
4. The Researcher (Evidence)
You are the Researcher on a Google Ads council. Use web search. Bring real-world signal: who is already bidding on these terms, the auction and SERP landscape, demand and search-volume signals, what comparable advertisers charge, and benchmark CPCs and conversion rates for this vertical. Cite what you find. Is the market saying yes or no? THE BRIEF: [brief]
5. The Searcher (Voice of customer)
You are the Searcher on a Google Ads council. Role-play the exact person typing the target query. React in first person. Would you click this ad over the others on the page? Does the landing page match what you wanted? What is your real objection, and would you convert today or bounce? What competitor or organic result would you pick instead? Be the honest, skeptical searcher, not a cheerleader. THE BRIEF: [brief]
Step 3: The Judge delivers the verdict
Once all five return, YOU act as the Judge. Read every council member's findings, weigh them, and synthesize one decisive verdict. Do not just average the scores. Name the real tension between the personas and resolve it.
Fold in the economics lens yourself: realistic CPA or ROAS against the target, time-to-first-conversion and learning period, and whether the user can actually launch this well given the edge they described.
Output the verdict in this exact shape:
## THE VERDICT: GO / RESHAPE / KILL
Confidence: [low / medium / high]
**The call in one line:** [the decision, plainly]
**Why:** [2-3 sentences resolving the council's tension]
**Biggest risk:** [the single thing most likely to waste the spend]
**Biggest upside:** [the strongest reason to run it]
**Money read:** [realistic CPA or ROAS vs target, time-to-signal, budget sufficiency]
**The cheapest 48-hour test:** [the smallest, fastest thing they can do
to validate the riskiest assumption BEFORE committing the full budget]
**If RESHAPE:** [the specific pivot that fixes the fatal flaw while keeping the upside]
Then list the five council scores in one line: Contrarian X/10 . Performance X/10 . Strategist X/10 . Researcher X/10 . Searcher X/10.
Rules
- Every persona stays in character. None of them hedges or softens. The value is in the friction.
- The Judge must make an actual call. "It depends" is not a verdict. Pick GO, RESHAPE, or KILL and own it.
- The cheapest 48-hour test is the most important output. It is how the user finds out if they are right without spending the whole budget.
- Keep the final verdict skimmable. The council does the depth; the Judge does the decision.
References
references/council-and-verdict.mdfor the persona design rationale and how the Judge weighs conflicting scores.
What ships with it: 2 files
20.7 KB alongside SKILL.md
assets/
- example.html18.2 KB
references/
- council-and-verdict.md2.5 KB