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

91%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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 skill body: executable CLI commands, a clear lifecycle model, a sequenced triage workflow with validation checkpoints for the destructive resolve step, and clean one-level-deep references. Little to improve.

Dimension	Reasoning	Score
Conciseness	The body is lean — a dense CLI table, an ASCII lifecycle plus transition table, a concrete numbered workflow, and a principles list — assuming Claude's competence without explaining concepts it already knows; every section earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands with flags throughout (e.g. `cx cases resolve <id> --reason <text>`, the `jq \| xargs` bulk example), matching the anchor for specific executable examples.	3 / 3
Workflow Clarity	The Triage Workflow is a clear Inspect→Investigate→Claim→Record→Resolve/Close→Re-prioritize sequence with explicit safety checkpoints for the irreversible resolve (reason required, `--yes` confirmation, 'stay in ACKNOWLEDGED until confident').	3 / 3
Progressive Disclosure	SKILL.md acts as an overview with two well-signaled, one-level-deep references (case-analytics.md, single-case.md), both verified to exist, with no nested reference chains.	3 / 3
	Total	12 / 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, well-scoped description that names concrete actions and uses natural trigger terms for a clearly distinct niche. Its only gap is the absence of an explicit 'Use when...' clause, which leaves the 'when to use it' half implicit.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when triaging or managing Coralogix Cases via the cx cases CLI — acknowledging, assigning, resolving, re-prioritizing, or inspecting a case's timeline/notifications.'

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'acknowledge, assign, resolve, or re-prioritize a case, or inspect its event timeline or notification deliveries' — matching the anchor for several specific concrete actions.	3 / 3
Completeness	It clearly answers 'what' (triage/manage cases via the CLI) but provides no explicit 'Use when...' trigger guidance, so per the rubric missing trigger guidance caps completeness at 2; the 'e.g.' only lists actions, not usage conditions.	2 / 3
Trigger Term Quality	Uses natural terms a user would actually say — 'Coralogix Cases', 'acknowledge', 'assign', 'resolve', 're-prioritize', 'event timeline', 'notification deliveries' — giving good coverage rather than opaque jargon.	3 / 3
Distinctiveness Conflict Risk	Anchored to a clear niche ('Coralogix Cases' / the `cx cases` CLI) with distinct triggers, making it unlikely to fire for unrelated 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: 6574ecc

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