skill-017-negative-keyword-conflict-detection

skill-017-negative-keyword-conflict-detection is a skill for Claude Code from TrueClicks/claude-plugins. It costs 33 tokens per session (648 once invoked), scanned A, original, MIT.

A Google Ads keyword-checking skill finds negative keywords, which prevent ads from appearing for matching searches, that conflict with active keywords.

In plain words
What is it for?
It compares shared-list, campaign, and ad-group negative keywords with enabled keywords and identifies direct or possible conflicts.
Why use it?
It helps explain why an ad may not show for a search the advertiser intended to target.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the google-ads plugin — 52 skills, 4 commands shipped together

Good fit It compares shared-list, campaign, and ad-group negative keywords with enabled keywords and identifies direct or possible conflicts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add TrueClicks/claude-plugins --skill skill-017-negative-keyword-conflict-detection
Clone the repo
git clone --depth 1 https://github.com/TrueClicks/claude-plugins

Made for: Claude Code.

Or install google-ads, the plugin that ships this one along with the rest of its 52 skills, 4 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for skill-017-negative-keyword-conflict-detection

README.md
[![agentmods](https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection/github.svg)](https://agentmods.dev/skills/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection)
Your own site
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for skill-017-negative-keyword-conflict-detection

Your own site · 80×15
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 648 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00648
Opus 5 $0.00016 $0.00324
Sonnet 5 $0.00007 $0.00130
Haiku 4.5 $0.00003 $0.00065

Measured 12d ago against content hash 415b430e83a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

skill-017-negative-keyword-conflict-detection scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/google-ads/skills/skill-017-negative-keyword-conflict-detection/SKILL.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill 017: Negative Keyword Conflict Detection

Purpose

Identify negative keywords that are blocking or could block desired active keywords, causing ads not to show for intended queries. Negative/positive conflicts can silently suppress valuable traffic.

Data Requirements

Data Source: Standard

Standard Data:

  • data/account/shared_negative_lists.md - Shared negative keyword lists
  • data/account/campaigns/*/negative_keywords.md - Campaign-level negatives
  • data/account/campaigns/*/*/negative_keywords.md - Ad group-level negatives
  • data/account/campaigns/*/*/keywords.md - Active positive keywords

Reference GAQL:

SELECT
  campaign.name,
  ad_group.name,
  ad_group_criterion.keyword.text,
  ad_group_criterion.keyword.match_type,
  ad_group_criterion.negative
FROM keyword_view
WHERE ad_group_criterion.status = 'ENABLED'

Use /google-ads:get-custom if you need to include shared set data.

Analysis Steps

  1. Build negative inventory: Compile all negatives with scope (shared list, campaign, ad group) and match type
  2. Build positive inventory: Compile all active keywords with match type and location
  3. Detect direct conflicts: Check if negatives would block positives (exact blocks same text, phrase blocks containing text, broad blocks all-words match)
  4. Check hierarchy conflicts: Campaign negatives blocking ad group keywords; shared list blocking campaign keywords
  5. Assess severity: Complete block (keyword fully suppressed) vs. partial/potential block

Thresholds

Condition Severity
Negative exactly matches active keyword Critical
Phrase negative contains words from active keyword Critical
Shared list negative blocks campaign keyword Critical
Broad negative words all appear in active keyword Warning
Close variant match possible Info

Output

Use Short format by default. Use Detailed if user requests comprehensive analysis.

Short:

## Negative Conflict Detection Audit
**Account:** [Name] | **Conflicts Found:** [X]

### Critical ([Count])
- **"[negative]"** (phrase) blocks **"[keyword]"** → Remove negative or use exact match
- **Shared list** "[list]" blocks campaign keyword → Remove from list

### Warnings ([Count])
- **"[negative]"** (broad) may block **"[keyword]"** → Review and test

### Recommendations
1. Remove or modify [X] blocking negatives
2. Change [X] phrase negatives to exact match

Read the full file on GitHub · 78 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 78 lines · 33 tokens per session scan A 415b430e83a1

Subscribe to this mod's changes

skill-017-negative-keyword-conflict-detection is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 648 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens