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-065-quality-score-component-breakdowngit 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-065-quality-score-component-breakdown)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-065-quality-score-component-breakdown"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-065-quality-score-component-breakdown/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-065-quality-score-component-breakdown"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-065-quality-score-component-breakdown.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.00029 | $0.00659 |
| Opus 5.5 | $0.00012 | $0.00264 |
| Sonnet 5.5 | $0.00006 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
skill-065-quality-score-component-breakdown 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 065: Quality Score Component Breakdown
Purpose
Track the three Quality Score components separately: Expected CTR, Ad Relevance, and Landing Page Experience. Understanding which component is causing low QS enables targeted optimization.
Data Requirements
Data Source: Standard
Standard Data:
data/account/campaigns/*/*/keywords.md- Contains QS components (Expected CTR, Ad Relevance, Landing Page Experience)data/performance/campaigns/*/*/keywords_metrics_30_days.md- Performance metrics for prioritization
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,
ad_group_criterion.quality_info.creative_quality_score,
ad_group_criterion.quality_info.post_click_quality_score,
metrics.impressions,
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
Use /google-ads:get-custom if you need additional fields or filters.
Analysis Steps
- Extract component ratings: Read keywords.md files for Expected CTR, Ad Relevance, Landing Page ratings.
- Classify by component: Count keywords with Below Average for each component.
- Identify primary issues: Which component has the most Below Average ratings?
- Prioritize by spend: Focus on high-spend keywords with component issues.
Thresholds
| Condition | Severity |
|---|---|
| All 3 components Below Average | Critical |
| 2 components Below Average | Critical |
| Landing Page Below Average (account-wide) | Critical |
| Expected CTR Below Average + high spend | Warning |
| Ad Relevance Below Average | Warning |
| >30% of keywords with any Below Average | Warning |
Output
Short (default):
## Quality Score Component Audit
**Account:** [Name] | **Keywords Analyzed:** [X] | **Issues:** [Y]
### Component Summary
| Component | Below Avg | Avg | Above Avg |
|-----------|-----------|-----|-----------|
| Expected CTR | [X] | [Y] | [Z] |
| Ad Relevance | [X] | [Y] | [Z] |
| Landing Page | [X] | [Y] | [Z] |
### Critical ([Count])
- **[Keyword]**: All 3 components Below Average -> Full restructure needed
### Recommendations
1. [Priority action based on most common issue]
2. [Secondary action]
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.
- 21d ago First seen · 85 lines · 29 tokens per session scan A 9f4664d054b5
skill-065-quality-score-component-breakdown is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 29 tokens to every session and 659 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.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…