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 regression automatically. Use when checking whether reliability degraded.
Profile →npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill regression-alert --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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/a
- Input
- Data Sources
- Report Sections
- 1. Windowing
- 2. Error-Rate Regression
- 3. Tool-Failure-Rate Regression
- 4. Verdict
- 5. Optional — Arm an Alert
- Output
What does the regression-alert skill do?
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.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill regression-alert --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.