Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From observability-ops
Defines SLO/SLI for a specified service and tracks its reliability metrics, optionally by type like availability or latency.
npx claudepluginhub dotclaude/marketplace --plugin observability-opsHow this command is triggered — by the user, by Claude, or both
Slash command
/observability-ops:slo <service> [type]sonnetThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Slo Command SLO/SLI definition and reliability tracking ## Arguments **$1 (Required)**: service **$2 (Optional)**: type ## Examples Invoke the sre-engineer agent with: $ARGUMENTS
/track-sla-sliDefines SLIs with measurement methods, sets SLO targets and error budgets, generates monitoring code, dashboard configs, and alerts for tracking SLAs/SLOs.
/observabilityInstruments services with structured logging, Prometheus metrics, and OpenTelemetry tracing. Also supports Grafana dashboards, alerting rules, SLOs, k6 load tests, and capacity planning.
/hatch3r-slo-scaffoldGenerates baseline SLI/SLO scaffolding for a user-facing service: availability + latency p95/p99 objectives, 28-day error budget, and Google-SRE multi-window multi-burn-rate alert rules in OpenSLO format.
Share bugs, ideas, or general feedback.
SLO/SLI definition and reliability tracking
$1 (Required): service
$2 (Optional): type
/slo "payment-api" availability
/slo "search-service" latency
Invoke the sre-engineer agent with: $ARGUMENTS