Name: cx-slos
Rating: 75.2 (1 reviews)
Author: coralogix

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".

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body built on executable cx slos commands and safe round-trip authoring patterns. The main gap is a minor validation checkpoint for destructive/batch operations and a small amount of introductory concept framing that could be tightened.

Suggestions

Add an explicit post-create/post-update verification step (e.g. `cx slos get <id> -o json` to confirm the definition applied) and a pre-apply JSON shape check, turning the round-trip into a validate-then-confirm feedback loop for these destructive/batch operations.

Trim the opening SLO definition and the request-based vs window-based explanation, or fold them into the field table, since Claude already knows what an SLO is.

Show a concrete multi-profile fan-out example (e.g. `-p prod -p staging`) with a note on how to compare attainment across environments, since -p is called out as repeatable but never demonstrated.

Dimension	Reasoning	Score
Conciseness	Mostly lean with compact command/field tables and code blocks, but the opening 'An SLO (Service Level Objective) defines a reliability target...' and the request-based vs window-based explanation are mild over-explanation of a concept Claude already knows that could be trimmed.	4 / 5
Actionability	Fully executable guidance throughout — real `cx slos list/get/create/update/delete` commands, a working jq projection, and a concrete round-trip authoring workflow with copy-paste-ready bash covering the common cases.	5 / 5
Workflow Clarity	Clear round-trip sequence (get → edit → create/update with --yes) with checkpoints like reviewing `effectedSloAlertIds` and comparing attainment vs. target, but no explicit post-create verification (e.g. `cx slos get` to confirm) or pre-apply JSON validation feedback loop for these destructive/batch operations.	4 / 5
Progressive Disclosure	Self-contained body appropriately organized under clear section headers with no content that belongs in a separate file, plus one-level-deep, clearly signaled cross-skill references (cx-alerts, cx-telemetry-querying, cx-cases) for easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, complete description: it states concrete capabilities, provides an explicit 'Use when' clause with natural trigger phrases, and carves out a distinct SLO-management niche. It is concise without padding and avoids over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'list and inspect SLOs', 'check whether targets and error budgets are healthy', 'create, update, or delete SLO definitions from JSON' — with comprehensive coverage of the SLO lifecycle, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	Explicitly answers both 'what' (manage SLO definitions via the cx slos CLI) and 'when' with concrete trigger phrases in a 'Use when the user asks to...' clause, matching the top anchor.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would say: 'list SLOs', 'check SLO status', 'is an SLO breaching', 'error budget', 'create an SLO', 'update an SLO', 'delete an SLO', and 'service level objective', covering synonyms and the full term.	5 / 5
Distinctiveness Conflict Risk	Clear niche (Coralogix SLO management via the cx slos CLI) with SLO-specific triggers ('error budget', 'service level objective') that minimize overlap with related alerting/case skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: coralogix/cx-cli
Path: skills/cx-slos/SKILL.md
Commit: 4aa811a

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.