google-ads-shopping
Skill15 starsChanged 38 days agoMITView on GitHub
Use when analyzing or optimizing Google Ads Shopping campaigns: feed health gate, item KILL/DOWNGRADE/PROMOTE rules, product groups, search-term negatives, SCALE/T/CAP.
In this repository61 other files it gives its agents.
- access-and-permissionsSkill
- accounts-and-connectionsSkill
- ad-brief-generatorSkill
- affiliate-marketingSkill
- analyse-creativeSkill
- automate-with-agentsSkill
- brief-creativeSkill
- build-reportsSkill
- clean-wasted-spendSkill
- competitor-ad-intelligenceSkill
- creative-psychology-hooksSkill
- creative-researchSkill
- diagnose-performanceSkill
- email-marketingSkill
- ga4-source-of-truthSkill
- get-startedSkill
- gomarble-skills-creative-strategistsSkill
- gomarble-skills-ecommerce-brandsSkill
- gomarble-skills-google-ads-auditSkill
- gomarble-skills-meta-ads-auditSkill
- gomarble-skills-saas-companiesSkill
- google-ads-create-master-skillSkill
- google-ads-depth-of-analysisSkill
- google-ads-guardrailsSkill
- google-ads-keywordplannerSkill
- google-ads-pmax-evaluationSkill
- google-ads-pmax-scalingSkill
- google-ads-search-analysisSkill
- google-ads-search-executionSkill
- google-ads-tool-fundamentalsSkill
- google-impression-shareSkill
- google-pmax-pulseSkill
- google-search-auditSkill
- google-search-term-auditSkill
- launch-campaignsSkill
- linkedin-adsSkill
- manage-campaignsSkill
- meta-ads-auditSkill
- meta-agent-operationsSkill
- meta-create-master-skillSkill
- meta-creative-analysisSkill
- meta-creative-fatigue-detectionSkill
- meta-creative-strategySkill
- meta-custom-event-interpretationSkill
- meta-daily-optimizationSkill
- meta-depth-of-analysisSkill
- meta-guardrailsSkill
- meta-performance-analysisSkill
- meta-tool-fundamentalsSkill
- microsoft-adsSkill
- organic-socialSkill
- own-creative-diagnosisSkill
- research-competitorsSkill
- search-console-master-skillSkill
- shift-budgetSkill
- shopify-order-disciplineSkill
- tiktok-adsSkill
- tiktok-create-master-skillSkill
- winning-ads-engineSkill
- winning-ads-orchestratorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Before any optimization, verify:
- Distinctive: line 35
Ask user for target ROAS. Default: historical 30-day ROAS.
- Distinctive: line 57
If groups don't have meaningfully different ROAS targets → consolidate
- Distinctive: line 63
Add negatives ONLY for wrong-intent terms:
- Distinctive: line 70
Do NOT negate high-intent commercial terms even if they haven't converted yet.
- Distinctive: line 77
ALL must be true:
- Distinctive: line 93
Only analyze if segment spend ≥ 2× AOV (enough data to judge).
- Distinctive: line 96
Check for technical issues before excluding (site speed, checkout flow)
- Distinctive: line 110
Never optimize by CTR alone (Shopping is ROAS-driven)
- Distinctive: line 111
Never let cheap, low-converting SKUs dominate spend
- Distinctive: line 112
Never scale without confirming winners are getting the budget
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Google Ads Shopping — Optimization Protocol
Product-led optimization: validate feed → classify items → manage structure → scale or cut.
Step 0: Feed Health (BLOCKING — fail = STOP)
Before any optimization, verify:
- ≥ 80% products approved in Merchant Center
- Purchase conversion tracking is active (conversions_value > 0 in data)
- Price and availability are accurate (requires manual verification or Merchant Center check)
If ANY check fails → STOP all optimization. Fix feed first.
Step 1: Data Pull
Query using google_ads_run_gaql:
- Account AOV: total conversions_value / total conversions from
customerresource, LAST_30_DAYS - Item-level performance: product_item_id, product_title, product_brand, cost, conversions, conv_value, clicks, impressions from
shopping_performance_view. Sort by cost DESC, limit 200. Filter:SHOPPINGcampaigns. - Campaign-level: campaign id/name/status, budget, cost, conversions, conv_value from
campaign. Filter:SHOPPING,ENABLED. - Search terms: search_term, cost, clicks, conversions from
search_term_view. Filter:SHOPPING. Sort by cost DESC, limit 200. - Daily budget utilization: campaign id, date, cost from
campaign. Filter:SHOPPING,LAST_14_DAYS.
Lookback: 14 days if ≥ 100 purchases/month, otherwise 30 days.
Ask user for target ROAS. Default: historical 30-day ROAS.
Step 2: Item-Level Classification
Sort items by cost (highest first). For each item:
| Classification | Condition | Action |
| KILL | Cost ≥ 2× AOV AND conversions = 0 | Exclude item ID immediately. No learning window. |
| DOWNGRADE | ROAS < 0.7× target AND cost ≥ 0.5× AOV | Lower bid or exclude. Item is spending but underperforming. |
| PROMOTE | Conversions ≥ 2 AND ROAS ≥ target | Isolate into own product group/campaign to protect budget. |
Items not matching any rule: monitor, no action needed.
Step 3: Product Group Structure
- Maximum 3 product groups per campaign
- Split ONLY when economics differ (different margins, price bands, seasonal risk)
- If groups don't have meaningfully different ROAS targets → consolidate
Step 4: Search Term Negatives
Add negatives ONLY for wrong-intent terms:
- Price objection: free, cheap, budget, discount code, coupon
- DIY/repair: diy, repair, fix, how to, tutorial
- Used/second-hand: used, second hand, refurbished, pre-owned
- Products not in feed (compare search terms to product titles)
- Irrelevant attributes (colors/sizes not offered)
Do NOT negate high-intent commercial terms even if they haven't converted yet.
Step 5: Budget & Bid Decisions
SCALE (increase budget 10–20%)
ALL must be true:
- Campaign ROAS ≥ target
- Budget utilization ≥ 90% on 10+ of last 14 days
- Top 20% of SKUs by conversions account for ≥ 60% of spend (winners getting the budget)
CUT/CAP (reduce budget or exclude SKUs)
ANY true:
- Campaign ROAS < target
- SKUs with ROAS < 0.7× target receiving increasing spend share WoW
→ Reduce budget OR exclude underperforming SKUs first, then reassess.
Step 6: Device & Location (last)
Only analyze if segment spend ≥ 2× AOV (enough data to judge).
- Exclude device/location ONLY if ROAS ≤ 0.6× account average AND no operational explanation (e.g., mobile site is broken)
- Check for technical issues before excluding (site speed, checkout flow)
Step 7: Campaign Kill Conditions
Pause the Shopping campaign if:
- ROAS < 0.6× target after total spend ≥ 2× AOV
- Shopping ROAS consistently worse than Search ROAS over 30+ days
Prohibitions
- Never optimize by CTR alone (Shopping is ROAS-driven)
- Never let cheap, low-converting SKUs dominate spend
- Never scale without confirming winners are getting the budget
Output must include: item classification summary (KILL/DOWNGRADE/PROMOTE counts + savings), search term negatives, budget recommendation with rationale, expected 7-day ROAS impact.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

