regression-alert
Compare this period's reliability against the prior period using Agent Monitor data — error rate (APIError/total) and tool-failure rate (PreToolUse→PostToolUse gap) — flag any regression where reliability got worse, and optionally wire a persistent alert rule so the dashboard catches the next regres…
Install / Use
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill regression-alertInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of regression-alert
regression-alert scores 81/100 on our quality scale, 2408th of 2,771 Automation skills we index.
Its SKILL.md is 3.5 KB long, well organised into 10 sections and no code examples: a solid amount of guidance for an agent.
With 1,015 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so regression-alert is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
regression-alert compared with similar skills
All 4 of these similar skills score higher than regression-alert; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| regression-alert (this skill)by hoangsonww | 81 | 1.0k | 55d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 10d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.0k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
Frequently asked questions
- How do I install regression-alert?
- Run
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill regression-alert. The install tabs above show the steps for each supported agent. - Which AI agents does regression-alert work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is regression-alert safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is regression-alert still maintained?
- The repository was last updated about 2 months ago, so regression-alert is actively maintained.
Skill content
View source on GitHubname: regression-alert description: > Compare this period's reliability against the prior period using Agent Monitor data — error rate (APIError/total) and tool-failure rate (PreToolUse→PostToolUse gap) — flag any regression where reliability got worse, and optionally wire a persistent alert rule so the dashboard catches the next regression automatically. Use when checking whether reliability degraded.
Regression Alert
Detect whether Claude Code reliability is getting worse period-over-period, and
optionally arm an alert so it never has to be checked by hand again. Scope is
reliability/failures only — for cache/cost/compaction drift, use ccam-insights'
regression-watch instead.
Input
The user provides: $ARGUMENTS
This may be:
- empty or "all" — check error rate and tool-failure rate (default)
- "errors" — APIError-rate regression only
- "tools" — tool-failure-rate regression only
- a window like "7 vs 7" or "30 vs 30" — recent vs baseline window sizes (default: last 7 days vs the prior 7)
- "arm" — after reporting, also create an alert rule via
POST /api/alerts/rules(only on explicit request)
Data Sources
| Endpoint | Returns |
|----------|---------|
| GET /api/analytics | daily_events (365d), daily_sessions (365d), event_types — split into recent vs baseline windows to compute per-window failure rates |
| GET /api/events?session_id=X | Per-session stream — localize a regression to the sessions driving it |
| GET /api/alerts/rules | Existing alert rules — check whether a matching reliability rule already exists before arming a new one |
| POST /api/alerts/rules | Create a new alert rule (only when the user says "arm") |
Report Sections
1. Windowing
Split history into a recent window (newer) and a baseline window (the equal-length period just before it). Default: recent = last 7 days, baseline = the prior 7. Use daily_events/daily_sessions to bucket counts by day.
2. Error-Rate Regression
- Per window:
error rate = APIError count / total events. - Compare recent vs baseline. Flag if recent is higher. Report absolute change (pp) and relative change (%), plus the recent sessions contributing the most
APIErrorevents.
3. Tool-Failure-Rate Regression
- Per window:
tool-failure rate = (PreToolUse − PostToolUse) / PreToolUse. - Compare recent vs baseline. Flag a rising rate as a reliability regression. Name the tools whose gap grew most.
4. Verdict
Roll up which rates regressed, rank by relative worsening, and name the most likely driver.
5. Optional — Arm an Alert
Only if the user passed "arm". First GET /api/alerts/rules to avoid duplicates. Then POST /api/alerts/rules with a rule that fires when the regressed metric crosses a threshold near the recent value (e.g., error rate > recent rate). Echo the created rule back; do not create webhooks or fire alerts.
Output
- A Markdown table: metric | baseline | recent | Δ (pp) | Δ (%) | direction (▲ worse / ▼ better) | verdict.
- Tag each metric 🔴 (clear regression), 🟡 (within noise), or 🟢 (improved).
- Rates as percentages to 2 decimals; any currency in USD to 4 decimals.
- List the specific session IDs that contributed most to any regression.
- End with the single highest-priority regression and a concrete next step (and, if armed, the new rule's id/threshold).
- Read-only except the explicit "arm" path, which is the only write. Never mutate alert rules otherwise. If
curlcannot reachhttp://localhost:4820, tell the user to start the dashboard withnpm startfrom the repo root.
Related Skills
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.0k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.9kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
