This skill should be used whenever the user runs any cx command, uses the cx CLI, Coralogix CLI, or mentions cx in the context of Coralogix observability. This skill provides cross-cutting concerns like update notifications that apply to all cx commands.

cx cli Cross cutting behaviors for all cx CLI commands. Update Notifications After running any cx command, check for update notices using the channels below (in priority order). If a newer version is available, finish answering the user's request first, then mention the update once at the end. An update notice always has two parts — binary upgrade and skills refresh. Offer both commands; don't mention only the version number or only the binary upgrade. 1. Primary — toon mode ( o toon ) Commands with output toon append a standalone trailing JSON line to stdout: Scan the last line of stdout for meta.update . When present: Binary upgrade: meta.update.binary.command (current: .binary.current , latest: .binary.latest ) Skills refresh: meta.update.skills.command 2. Schema startup check cx schema embeds the same meta.update object at the top level of the schema JSON (not a trailing line). Check meta.update.binary and meta.update.skills the same way. 3. Fallback — human readable text Also scan stderr and stdout for plain text notices. Binary and skills appear on one line, separated by : TTY text mode uses two lines with the same upgrade: ... skills: ... pattern: These appear on stderr for text/json mode after normal commands. Response template [Summarize the command result here] A newer cx version (X.Y.Z) is available — you have A.B.C. Would you like me to run <binary upgrade command and npx skills add coralogix/cx cli/skills to update? Keep it to one brief closing line. Don't repeat on later commands in the same session. General cx CLI Guidelines Always use output toon for machine readable output when processing results programmatically Use cx schema to discover available commands and their flags Commands support multi profile fan out with p profile1 p profile2 For commands that query or manage Coralogix data, use http timeout <SECONDS or CX HTTP TIMEOUT=<SECONDS to set an API request deadline. Use yes to skip confirmation prompts in scripts Use read only for safe exploration without risk of modifications

cx-cli