Name: cx-cases
Rating: 70.39999999999999 (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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

87%

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

A tight, highly actionable CLI skill body with excellent progressive disclosure and resolve-guardrails, held back only by the batch-operation path lacking a validation/feedback loop. Adding error handling to the bulk example would raise workflow clarity.

Suggestions

Add a validation/feedback loop to the bulk-operations example (e.g. per-item success/error reporting or a retry-on-failure step) so the batch path matches the resolve path's safety.

Optionally show the expected JSON shape returned by `cx cases get` so the inspect step's referenced fields (groupings, aiSummary, priorityDetails) are unambiguous.

Dimension	Reasoning	Score
Conciseness	Lean command table, lifecycle diagram, numbered workflow, and key principles with no padding of concepts Claude already knows; every section carries operational load.	3 / 3
Actionability	Fully executable `cx cases ...` commands with flags throughout, plus a copy-paste bulk pipe ("... \| jq -r '.[].id' \| xargs -I {} cx cases acknowledge {}") — copy-paste ready.	3 / 3
Workflow Clarity	The triage workflow is clearly sequenced with strong guardrails on the irreversible `resolve` (reason + `--yes` + "stay in ACKNOWLEDGED if uncertain"), but the bulk/batch path offers no per-item validation or feedback loop, which the rubric caps at 2.	2 / 3
Progressive Disclosure	The body is an overview pointing one level deep to clearly signaled, real references (`references/case-analytics.md`, `references/single-case.md`, both present), with detail appropriately split out.	3 / 3
	Total	11 / 12 Passed

Description

82%

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, distinctive description with strong action verbs and natural trigger terms, weakened only by the absence of an explicit "Use when..." trigger clause. Adding when-to-use guidance would lift completeness to the top level.

Suggestions

Append a "Use when triaging or driving Coralogix Cases through their lifecycle..." clause so the when-to-use trigger is explicit, not implied.

Consider naming the lifecycle states (active/acknowledged/resolved/closed) as additional trigger keywords users may mention.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "acknowledge, assign, resolve, or re-prioritize a case" plus "inspect its event timeline or notification deliveries" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	The "what" is explicit and detailed, but there is no "Use when..." clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural terms a Coralogix user would actually say ("triage and manage ... Cases", "acknowledge, assign, resolve, re-prioritize", "event timeline", "notification deliveries") give good coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to the "cx cases" CLI for Coralogix Cases with domain-specific triggers, a clear niche unlikely to collide with other skills.	3 / 3
	Total	11 / 12 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
Commit: 76b0766

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