Use this skill when working with Elastic SLOs (Service Level Objectives). Activate when the user asks about SLO status, burn rates, error budgets, or needs to create and manage SLO definitions.
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/opencode/src/elastic/skills/slo-management/SKILL.mdList all SLOs and their current status:
elastic slos listList SLO definitions for configuration review:
elastic slos list-definitions| Status | Meaning | Action |
|---|---|---|
| Healthy | Within error budget | No action needed |
| Degraded | Budget being consumed faster than expected | Monitor closely |
| Breached | Error budget exhausted | Immediate investigation required |
SLO data is stored in Elasticsearch indices. Query the rollup data:
elastic es query 'FROM .slo-observability.sli-v3* | STATS good = SUM(slo.numerator), total = SUM(slo.denominator) BY slo.id, slo.name | EVAL sli = good / total * 100 | SORT sli ASC | LIMIT 20'2e200ec
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.