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
Install / Use
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill api-error-reportInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Our assessment of api-error-report
api-error-report scores 81/100 on our quality scale, 659th of 753 Operations skills we index.
Its SKILL.md is 2.9 KB long, well organised into 9 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 api-error-report 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.
api-error-report compared with similar skills
All 4 of these similar skills score higher than api-error-report; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| api-error-report (this skill)by hoangsonww | 81 | 1.0k | 55d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 10d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.9k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.9k | today | MCP Server |
| crawl4aiby unclecode | 100 | 87.5k | today | MCP Server |
Frequently asked questions
- How do I install api-error-report?
- Run
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill api-error-report. The install tabs above show the steps for each supported agent. - Which AI agents does api-error-report work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is api-error-report 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 api-error-report still maintained?
- The repository was last updated about 2 months ago, so api-error-report is actively maintained.
Skill content
View source on GitHubname: api-error-report description: > 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.
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/events?session_id=X and collect APIError events. Group by session_id and, via GET /api/sessions, by model. Report the top affected sessions and which model accounts for the most errors.
3. Likely Cause Classification
Inspect each error's summary/data and bucket it:
- Rate limit β mentions 429, "rate limit", "quota", or retry-after.
- Overload β mentions 529, "overloaded", or capacity.
- Context β mentions context length, token limit, or "too long" (correlate with nearby
Compactionevents). - Other β anything else; quote the
summary. Report the count and percentage in each bucket.
4. Timeline
List the most recent APIErrors with timestamp, session_id, model, classified cause, and a one-line summary excerpt.
Output
- A Markdown table per section (volume, by model, by cause).
- Rates as percentages to 2 decimals; any currency in USD to 4 decimals.
- Cite exact
session_id,model,timestamp, andsummaryvalues β never invent a cause not supported by the payload; bucket as "Other" when unclear. - End with the dominant cause and a concrete mitigation (e.g., back off and retry on 529, reduce context to cut context errors, slow request rate on 429).
- Read-only: only report what the API returns. 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.
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.
Scrapling
103.9kπ·οΈ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
crawl4ai
87.5kOfficial Crawl4AI Cloud: a hosted web scraping, extraction, and search API for AI agents. Free API key, 1,000 credits a month, no card. Fully open source: this repo is the Apache-2.0 crawler that powers it, and you can self-host it.
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.
