cx-slos
Manage Coralogix SLO (Service Level Objective) definitions with the cx slos CLI — list and inspect SLOs, check whether targets and error budgets are healthy, and create, update, or delete SLO definitions from JSON. Use when the user asks to "list SLOs", "check SLO status", "is an SLO breaching", "error budget", "create an SLO", "update an SLO", "delete an SLO", or "service level objective".
- Installs
- 2.6K
- Last 24h
- +75
- Trending rank
- #2414
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/coralogix/cx-cli --skill cx-slos- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads cx-slos automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
SLO Management Skill
An SLO (Service Level Objective) defines a reliability target for a service — e.g. "99.9% of requests succeed over 28 days". Use this skill to inspect SLO definitions, judge whether they are healthy, and manage their lifecycle.
CLI Commands
| Command | Purpose |
|---|---|
cx slos list | List all SLO definitions |
cx slos get <id> | Get a single SLO by ID |
cx slos create --from-file <path> | Create an SLO from a JSON definition [requires --yes] |
cx slos update --from-file <path> | Replace an SLO definition from JSON [requires --yes] |
cx slos delete <id> | Delete an SLO [requires --yes] |
- All commands support
-o jsonfor structured output and-p <profile>(repeatable) for multi-profile fan-out. create/updateread from--from-file <path>, or-for stdin (the default).create,update, anddeleteare write operations and require--yesin non-interactive / agent mode.
SLO Definition
The fields surfaced on every SLO:
| Field | Meaning |
|---|---|
name | Human-readable SLO name |
description | Optional description |
targetThresholdPercentage | The objective, e.g. 99.9 |
sloType | SLO_TYPE_REQUEST (request-based) or SLO_TYPE_WINDOW (window-based) |
sloTimeFrame | Rolling window, e.g. SLO_TIME_FRAME_7_DAYS, SLO_TIME_FRAME_28_DAYS |
productType | The pillar the SLO is computed from, e.g. SLO_PRODUCT_TYPE_APM |
Monitoring SLO Health
# All SLOs with their target and window
cx slos list -o json | jq '[.[] | {name, targetThresholdPercentage, sloType, sloTimeFrame}]'
# Inspect a single SLO in full
cx slos get <slo-id> -o json
Compare the live attainment against targetThresholdPercentage to judge whether
the SLO is healthy or burning error budget. A request-based SLO measures the
fraction of good events; a window-based SLO measures the fraction of good time
windows. After triage, pivot to the cx-telemetry-querying skill to find the root
cause of a breach in logs, spans, or metrics.
Creating and Updating SLOs
The safest way to author an SLO is to round-trip an existing one — template from the
exact field shape that get returns rather than hand-writing JSON:
# Template from an existing SLO, edit, then create
cx slos get <existing-slo-id> -o json > slo.json
# Edit slo.json: change name, targetThresholdPercentage, sloType, sloTimeFrame, etc.
cx slos create --from-file slo.json --yes
# Replace an existing definition
cx slos update --from-file slo.json --yes
update and delete report the alert IDs they affect (effectedSloAlertIds), so
review that list — changing or removing an SLO can disable the alerts attached to
it.
Key Principles
- Check attainment vs. target, not just existence — an SLO at 99.91% against a 99.9% target has almost no error budget left and needs attention before it breaches.
- Round-trip definitions — template create/update payloads from
cx slos getrather than hand-writing JSON, to keep the exact field shape the API expects. create/update/deleteneed--yesin agent / non-interactive mode.- Watch affected alerts —
update/deletereturneffectedSloAlertIds; deleting an SLO can silence its alerts. - Multi-profile fan-out with
-p <profile>(repeatable) to compare SLOs across environments.
Related Skills
cx-alerts— the alert definitions that fire when an SLO's error budget burns.cx-telemetry-querying— investigate the logs, spans, and metrics behind an SLO breach.cx-cases— triage the cases that group the alert events raised against a service.
FAQ
What does the cx-slos skill do?
Manage Coralogix SLO (Service Level Objective) definitions with the cx slos CLI — list and inspect SLOs, check whether targets and error budgets are healthy, and create, update, or delete SLO definitions from JSON. Use when the user asks to "list SLOs", "check SLO status", "is an SLO breaching", "error budget", "create an SLO", "update an SLO", "delete an SLO", or "service level objective".
How do I install cx-slos?
Run npx skills add https://github.com/coralogix/cx-cli --skill cx-slos in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/cx-slos/ (personal) or .claude/skills/cx-slos/ (project).
Which AI agents can use cx-slos?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is cx-slos safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains cx-slos?
It is published by coralogix in coralogix/cx-cli. It has 2,573 recorded installs.
More from coralogix/cx-cli
cx-telemetry-querying
coralogix/cx-cli
Use this skill for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior", "understand a production incident", "query telemetry data", "look at logs", "search logs", "find errors", "find stack traces", "filter by severity", "check traces", "examine spans", "investigate request latency", "debug service-to-service calls", "look up a trace ID", "analyze RUM data", "query rum.events", "check frontend performance", "frontend errors", "Core Web Vitals", "JavaScript exceptions", "query metrics", "check CPU usage", "run a PromQL query", "check error rate", "look up a metric", "check memory usage", "how do I write a DataPrime query", "DataPrime syntax", or wants to answer questions using observability data from logs, metrics, traces, RUM, or APM.
cx-search-dashboard
coralogix/cx-cli
This skill should be used when the user asks to "find a dashboard", "search dashboards", "does a dashboard exist for X", "find widgets that query Y", "which dashboards use this field", "find a dashboard about errors", "look up dashboards by description", "search for existing monitoring dashboards", "find widgets that reference a field", or wants to discover existing Coralogix dashboards or widgets using natural-language or field-based search.
coralogix-docs
coralogix/cx-cli
Search and read official Coralogix platform documentation using cx docs search and cx docs fetch. Use when the user asks how Coralogix features work, how to configure or use the UI, set up integrations (OpenTelemetry, agents, collectors, webhooks), manage API keys, explore spans/traces/logs in the product, configure alerts/SLOs/dashboards, or needs authoritative product docs — not live tenant telemetry.
cx-alerts
coralogix/cx-cli
This skill should be used when the user asks to "manage alerts", "create alert", "list alerts", "delete alert", "check alert status", "enable alert", "disable alert", "investigate firing alerts", "check which alerts are active", "find alerting rules", "set up an alert", "configure alerting", "mute an alert", "silence an alert", "see alert definitions", "check alert priority", or wants to manage Coralogix alert definitions using the cx CLI.
cx-cli
coralogix/cx-cli
This skill should be used whenever the user runs any cx command, uses the cx CLI, Coralogix CLI, or mentions cx in the context of Coralogix observability. This skill provides cross-cutting concerns like update notifications that apply to all cx commands.
cx-observability-setup
coralogix/cx-cli
Use this skill when the user asks to "set up monitoring", "configure observability", "onboard new service", "create saved view", "set up notifications", "configure webhook", "set up Slack integration", "outgoing webhook", "automation action", "webhook for alerts", "create view", "saved view", "view folder", "organize dashboards", "install integration", "configure extension", "contextual data", "connect external service", "create notification connector", "set up email alerts", "configure PagerDuty", "notification routing", "deploy extension", "test webhook", "notification preset", "test notification", "webhook actions", or wants to set up, configure, or manage the observability stack for a service or team.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.