Google ads competitor intel
Skill kastriasani/google-ads-skills/skills/google-ads-competitor-intel
13 Claude Code Agent Skills for Google Ads (research, planning, build, optimization, reporting) with a premium visual dashboard and a live example per skill.
npx -y skills add kastriasani/google-ads-skills --skill google-ads-competitor-intelAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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.
What its author says it does
Copied from the file, not written here
Competitor conquesting and a client-ready paid-search battlecard for Google Ads. Builds a win, tie, and loss matrix vs each competitor, derives USP headlines and which competitors to attack or avoid, generates conquesting keyword sets (competitor alternative, competitor vs brand, tools like competitor, switch from competitor, competitor pricing) with match types and an RSA angle per cluster, and flags trademark and policy caution on naming competitors in ad text. Use when the user wants to research competitors for paid search, build a battlecard, conquest a competitor, bid on competitor terms, create alternative or vs keywords, find their USP against rivals, or read auction insights. Trigger phrases include competitor intel, conquesting, competitor keywords, battlecard, competitor alternative ads, and how do we compare on Google Ads.
SKILL.md
5.3 KB, as published. Nobody here has run it
Google Ads Competitor Intel
Turn competitor research into two paid-search assets: a win/tie/loss battlecard that tells you which competitors to attack and which USP headlines to lead with, and a set of conquesting keyword clusters with match types, RSA angles, and trademark guidance. The point is to capture switchers and comparison shoppers profitably, not to pay to send buyers to a page where you lose the comparison.
When to use
- The user wants to conquest a competitor, bid on competitor terms, or build alternative/vs keyword sets.
- The user needs a client-ready paid-search battlecard or wants to know their USP against named rivals.
- The user is reading Auction Insights and wants to decide where to push, hold, or pull back against competitors.
Run google-ads-keyword-research for the core (non-conquest) plan and
google-ads-research for the broader market picture; this skill owns the
competitor-facing slice.
Workflow
-
Build the win/loss battlecard. Capture your offer's capabilities vs each competitor as JSON (offer, onboarding, support, capability, security), then:
python3 scripts/competitor_gap_matrix.py --input matrix.json --markdownIt computes per-competitor win rates and outputs three decision lists: advantages (your USP headlines for RSAs and conquest copy), gaps (claims to avoid in ad text), and parity (win on price/proof/offer instead). It flags which competitors to attack (you win clearly) and which to avoid.--demoruns on sample data;--jsonfor pipelines. -
Decide who to conquest from the matrix. Attack competitors where your win rate is 60%+, be selective at 40-60%, and avoid conquesting any competitor you trail; sending comparison shoppers to a losing page wastes budget. See
references/conquesting-playbook.md. -
Generate conquesting keyword sets:
python3 scripts/conquest_keyword_builder.py --brand FlowDesk --competitors "Asana, Monday"For each competitor it builds five clusters -- alternative, vs, tools-like, switch, and pricing -- each with suggested match types, an RSA angle, and a per-cluster trademark caution.--demoand--jsonsupported. -
Apply the trademark and policy rules. Bidding on a competitor trademark as a keyword is generally allowed; using it in ad text is restricted and can be disapproved or complained against. Default to keeping the competitor name in the keyword and landing page, and keep ad text about your own brand and benefits unless rights are confirmed.
-
Pair every conquest cluster with a matching landing page (alternative, vs, migration) and lead with a USP headline from step 1 plus a risk-reversal offer. Generic homepages tank Quality Score and conversion on conquest traffic.
-
Measure with Auction Insights. Use overlap rate to find your real rivals, position-above-rate and outranking share to see if conquesting is working, and separate budget-limited from rank-limited impression-share loss before changing bids. See
references/auction-insights.md.
Inputs and data sources
Both scripts run standalone, stdlib only.
competitor_gap_matrix.py: a JSON matrix of your status vs each competitor per feature/offer dimension.conquest_keyword_builder.py: your brand and a list of competitor names.
Optional sources sharpen the work:
- Google Ads Auction Insights: real overlap, impression share, and outranking data to prioritize and validate conquesting.
- Web search: competitor pricing, positioning, reviews, and release notes to fill the matrix and find switching pains.
- Google Ads Keyword Planner: volume and competition on conquest terms.
- Google Sheets / BigQuery: store the matrix and conquest plan.
Outputs
- A paid-search battlecard: per-competitor win/tie/loss, win rate, conquest action (attack/selective/avoid), a feature matrix, USP headlines, and claims to avoid (markdown or JSON).
- Conquesting keyword sets per competitor (five clusters each) with match types, RSA angles, and trademark cautions.
References
- conquesting-playbook.md: the four conquesting page/keyword formats, which competitors to attack vs avoid, copy rules, and trademark/policy guidance.
- auction-insights.md: how to read impression share, lost IS (rank vs budget), overlap rate, position-above-rate, and outranking share, and the action each implies.