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.
npx skills add TrueClicks/claude-plugins --skill skill-027-ad-strength-improvementgit clone --depth 1 https://github.com/TrueClicks/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/trueclicks/claude-plugins/skill-027-ad-strength-improvement)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-027-ad-strength-improvement"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-027-ad-strength-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.
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-027-ad-strength-improvement"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-027-ad-strength-improvement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.00658 |
| Opus 5 | $0.00013 | $0.00329 |
| Sonnet 5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
skill-027-ad-strength-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 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 027: Ad Strength Improvement
Purpose
Ad Strength is Google's assessment of RSA quality based on relevance, quantity, and diversity of assets. RSAs rated Average or Poor receive fewer impressions and miss optimization opportunities. Improving to Good or Excellent can increase impressions by 5-15%.
Data Requirements
Data Source: Standard
Standard Data:
data/account/campaigns/*/*/ads.md- RSA ad strength, headlines, descriptions
Reference GAQL:
SELECT
campaign.name,
ad_group.name,
ad_group_ad.ad.id,
ad_group_ad.ad_strength,
ad_group_ad.ad.responsive_search_ad.headlines,
ad_group_ad.ad.responsive_search_ad.descriptions,
ad_group_ad.status,
metrics.impressions,
metrics.clicks,
metrics.conversions
FROM ad_group_ad
WHERE ad_group_ad.ad.type = 'RESPONSIVE_SEARCH_AD'
AND ad_group_ad.status = 'ENABLED'
AND segments.date DURING LAST_30_DAYS
ORDER BY ad_group_ad.ad_strength ASC
Use /google-ads:get-custom for performance correlation analysis.
Analysis Steps
- Categorize by Ad Strength: Excellent (optimal), Good (acceptable), Average (needs work), Poor (priority fix)
- Diagnose issues for each below-Good RSA: Headline count, description count, duplicates, missing keyword relevance, pinning restrictions
- Analyze improvement potential: Map current assets to requirements, estimate effort vs impact
- Correlate with performance: Compare CTR/conversion rates across Ad Strength levels
- Prioritize by campaign importance: Focus on high-spend campaigns first
Thresholds
| Condition | Severity |
|---|---|
| Ad Strength = Poor | Critical |
| Ad Strength = Average | Warning |
| >50% of RSAs below Good | Critical |
| High-spend campaign with Poor Ad Strength | Critical |
Output
Short (default):
## Ad Strength Audit
**Account:** [Name] | **RSAs:** [X] | **Below Good:** [Y]%
### Critical (Poor) ([Count])
- **[Campaign] / [Ad Group]**: Headlines [X]/15, Descriptions [Y]/4 -> Add [Z] headlines, [W] descriptions
### Warnings (Average) ([Count])
- **[Campaign] / [Ad Group]**: [Specific issue] -> [Fix]
### Distribution
| Ad Strength | Count | % |
|-------------|-------|---|
| Excellent | X | X% |
| Good | X | X% |
| Average | X | X% |
| Poor | X | X% |
### Recommendations
1. [Priority action with time estimate]
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.
- 9d ago First seen · 86 lines · 25 tokens per session scan A 6ffe245a2cae
skill-027-ad-strength-improvement is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 658 once invoked, about $0.0001 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…