Inference Autopilot
rednote-machine-learning/Inference-autopilot
Analyze, benchmark, diagnose, and optimize large-model inference deployments from hardware inventory, model details, workload traces, and latency or throughput 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…
Install Cx Slos
$ npx skills add coralogix/cx-cli --skill cx-slos -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install coralogix/cx-cli cx-slos --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cx-slos .claude/skills/cx-slos && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cx-slos" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-slos into .claude/skills/cx-slos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-slos", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/coralogix/cx-cli/tree/master/skills/cx-slosType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add coralogix/cx-cli --skill cx-slos -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install coralogix/cx-cli cx-slos --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cx-slos .agents/skills/cx-slos && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cx-slos" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-slos into .agents/skills/cx-slos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-slos", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add coralogix/cx-cli --skill cx-slos -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install coralogix/cx-cli cx-slos --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cx-slos .cursor/skills/cx-slos && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cx-slos" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-slos into .cursor/skills/cx-slos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-slos", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/coralogix/cx-cli.git --path skills/cx-slos--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add coralogix/cx-cli --skill cx-slos -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install coralogix/cx-cli cx-slos --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cx-slos .gemini/skills/cx-slos && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cx-slos" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-slos into .gemini/skills/cx-slos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-slos", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install coralogix/cx-cli cx-slosInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add coralogix/cx-cli --skill cx-slos -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cx-slos .github/skills/cx-slos && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cx-slos" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-slos into .github/skills/cx-slos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-slos", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add coralogix/cx-cli --skill cx-slos -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install coralogix/cx-cli cx-slos --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cx-slos .opencode/skills/cx-slos && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cx-slos" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-slos into .opencode/skills/cx-slos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-slos", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cx-slos- GitHub stars
- 121
- Token cost
- ~1k tokens
- SKILL.md length
- 414 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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…
- The user asks to list SLOs
- SKILL.md covers CLI Commands, SLO Definition, Monitoring SLO Health and Creating and Updating SLOs, plus 2 more sections
- Calls jq
- Check SLO status
What it does
Cx Slos is an agent skill from coralogix/cx-cli. 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".
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Site reliability engineering. The repository describes itself as: This is the Coralogix CLI. The licence is Apache-2.0.
When your agent uses it
- The user asks to list SLOs
- Check SLO status
- Is an SLO breaching
- Service level objective
Example prompts
- “list SLOs”
- “check SLO status”
- “is an SLO breaching”
- “/cx-slos”
What it can do on your machine
Read from SKILL.md and the folder at commit c071372. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cx Slos loads about 1k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 414 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from coralogix/cx-cli at commit c071372, republished under its Apache-2.0 licence (© coralogix). 414 words, ~1,037 tokens.
Download SKILL.mdSave it as
.claude/skills/cx-slos/SKILL.md (or your agent's skills folder).- name
- cx-slos
- description
- 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".
- metadata.version
- 0.1.0
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 jsonCompare 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.
Show full SKILL.md (176 more words)Show less
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 --yesupdate 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.
© coralogix, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/cx-slos of coralogix/cx-cli.
Open the folder on GitHubat commit c071372
Compare with similar skills
Cx Slos next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cx Slos this skillcoralogix/cx-cli | 121 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Inference Autopilotrednote-machine-learning/Inference-autopilot | 144 | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| Executing Distributed System Testsshenli/distributed-system-testing | 231 | — | ~5.1k | Automated safety check: Notes | MIT | |
| Alerting Irmgrafana/skills | 282 | 1 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Slo Implementationwshobson/agents | 40k | 11 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Agentforce D360 Analyzeforcedotcom/sf-skills | 1.1k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Executing Distributed System Tests
shenli/distributed-system-testing
A skill your agent uses when running a previously designed distributed-systems test plan against a real or simulated cluster — driving fault injection, workload, chaos scenarios, linearizability /…
- Official
Alerting Irm
grafana/skills
Configure Grafana Alerting, Incident Response Management (IRM), and SLOs end-to-end — provisions Grafana-managed and data-source-managed alert rules, contact points (Slack/PagerDuty/email/webhook)…
Slo Implementation
wshobson/agents
Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting.
Agentforce D360 Analyze
forcedotcom/sf-skills
Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.
- Official
Promql
grafana/skills
Write, validate, and optimize PromQL for Prometheus / Grafana Mimir / Grafana Cloud Metrics.
More from coralogix/cx-cli
All 21 skills in this repoCx AI Center
coralogix/cx-cli
A skill your agent uses for any question or action about the user's AI/GenAI applications or agents — their behavior, prompts/responses, quality, hallucinations, guardrails, security, cost/tokens…
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"…
Cx Coding Agents
coralogix/cx-cli
A skill your agent uses when the user asks about AI Center Coding Agents data, wants to reproduce or extend the Coding Agents dashboards, or asks questions about usage, cost, tokens, sessions…
Cx Cost Optimization
coralogix/cx-cli
A skill your agent uses when the user asks to "check data usage", "list TCO policies", "reduce Coralogix costs", "optimize observability spend", "lower our logging bill", "data budget exceeded"…
Cx Data Pipeline
coralogix/cx-cli
A skill your agent uses when the user asks to "set up parsing", "create parsing rule", "extract fields from logs", "regex extraction", "log parsing", "enrich logs", "add context to logs", "custom…
Cx Telemetry Querying
coralogix/cx-cli
A skill your agent uses for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior"…
Related
Categories
Questions about Cx Slos
What does Cx Slos 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…. Cx Slos is an agent skill from coralogix/cx-cli. 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.
When should I use Cx Slos?
Cx Slos fits situations like: the user asks to list SLOs; check SLO status; is an SLO breaching; service level objective.
How do I install Cx Slos in Claude Code?
Run `npx skills add coralogix/cx-cli --skill cx-slos -a claude-code`. Or copy the skill folder (skills/cx-slos in coralogix/cx-cli) into .claude/skills/cx-slos in your project. Claude Code loads it when a task matches its description.
How do I install Cx Slos in Codex?
Run `npx skills add coralogix/cx-cli --skill cx-slos -a codex`. Or copy the skill folder (skills/cx-slos in coralogix/cx-cli) into .agents/skills/cx-slos in your project. Codex loads it when a task matches its description.
Can I use Cx Slos in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coralogix/cx-cli --skill cx-slos -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cx-slos, .gemini/skills/cx-slos, .github/skills/cx-slos and .opencode/skills/cx-slos in your project.
What does Cx Slos need to run?
Going by SKILL.md and its folder, Cx Slos needs the command-line tools its instructions call (jq).
Does Cx Slos access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cx Slos safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cx Slos use?
Cx Slos is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cx Slos use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cx Slos?
Skills that share tags, products or a category with Cx Slos: Inference Autopilot (rednote-machine-learning/Inference-autopilot, 144 stars), Executing Distributed System Tests (shenli/distributed-system-testing, 231 stars), Alerting Irm (grafana/skills, 282 stars) and Slo Implementation (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cx Slos?
coralogix (a GitHub organization) maintains it in coralogix/cx-cli, which has 121 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.
Source: coralogix/cx-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.