api-runtime-monitor
Monitors LTX API runtime performance, latency, error rates, and throughput. Alerts on performance degradation or errors.
npx skills add majiayu000/claude-skill-registry --skill api-runtime --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 Runtime Monitor ## When to use - "Monitor API latency" - "Alert on API errors" - "Track API throughput" - "Monitor inference time" - "Alert on API performance degradation" ## What it monitors - **Latency**: Request processing time, inference time, queue time - **Error rates**: % of failed requests, error types, error sources - **Throughput**: Requests per hour/day, by endpoint/model - **Performance**: P50/P95/P99 latency, success rate - **Utilization**: API usage by org, model, resolution ## Steps 1. **Gather requirements from user:** - Which performance metric to monitor (latency, errors, throughput) - Alert threshold (e.g., "P95 latency > 30s", "error rate > 5%", "throughput drops > 20%") - Time window (hourly, daily) - Scope (all requests, specific endpoint, specific org) - Notification channel 2. **Read shared files:** - `shared/bq-schema.md` — GPU cost table (has API runtime data) and ltxvapi tables - `shared/metric-standards.md` — Performance metric patterns 3. **Identify data source:** - For LTX API: Use `ltxvapi_api_requests_with_be_costs` or `gpu_request_attribution_and_cost` - **Key columns explained:** - `request_processing_time_ms`: Total time from request submiss
- When to use
- What it monitors
- Steps
- Reference files
- Rules
What does the api-runtime-monitor skill do?
Monitors LTX API runtime performance, latency, error rates, and throughput. Alerts on performance degradation or errors.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-runtime --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 majiayu000/claude-skill-registry, a repository with 534 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.