skill-067-expected-ctr-improvement

skill-067-expected-ctr-improvement is a skill for Claude Code from TrueClicks/claude-plugins. It costs 23 tokens per session (614 once invoked), scanned A, original, MIT.

A Google Ads check that finds keywords with below-average expected click-through rate (CTR), meaning the estimated chance that a searcher will click the ad, and suggests improvements.

In plain words
What is it for?
It is for reviewing search keywords, ad copy, recent clicks, impressions, and spend to identify likely CTR problems.
Why use it?
It helps explain why ads may receive few clicks, cost more, or appear lower. It turns a low CTR warning into specific ad or keyword changes to review.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

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

Good fit It is for reviewing search keywords, ad copy, recent clicks, impressions, and spend to identify likely CTR problems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/trueclicks/claude-plugins/skill-067-expected-ctr-improvement
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-067-expected-ctr-improvement
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 145 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-067-expected-ctr-improvement

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-067-expected-ctr-improvement"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-067-expected-ctr-improvement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 614 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.00023 $0.00614
Opus 5.5 $0.00009 $0.00246
Sonnet 5.5 $0.00005 $0.00123
Haiku 4.5 $0.00002 $0.00061

Measured 21d ago against content hash e3849b0e36ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

skill-067-expected-ctr-improvement 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 21d 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-067-expected-ctr-improvement/SKILL.md · 83 lines

How it starts

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

Skill 067: Expected CTR Improvement

Purpose

Find keywords with "Below Average" Expected CTR and recommend improvements. Expected CTR is based on historical click-through rates and is a key Quality Score component that directly impacts ad costs and positions.

Data Requirements

Data Source: Standard

Standard Data:

  • data/account/campaigns/*/*/keywords.md - Keyword QS components including Expected CTR
  • data/account/campaigns/*/*/ads.md - Ad copy to review for CTR issues
  • data/performance/campaigns/*/*/keywords_metrics_30_days.md - CTR performance data

Reference GAQL:

SELECT
  campaign.name,
  ad_group.name,
  ad_group_criterion.keyword.text,
  ad_group_criterion.quality_info.quality_score,
  ad_group_criterion.quality_info.search_predicted_ctr,
  metrics.impressions,
  metrics.clicks,
  metrics.ctr,
  metrics.cost_micros
FROM keyword_view
WHERE ad_group_criterion.status = 'ENABLED'
  AND campaign.status = 'ENABLED'
  AND metrics.impressions > 100
  AND segments.date DURING LAST_30_DAYS
ORDER BY metrics.cost_micros DESC

Use /google-ads:get-custom if you need additional CTR metrics.

Analysis Steps

  1. Identify Below Average Expected CTR: Filter keywords with search_predicted_ctr = BELOW_AVERAGE.
  2. Analyze associated ads: Check if keyword appears in headlines, evaluate ad copy quality.
  3. Review actual CTR: Compare to ad group and campaign averages.
  4. Generate recommendations: Ad copy improvements, extensions, restructuring.

Thresholds

Condition Severity
Expected CTR Below Average + Cost > $500/30d Critical
>30% of keywords have Below Average Expected CTR Critical
Keyword not appearing in any ad headline Critical
Expected CTR Below Average + high impressions Warning
Missing ad extensions in ad group Warning
Actual CTR below 1% for Search Warning

Output

Short (default):

## Expected CTR Improvement Audit

**Account:** [Name] | **Keywords Analyzed:** [X] | **Below Average CTR:** [Y]

### Critical ([Count])
- **[Keyword]** in [Ad Group]: Below Avg Expected CTR, $[Cost] -> Add keyword to headline

### Warnings ([Count])
- **[Keyword]**: [Issue] -> [Fix]

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

Read the full file on GitHub · 83 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. 21d ago First seen · 83 lines · 23 tokens per session scan A e3849b0e36ee

Subscribe to this mod's changes

skill-067-expected-ctr-improvement is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 23 tokens to every session and 614 once invoked, about $0.0001 per session on Opus 5.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-10-08.

Related

Other skills, from other repositories

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

systematic-debugging

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

obra/superpowers · 21 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