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-137-seasonal-competitive-pattern-trackinggit 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-137-seasonal-competitive-pattern-tracking)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-137-seasonal-competitive-pattern-tracking"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-137-seasonal-competitive-pattern-tracking/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-137-seasonal-competitive-pattern-tracking"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-137-seasonal-competitive-pattern-tracking.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.00028 | $0.00638 |
| Opus 5.5 | $0.00011 | $0.00255 |
| Sonnet 5.5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
skill-137-seasonal-performance-pattern-tracking 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 137: Seasonal Performance Pattern Tracking
Purpose
Analyze your own seasonal performance patterns across 12+ months to identify recurring trends, plan budget allocation, and set realistic targets. Understanding when impressions, costs, and conversions naturally rise or fall prevents overreacting to expected fluctuations.
Data Requirements
Data Source: Custom GAQL Required
GAQL Query:
SELECT
campaign.name,
segments.month,
metrics.impressions,
metrics.clicks,
metrics.cost_micros,
metrics.conversions,
metrics.search_impression_share
FROM campaign
WHERE campaign.advertising_channel_type = 'SEARCH'
AND segments.date BETWEEN '{start_date}' AND '{end_date}'
Run via /google-ads:get-custom. Use 12+ month date range for meaningful seasonal patterns.
Analysis Steps
- Fetch historical data: Run GAQL query covering 12+ months
- Build monthly profiles: Aggregate metrics by month to identify peaks and valleys
- Identify seasonal patterns: Holiday ramps, summer dips, Q1 resets, etc.
- Assess impression share trends: Months where IS drops may indicate increased competition
- Plan budget allocation: Recommend shifting budget toward high-performing months
Thresholds
| Condition | Severity |
|---|---|
| Conversion rate drops >30% in specific months repeatedly | Warning |
| Impression share drops >15% during peak months | Warning |
| Budget flat despite clear seasonal performance swings | Warning |
| CPA increases >25% in specific months year-over-year | Info |
Output
Short format (default):
## Seasonal Performance Audit
**Account:** [Name] | **Period:** [start] to [end] | **Campaigns:** [X]
### Monthly Performance Summary
| Month | Impressions | Clicks | Cost | Conv | IS | Trend |
|-------|-------------|--------|------|------|----|-------|
| Jan | [X] | [X] | $[X] | [X] | [X]% | Low season |
| ... | ... | ... | ... | ... | ... | ... |
### Seasonal Patterns Identified
- **Peak months:** [months] — Conversions +[X]% above average
- **Low months:** [months] — Conversions -[X]% below average
- **IS dips:** [months] — Competition increases
### Recommendations
1. Increase budget [X]% for [peak months] to capture additional volume
2. Reduce budget [X]% during [low months] to improve efficiency
3. Apply seasonality bid adjustments for [months] with predictable swings
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 · 79 lines · 28 tokens per session scan A 32999b12c0d0
skill-137-seasonal-performance-pattern-tracking is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 28 tokens to every session and 638 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…