skill-053-location-targeting-method-audit

skill-053-location-targeting-method-audit is a skill for Claude Code from TrueClicks/claude-plugins. It costs 33 tokens per session (601 once invoked), scanned A, original, MIT.

A campaign audit skill that checks whether location targeting matches the type of business being advertised. It distinguishes targeting people physically present in an area from targeting people who are present or merely interested in it.

In plain words
What is it for?
Use it to review account and campaign data, inspect positive and negative location targeting, and flag potentially incorrect geographic settings.
Why use it?
It can reveal settings that spend money on people who are unlikely to visit a local business.

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 Use it to review account and campaign data, inspect positive and negative location targeting, and flag potentially incorrect geographic settings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/trueclicks/claude-plugins/skill-053-location-targeting-method-audit
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-053-location-targeting-method-audit
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-053-location-targeting-method-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-053-location-targeting-method-audit/github.svg)](https://agentmods.dev/skills/trueclicks/claude-plugins/skill-053-location-targeting-method-audit)
Your own site
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-053-location-targeting-method-audit"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-053-location-targeting-method-audit/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-053-location-targeting-method-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-053-location-targeting-method-audit"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-053-location-targeting-method-audit.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 601 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.00601
Opus 5 $0.00016 $0.00300
Sonnet 5 $0.00007 $0.00120
Haiku 4.5 $0.00003 $0.00060

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

Security

Grade A, and why

skill-053-location-targeting-method-audit 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 9d 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-053-location-targeting-method-audit/SKILL.md · 76 lines

How it starts

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

Skill 053: Location Targeting Method Audit

Purpose

For local businesses, "Presence" targeting is typically preferred to avoid wasted spend on users who cannot physically visit. This skill verifies campaigns use the correct location targeting method based on business type and flags potentially misconfigured campaigns.

Data Requirements

Data Source: Standard

Standard Data:

  • data/account/account_summary.md - Account context and business type
  • data/account/campaigns/*/campaign.md - Campaign settings including geo targeting type
  • data/account/campaigns/*/bid_adjustments.md - Location targeting details

Reference GAQL:

SELECT
  campaign.id,
  campaign.name,
  campaign.geo_target_type_setting.positive_geo_target_type,
  campaign.geo_target_type_setting.negative_geo_target_type,
  campaign.status
FROM campaign
WHERE campaign.status != 'REMOVED'

Use /google-ads:get-custom if geo target type settings are not in standard export.

Analysis Steps

  1. Load campaign data: Read account summary to understand business type, read each campaign.md for geo targeting settings.

  2. Identify location targeting settings: Extract positiveGeoTargetType and negativeGeoTargetType values (Presence vs PresenceOrInterest).

  3. Classify by business type: Local Service/Retail = should use Presence. E-commerce/Travel = can use PresenceOrInterest.

  4. Flag potential issues: Local business using PresenceOrInterest (wasted spend), e-commerce using Presence only (missing researchers), inconsistent settings across similar campaigns.

Thresholds

Condition Severity
Local service business with PresenceOrInterest Critical
Local retail with PresenceOrInterest High
Inconsistent settings across similar campaigns Warning
E-commerce with Presence only Info

Output

Short (default):

## Location Targeting Method Audit

**Account:** [Name] | **Campaigns Analyzed:** [X] | **Potentially Misconfigured:** [Y]

### Critical ([Count])
- **[Campaign]**: Local business using "Presence or Interest" → Change to "Presence"

### Warnings ([Count])
- **[Campaign]**: Inconsistent with other campaigns → Review for consistency

### Recommendations
1. [Priority action]
2. [Secondary action]

Read the full file on GitHub · 76 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. 9d ago First seen · 76 lines · 33 tokens per session scan A 6d246271d93e

Subscribe to this mod's changes

skill-053-location-targeting-method-audit 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 601 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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens