cx-alerts
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", "check which alerts are active", "find alerting rules", "set up an alert", "configure alerting", "mute an alert", "silence an alert", "see alert definitions", "check alert priority", or wants to manage Coralogix alert definitions using the cx CLI.
66
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/cx-alerts/SKILL.mdQuality
Discovery
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger term coverage and distinctiveness, providing an extensive list of natural phrases users might say and clearly identifying its niche (Coralogix alerts via cx CLI). However, it reads more like a keyword dump than a proper skill description — it lacks a clear statement of what the skill actually does (its concrete capabilities and outputs). Adding a concise 'what it does' section would significantly improve it.
Suggestions
Add a clear capability statement before the trigger phrases, e.g., 'Creates, lists, deletes, enables, disables, mutes, and investigates Coralogix alert definitions using the cx CLI. Supports configuring alert priorities, silencing rules, and viewing active/firing alerts.'
Restructure to lead with 'what it does' followed by 'Use when...' rather than starting with trigger phrases, to better balance completeness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Coralogix alert management via cx CLI) and mentions actions like create, list, delete, enable, disable, mute, and investigate alerts. However, it doesn't clearly describe concrete capabilities beyond listing trigger phrases — it's more of a keyword list than a capability description. | 2 / 3 |
Completeness | The 'when' is extensively covered with explicit trigger phrases. However, the 'what does this do' part is weak — it only says 'manage Coralogix alert definitions using the cx CLI' at the end without describing the actual capabilities, outputs, or workflow. The description is essentially all 'when' with minimal 'what'. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'manage alerts', 'create alert', 'list alerts', 'delete alert', 'enable alert', 'disable alert', 'mute an alert', 'silence an alert', 'check alert status', 'investigate firing alerts', 'configure alerting', etc. These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — it specifically targets Coralogix alert definitions via the cx CLI, which is a very clear niche. The combination of 'Coralogix' and 'cx CLI' makes it unlikely to conflict with other alerting or monitoring skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides actionable CLI commands, complete JSON examples, and clear workflows for alert management. The progressive disclosure is excellent with well-signaled references to deeper schema and query documentation. Minor improvements could be made in conciseness by eliminating the duplicated suppression rules command listing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — the suppression rules commands are listed twice (once in the main CLI table and again in the Suppression Rules section). The alert types table and priority table are useful reference material but could be more compact. Overall reasonably lean but not maximally token-efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands, complete JSON examples for three different alert types, and concrete bash snippets for investigation workflows. The examples are copy-paste ready with realistic field values and proper API wire format. | 3 / 3 |
Workflow Clarity | The create workflow has a clear 6-step sequence with a verification step at the end. The investigation workflow provides concrete steps for finding firing alerts, inspecting them, and temporarily muting. The structural note about the type field being a sibling (not nested) is a valuable gotcha. The 'Key Principles' section reinforces verification and safe practices (disable don't delete). | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections and references five specific reference files for deeper content (alert schemas, DataPrime, PromQL, logs querying, spans querying). References are one level deep, clearly signaled with descriptions, and the main content stands alone as a useful guide without requiring them. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coralogix/cx-cli
- Commit
34d6303
- Reviewed
Table of Contents
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.