Name: cx-cases
Rating: 65.60000000000001 (1 reviews)
Author: coralogix

cx-cases

Triage and manage Coralogix Cases with the `cx cases` CLI — e.g. acknowledge, assign, resolve, or re-prioritize a case, or inspect its event timeline or notification deliveries.

Quality

82%

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-engineered skill body: copy-paste-ready commands, an explicit lifecycle state machine, safety rails around the irreversible resolve operation, and clean progressive disclosure into two real reference files. The only trims available are the duplicated lifecycle diagram/table and adding a lightweight post-action state check.

Dimension	Reasoning	Score
Conciseness	The body is dense with domain-specific, non-obvious knowledge (irreversibility rules, multi-profile fan-out, the never-fabricate-<base> rule) with almost no filler. Minor redundancy in rendering the lifecycle as both an ASCII diagram and a transition table keeps it at anchor 4 rather than 5.	4 / 5
Actionability	Every command appears with exact syntax and flags ("cx cases resolve <id> --reason <text>", "--yes" for non-interactive mode), plus a copy-paste bulk pattern ("jq -r '.[].id' \| xargs -I {} cx cases acknowledge {}") — fully executable, matching anchor 5.	5 / 5
Workflow Clarity	The six-step triage workflow is clearly sequenced and includes real checkpoints around the destructive resolve operation (required reason, confirmation flag, "If uncertain, stay in ACKNOWLEDGED"). It sits at anchor 4 rather than 5 because there is no post-action verification step (e.g. re-running `cx cases get` to confirm the new state).	4 / 5
Progressive Disclosure	The SKILL.md body is a concise overview and pushes detail to two clearly labeled, one-level-deep references ([references/case-analytics.md], [references/single-case.md]), both of which exist in the bundle — matching anchor 5.	5 / 5
	Total	18 / 20 Passed

Description

70%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 specific, well-scoped description with strong action verbs and a distinct niche, but it lacks an explicit 'when to use' trigger clause, leaving completeness as the main weakness. Adding a Use-when sentence and covering the remaining lifecycle actions would raise it further.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Coralogix cases, asks to acknowledge/assign/resolve a case, or wants a case's event timeline or notification deliveries."

Mention the remaining lifecycle actions (close, comment, update case fields) so the coverage reads as comprehensive rather than partial.

Include common user synonyms such as 'ticket' or 'incident investigation' to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ("acknowledge, assign, resolve, or re-prioritize a case, or inspect its event timeline or notification deliveries") anchored to a specific CLI. Falls short of anchor 5 because lifecycle actions like close, comment, and update are absent, though the 'e.g.' signals non-exhaustiveness.	4 / 5
Completeness	The 'what' is clear ("Triage and manage Coralogix Cases with the `cx cases` CLI") but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Natural terms a user would say are present ("triage", "cases", "acknowledge", "assign", "resolve", "re-prioritize", "event timeline", "notification deliveries"), but common synonyms users might use such as 'ticket' or 'incident' are missing, matching anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	"Coralogix Cases" plus the `cx cases` CLI carves a clear niche with distinct triggers; nothing generic remains that would pull in unrelated skills, matching anchor 5.	5 / 5
	Total	16 / 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-cases/SKILL.md
Commit: c071372

Reviewed: 6 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.