skill-127-trending-search-term-detection

skill-127-trending-search-term-detection is a skill for Claude Code from TrueClicks/claude-plugins. It costs 26 tokens per session (620 once invoked), scanned A, original, MIT.

A search-term trend analysis for Google Ads. Search terms are the words people actually enter; the analysis compares their recent volume over time.

In plain words
What is it for?
Use it to find growing terms to consider as keywords, investigate falling terms, and spot newly appearing queries.
Why use it?
It reveals rising or declining interest that a single reporting period can hide, helping distinguish new opportunities from fading demand.

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 Use it to find growing terms to consider as keywords, investigate falling terms, and spot newly appearing queries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/trueclicks/claude-plugins/skill-127-trending-search-term-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-127-trending-search-term-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 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-127-trending-search-term-detection

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-127-trending-search-term-detection"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-127-trending-search-term-detection.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 620 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.00026 $0.00620
Opus 5.5 $0.00010 $0.00248
Sonnet 5.5 $0.00005 $0.00124
Haiku 4.5 $0.00003 $0.00062

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

Security

Grade A, and why

skill-127-trending-search-term-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 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-127-trending-search-term-detection/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.

Purpose

Analyze search term data across time periods to identify rising trends (opportunities to add as keywords), declining terms (investigate relevance), and new emerging queries worth capturing.

Data Requirements

Data Source: Standard + Custom GAQL

Standard Data:

  • data/performance/campaigns/*/*/search_terms_metrics_30_days.md - Recent search terms

GAQL Query (for trend analysis):

SELECT
  search_term_view.search_term,
  campaign.name,
  ad_group.name,
  segments.date,
  metrics.impressions,
  metrics.clicks,
  metrics.cost_micros,
  metrics.conversions
FROM search_term_view
WHERE segments.date DURING LAST_14_DAYS
  AND metrics.impressions > 0
ORDER BY search_term_view.search_term, segments.date

Run via /google-ads:get-custom with query name search_term_trends.

Analysis Steps

  1. Fetch multi-period data: Get search term data segmented by date for trend analysis
  2. Calculate week-over-week changes: Compare this week vs last week impressions/clicks
  3. Identify rising trends: Terms with >50% impression increase
  4. Flag declining terms: Terms with >30% impression decrease
  5. Spot new terms: First-time appearances with conversion potential

Thresholds

Condition Severity
New term with conversion, not added as keyword Critical
Rising term (>100% increase) with good CTR Warning
Declining term (>50% drop) with high spend Warning
High-volume term not in keyword list Info

Output

Short format (default):

## Search Term Trends Audit

**Account:** [Name] | **Period:** Last 14 days | **Trending Terms:** [X]

### Rising Trends - Add as Keywords ([Count])
- **"[Term]"**: +[X]% impressions, [Y] conversions → Add as [match type]
- **"[Term]"**: +[X]% impressions, high CTR → Add as exact match

### New High-Potential Terms ([Count])
- **"[Term]"**: First appearance, [X] conversions → Add immediately

### Declining Terms - Investigate ([Count])
- **"[Term]"**: -[X]% impressions → Check relevance/seasonality

### Recommendations
1. Add [X] rising terms as keywords
2. Investigate [Y] declining terms
3. Monitor [Z] new terms for patterns

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 · 26 tokens per session scan A ddf5e8c82e54

Subscribe to this mod's changes

skill-127-trending-search-term-detection is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 26 tokens to every session and 620 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