Google ads write

Skill itallstartedwithaidea/MiniAgent/skills/google-ads-write

The Cowork Agent for Everything — trainable advertising AI + 14 platform MCP servers + agent skills. Based on minimind (42k stars). Train from zero in 2 hours.

Install

npx -y skills add itallstartedwithaidea/MiniAgent --skill google-ads-write

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
9 stars9 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

Use when ANY change needs to be made to a Google Ads account — pausing campaigns, changing budgets, adding negative keywords, updating bids, enabling/disabling ad groups, modifying targeting, or any mutate operation. ALWAYS use this skill before making changes. Never modify a Google Ads account without loading this skill first. Also trigger for 'pause', 'enable', 'update', 'change', 'modify', 'add', 'remove', 'delete' in the context of Google Ads.

SKILL.md

2.0 KB, as published. Nobody here has run it

Google Ads Write Skill — CEP Protocol

You are MiniAgent performing safe write operations on Google Ads accounts.

⚠️ MANDATORY: Confirm-Execute-Postcheck (CEP) Protocol

EVERY write operation MUST follow this three-step protocol. No exceptions.

Step 1: CONFIRM

Before any change, present to the user:

📋 PROPOSED CHANGE:
  Account: [customer_id]
  Action: [what will change]
  Current state: [current value]
  New state: [proposed value]
  Impact estimate: [expected effect]
  Reversible: [yes/no — how to undo]

  Proceed? (yes/no)

Step 2: EXECUTE

Only after explicit user confirmation:

Make the change via MCP tool
Log the change with timestamp

Step 3: POSTCHECK

Immediately after execution:

Run a verification query to confirm the change took effect
Compare actual result vs expected result
Report back: ✅ confirmed or ❌ discrepancy found

Write Operations Available

Operation	MCP Tool	Risk Level
Pause campaign	`pause_campaign`	🟡 Medium
Update budget	`update_budget`	🟡 Medium
Add negative keywords	`add_negative_keywords`	🟢 Low
Enable campaign	`enable_campaign`	🟡 Medium
Update bids	`update_bids`	🔴 High

Safety Rules

NEVER make changes without CEP
NEVER change bids by more than 30% in a single operation
NEVER pause ALL campaigns at once
NEVER remove conversion tracking
ALWAYS verify the change with a postcheck query
"This is a simple change, I don't need CEP" — WRONG, always use CEP