Working with Honeycomb SLOs, burn alerts, and SLO history
npx skills add https://github.com/bendrucker/honeycomb-cli --skill sloCopy and paste this command into Claude Code to install the skill
| name | slo |
| description | Working with Honeycomb SLOs, burn alerts, and SLO history |
Dependency chain: derived column (SLI) → SLO → burn alert. All commands require --dataset.
target_per_million: 99.9% = 999000, 99% = 990000, 95% = 950000.
slo create -f - (file-only, no flags yet — see #109)slo update <id> --name/--description/--target/--time-period (flag-based, read-modify-write) or -f (mutually exclusive)slo get <id> / slo get <id> --detailed (Enterprise-only)slo list / slo delete <id> --yesCreate body: {"name":"...","sli":{"alias":"<derived-column-alias>"},"time_period_days":30,"target_per_million":999000}
Create/update require recipients (non-empty array of {"id":"..."}) and slo as {"id":"..."} (nested, not flat slo_id).
Exhaustion time: {"alert_type":"exhaustion_time","exhaustion_minutes":240,"slo":{"id":"..."},"recipients":[{"id":"..."}]}
Budget rate: {"alert_type":"budget_rate","budget_rate_window_minutes":60,"budget_rate_decrease_threshold_per_million":50000,"slo":{"id":"..."},"recipients":[{"id":"..."}]}
All burn alert commands are file-only (-f), no flags yet (#110, #111).
slo history --slo-id <id> --start-time <unix> --end-time <unix> — --slo-id is repeatable. Response is a map keyed by SLO ID.
Manage Honeycomb boards: create, update panels, configure visualizations, and review in Chrome. Activated by explicit mention of Honeycomb boards or /board invocation.
Honeycomb CLI and MCP server usage — auth, queries, datasets, SLOs, boards, triggers, markers, columns, and raw API requests for observability workflows
Design and build Honeycomb queries: calculations, filters, breakdowns, visualization selection, granularity tuning, and anti-patterns. Activated by explicit mention of Honeycomb queries or /query invocation.
Add a new cobra subcommand to the CLI