PluginBench
Skill
Pass
Audit score 90

cx-cli

coralogix/cx-cli

Cross-cutting behaviors and update notifications for all cx CLI commands.

What is cx-cli?

This skill handles shared concerns across all Coralogix CLI (cx) commands, including update notifications for both the binary and skills. Use it whenever running any cx command or working with Coralogix observability.

  • Detects and reports available updates for the cx binary and skills packages
  • Scans multiple notification channels: toon mode JSON, schema startup checks, and human-readable text
  • Offers both binary upgrade and skills refresh commands when updates are available
  • Provides general cx CLI guidelines including output formatting, profile fan-out, and timeout configuration

How to install cx-cli

npx skills add https://github.com/coralogix/cx-cli --skill cx-cli
Claude Code
Cursor
Windsurf
Cline

How to use cx-cli

  1. 1.Run any cx command as normal
  2. 2.Check the command output for update notifications in JSON (toon mode), schema, or text format
  3. 3.If an update is available, the skill will summarize the result and offer to run the upgrade commands
  4. 4.Accept the upgrade to update both the cx binary and skills package
  5. 5.For subsequent commands, use --output toon for machine-readable results, -p for multi-profile queries, and --http-timeout to set API deadlines

Use cases

Good for
  • Running cx commands and receiving update notifications before completing the session
  • Discovering available cx commands and their flags via cx schema
  • Executing multi-profile queries across different Coralogix configurations
  • Setting API request timeouts for long-running or slow-network scenarios
  • Running cx commands in scripts with confirmation prompts skipped
Who it's for
  • DevOps engineers using Coralogix observability
  • SREs managing multiple Coralogix profiles or environments
  • Developers integrating cx CLI into automation scripts
  • Teams needing programmatic access to Coralogix data

cx-cli FAQ

Where does the skill look for update notifications?

It checks three channels in priority order: toon mode JSON (trailing line in stdout), schema startup checks (top-level _meta.update), and fallback human-readable text on stderr/stdout.

What should I do when an update is available?

The skill will offer both the binary upgrade command and the skills refresh command. Run both to stay current with the latest cx CLI and skills.

How do I use cx with multiple Coralogix profiles?

Use the -p flag multiple times: cx command -p profile1 -p profile2 to fan-out queries across profiles.

How can I set API request timeouts?

Use --http-timeout <SECONDS> flag on individual commands or set the CX_HTTP_TIMEOUT environment variable globally.

Can I run cx commands in scripts without confirmation prompts?

Yes, use the --yes flag to skip confirmation prompts, and --read-only for safe exploration without risk of modifications.

Full instructions (SKILL.md)

Source of truth, from coralogix/cx-cli.


name: cx-cli description: 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. metadata: version: "0.1.0"

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:

{"_meta":{"update":{"binary":{"current":"0.1.7","latest":"0.2.0","command":"brew upgrade cx"},"skills":{"command":"npx skills add coralogix/cx-cli/skills","docs":"https://github.com/coralogix/cx-cli#install"}}}}

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 |:

[cx update] v0.2.0 available (you have 0.1.9) | upgrade: brew upgrade cx | skills: npx skills add coralogix/cx-cli/skills

TTY text mode uses two lines with the same upgrade: ... | skills: ... pattern:

cx 0.2.0 is available (you have 0.1.9).
upgrade: brew upgrade cx | skills: npx skills add coralogix/cx-cli/skills

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