Individual skill

add-account-negative-keywords

Add account-level negative keywords (Admin → Account Settings → Negative Keywords) to Google Ads accounts using the 3-step SharedSet approach. Auto-invoke when user says "add account negatives", "add account-level negatives", "set up account negative keywords for [account(s)]", or "roll the negative-list baseline to [accounts]". Supports single-account and bulk-portfolio operations.

add-account-negative-keywords/SKILL.md

Read pinned source

Source commit 90f0e419f2d820789d5e50eee1237ab9fd14dfc6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
80
Repository last updated
Aug 25, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Add Account-Level Negative Keywords

**Purpose:** Roll a curated baseline of account-level negative keywords (the ones in
Admin → Account Settings → Negative Keywords) across one or many Google Ads accounts,
using the confirmed 3-step SharedSet approach.

**Type:** MUTATION skill. This writes to live accounts. The
[`mutation-safety`](../mutation-safety/) two-step protocol is not a step in this
workflow — it *is* the workflow: dry-run preview → human reads the plan → approval code
generated → human gives the go → execution. Never chain code generation and execution
in a single action, and never skip the preview read.

**This skill deliberately does NOT:**
- Delete or detach anything — no keyword removals, no SharedSet deletion, no list
Back to top