api-error-report
Produce a detailed report on APIError events from Agent Monitor data — counts over time, which sessions and models are affected, and the likely root cause (rate limits, overload/529, or context-window pressure) inferred from each event's summary and data payload. Use when API errors spike or when you need to explain why requests are failing.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill api-error-report --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.
# API Error Report Drill into `APIError` events: how many, when, where, and most likely why. ## Input The user provides: **$ARGUMENTS** This may be: - empty or "all" — report on every APIError in the recent window (default) - a session ID — report APIErrors for that one session only - a window like "today" or "last 7d" — restrict the time range - a cause filter: "rate-limit", "overload", or "context" ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/analytics` | `event_types` (total `APIError` count), `daily_events` (365d) — APIError volume and trend over time | | `GET /api/events?session_id=X` | Per-session event stream — each `APIError` carries `summary`, `data`, and `timestamp` used to classify the cause | | `GET /api/sessions?limit=N` | Sessions with `id`, `model`, `started_at` — attribute each error to a model and place it on the timeline | ## Report Sections ### 1. Volume & Trend From `GET /api/analytics`: total `APIError` count and its share of `total_events`. Use `daily_events` to chart APIErrors over the requested window and flag any day that spikes above the window mean. ### 2. Affected Sessions & Models For each session in scope, pull `GET /api/ev
- Input
- Data Sources
- Report Sections
- 1. Volume & Trend
- 2. Affected Sessions & Models
- 3. Likely Cause Classification
- 4. Timeline
- Output
What does the api-error-report skill do?
Produce a detailed report on APIError events from Agent Monitor data — counts over time, which sessions and models are affected, and the likely root cause (rate limits, overload/529, or context-window pressure) inferred from each event's summary and data payload. Use when API errors spike or when you need to explain why requests are failing.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill api-error-report --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.