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-064-quality-score-distribution-analysisgit 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-064-quality-score-distribution-analysis)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-064-quality-score-distribution-analysis"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-064-quality-score-distribution-analysis/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-064-quality-score-distribution-analysis"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-064-quality-score-distribution-analysis.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.00026 | $0.00720 |
| Opus 5.5 | $0.00010 | $0.00288 |
| Sonnet 5.5 | $0.00005 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
skill-064-quality-score-distribution-analysis 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 064: Quality Score Distribution Analysis
Purpose
Monitor Quality Score distribution across keywords and flag keywords with QS of 3 or below. Low Quality Scores indicate poor ad relevance, landing page experience, or expected CTR, leading to higher CPCs and lower ad positions.
Data Requirements
Data Source: Standard
Standard Data:
data/account/campaigns/*/*/keywords.md- Keyword Quality Score data including overall QS and componentsdata/performance/campaigns/*/*/keywords_metrics_30_days.md- Keyword performance metrics
Reference GAQL:
SELECT
campaign.name,
ad_group.name,
ad_group_criterion.keyword.text,
ad_group_criterion.keyword.match_type,
ad_group_criterion.quality_info.quality_score,
ad_group_criterion.quality_info.creative_quality_score,
ad_group_criterion.quality_info.post_click_quality_score,
ad_group_criterion.quality_info.search_predicted_ctr,
metrics.impressions,
metrics.clicks,
metrics.cost_micros
FROM keyword_view
WHERE ad_group_criterion.status = 'ENABLED'
AND campaign.status = 'ENABLED'
AND segments.date DURING LAST_30_DAYS
Use /google-ads:get-custom if you need additional metrics or different date ranges.
Analysis Steps
- Load keyword QS data: Read all keywords.md files and extract Quality Score values.
- Calculate distribution: Count keywords by QS bucket (1-3, 4-5, 6-7, 8-10, N/A).
- Calculate weighted average: Weight by impressions, target weighted avg QS > 6.
- Flag critical issues: High-spend keywords with QS 1-3 are priority fixes.
Thresholds
| Condition | Severity |
|---|---|
| Keyword QS 1-3 with Cost > $100/30d | Critical |
| Keyword QS 1-3 with Impressions > 1,000 | Critical |
| >20% of keywords have QS 1-3 | Critical |
| Weighted average QS < 5 | Critical |
| Keyword QS 4-5 with Cost > $200/30d | Warning |
| Weighted average QS 5-6 | Warning |
Output
Short (default):
## Quality Score Distribution Audit
**Account:** [Name] | **Keywords Analyzed:** [X] | **Weighted Avg QS:** [Y]
### Distribution
| QS Range | Count | % |
|----------|-------|---|
| 8-10 | [X] | [%] |
| 6-7 | [X] | [%] |
| 4-5 | [X] | [%] |
| 1-3 | [X] | [%] |
### Critical ([Count])
- **[Keyword]** in [Ad Group]: QS [X], $[Cost] -> [Primary issue component]
### Recommendations
1. [Priority action]
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 · 87 lines · 26 tokens per session scan A 5362ad3013df
skill-064-quality-score-distribution-analysis 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 720 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…