google-ads

jdrhyne/agent-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jdrhyne/agent-skills --skill google-ads
0 commentsdiscussion
summary

Manage Google Ads accounts via API or an attached browser session.

skill.md

Google Ads Skill

Manage Google Ads accounts via API or an attached browser session.

Mode Selection

Check which mode to use:

  1. API Mode - If user has google-ads.yaml configured or GOOGLE_ADS_* env vars
  2. Browser Mode - If user says "I don't have API access" or just wants quick checks
# Check for API config
ls ~/.google-ads.yaml 2>/dev/null || ls google-ads.yaml 2>/dev/null

If no config found, ask: "Do you have Google Ads API credentials, or should I use the attached browser session?"


Browser Mode (Universal)

Requirements: User logged into ads.google.com in browser

Setup

  1. User opens ads.google.com and logs in
  2. User clicks Clawdbot Browser Relay toolbar icon (badge ON)
  3. Use browser tool with profile="chrome"

Common Workflows

Get Campaign Performance

1. Navigate to: ads.google.com/aw/campaigns
2. Set date range (top right date picker)
3. Snapshot the campaigns table
4. Parse: Campaign, Status, Budget, Cost, Conversions, Cost/Conv

Find Zero-Conversion Keywords (Wasted Spend)

1. Navigate to: ads.google.com/aw/keywords
2. Click "Add filter" → Conversions → Less than → 1
3. Click "Add filter" → Cost → Greater than → [threshold, e.g., $500]
4. Sort by Cost descending
5. Snapshot table for analysis

Pause Keywords/Campaigns

1. Navigate to keywords or campaigns view
2. Check boxes for items to pause
3. Click "Edit" dropdown → "Pause"
4. Confirm action

Download Reports

1. Navigate to desired view (campaigns, keywords, etc.)
2. Click "Download" icon (top right of table)
3. Select format (CSV recommended)
4. File downloads to user's Downloads folder

For detailed browser selectors: Load browser-workflows.md from this skill's references folder.


API Mode (Power Users)

Requirements: Google Ads API developer token plus locally configured client credentials

Setup Check

# Verify google-ads SDK
python -c "from google.ads.googleads.client import GoogleAdsClient; print('OK')"

# Check config
cat ~/.google-ads.yaml

Common Operations

Query Campaign Performance

from google.ads.googleads.client import GoogleAdsClient

client = GoogleAdsClient.load_from_storage()
ga_service = client.get_service("GoogleAdsService")

query = """
    SELECT campaign.name, campaign.status,
           metrics.cost_micros, metrics.conversions,
           metrics.cost_per_conversion
    FROM campaign
    WHERE segments.date DURING LAST_30_DAYS
    ORDER BY metrics.cost_micros DESC
"""

response = ga_service.search(customer_id=CUSTOMER_ID, query=query)

Find Zero-Conversion Keywords

query = """
    SELECT ad_group_criterion.keyword.text,
           campaign.name, metrics.cost_micros
    FROM keyword_view
    WHERE metrics.conversions = 0
      AND metrics.cost_micros > 500000000
      AND segments.date DURING LAST_90_DAYS
    ORDER BY metrics.cost_micros DESC
"""

Pause Keywords

operations = []
for keyword_id in keywords_to_pause:
    operation = client.get_type("AdGroupCriterionOperation")
    operation.update.resource_name = f"customers/{customer_id}/adGroupCriteria/{ad_group_id}~{keyword_id}"
    operation.update.status = client.enums.AdGroupCriterionStatusEnum.PAUSED
    operations.append(operation)

service.mutate_ad_group_criteria(customer_id=customer_id, operations=operations)

For full API reference: Load api-setup.md from this skill's references folder.


Audit Checklist

Quick health check for any Google Ads account:

Check Browser Path What to Look For
Zero-conv keywords Keywords → Filter: Conv<1, Cost>$500 Wasted spend
Empty ad groups Ad Groups → Filter: Ads=0 No creative running
Policy violations Campaigns → Status column Yellow warning icons
Optimization Score Overview page (top right) Below 70% = action needed
Conversion tracking Tools → Conversions Inactive/no recent data

Output Formats

When reporting findings, use tables:

## Campaign Performance (Last 30 Days)
| Campaign | Cost | Conv | CPA | Status |
|----------|------|------|-----|--------|
| Branded  | $5K  | 50   | $100| ✅ Good |
| SDK Web  | $10K | 2    | $5K | ❌ Pause |

## Recommended Actions
1. **PAUSE**: SDK Web campaign ($5K CPA)
2. **INCREASE**: Branded budget (strong performer)

Troubleshooting

Safety Boundaries

  • Do not pause campaigns, keywords, or budgets without explicit confirmation from the user.
  • Do not export or summarize account data beyond the account, date range, and entities the user requested.
  • Do not expose API credentials, downloaded reports, or account identifiers in chat output.
  • Do not use browser mode unless the user has attached the correct logged-in ads.google.com session.

Browser Mode Issues

  • Can't see data: Check user is on correct account (top right account selector)
  • Slow loading: Google Ads UI is heavy; wait for tables to fully load
  • Session expired: User needs to re-login to ads.google.com

API Mode Issues

  • Authentication failed: Refresh OAuth token, check google-ads.yaml
  • Developer token rejected: Ensure token is approved (not test mode)
  • Customer ID error: Use 10-digit ID without dashes

Security & Change-Control Addendum

  • Default mode is read-only audit/reporting.
  • Any mutating action (pause/enable/edit bids/budgets) requires explicit confirmation listing impacted entities first.
  • Browser mode must be user-attended for account-affecting actions.
  • Protect ~/.google-ads.yaml permissions and never echo tokens/secrets in terminal output.
how to use google-ads

How to use google-ads on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add google-ads
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jdrhyne/agent-skills --skill google-ads

The skills CLI fetches google-ads from GitHub repository jdrhyne/agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/google-ads

Reload or restart Cursor to activate google-ads. Access the skill through slash commands (e.g., /google-ads) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.560 reviews
  • Dhruvi Jain· Dec 24, 2024

    Useful defaults in google-ads — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Amelia Reddy· Dec 20, 2024

    google-ads has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Mei Rahman· Dec 16, 2024

    google-ads fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Li Gill· Dec 12, 2024

    I recommend google-ads for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Dev Johnson· Dec 4, 2024

    We added google-ads from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sofia Huang· Nov 23, 2024

    Solid pick for teams standardizing on skills: google-ads is focused, and the summary matches what you get after install.

  • Min Thompson· Nov 19, 2024

    Registry listing for google-ads matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Oshnikdeep· Nov 15, 2024

    google-ads is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Liam Gupta· Nov 11, 2024

    google-ads fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Daniel Flores· Nov 7, 2024

    google-ads has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 60

1 / 6