slo-check
Define and check simple service-level objectives for Claude Code from Agent Monitor data — session completion rate, tool success rate (PostToolUse/PreToolUse), and error rate (APIError/total) — then compare each to its target and report the error budget remaining. Use when reporting reliability or when someone asks "are we meeting our SLOs?".
Profile →npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill slo-check --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.
# SLO Check Turn raw event counts into a clear SLO scorecard with error-budget accounting. ## Input The user provides: **$ARGUMENTS** This may be: - empty — use the default SLO targets below over all available data - targets like "completion=95 success=99 error=1" — override the defaults (percentages) - a window like "last 7d" or "today" — restrict the measurement period Default SLO targets: completion rate ≥ 95%, tool success rate ≥ 99%, error rate ≤ 1%. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/analytics` | `event_types` (PreToolUse, PostToolUse, APIError counts), `sessions_by_status`, `daily_events` (365d), `daily_sessions` (365d) — the raw numerators/denominators for every SLI | | `GET /api/stats` | `total_sessions`, `total_events`, `events_today`, `sessions_by_status` — fleet totals and recency | | `GET /api/events?session_id=X` | Per-session stream — drill into the sessions that breach an SLO | ## Report Sections ### 1. Service Level Indicators (SLIs) Compute each SLI from `GET /api/analytics` / `GET /api/stats`: - **Completion rate** = completed sessions / total sessions (from `sessions_by_status`; count `active`/`running` as in-flight, exclud
- Input
- Data Sources
- Report Sections
- 1. Service Level Indicators (SLIs)
- 2. SLO Scorecard
- 3. Error Budget
- 4. Breach Drill-Down
- Output
What does the slo-check skill do?
Define and check simple service-level objectives for Claude Code from Agent Monitor data — session completion rate, tool success rate (PostToolUse/PreToolUse), and error rate (APIError/total) — then compare each to its target and report the error budget remaining. Use when reporting reliability or when someone asks "are we meeting our SLOs?".
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill slo-check --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.