Agent skill · software engineering · coralogix
add-command
Use this skill when the user asks to "add a command", "implement cx <something>", "new subcommand", "new CLI command", "add a new cx command", "create a command", "add subcommand", "implement a new command", "build a cx command", "wire up a new command", "extend the CLI", "add an API to cx", "new cx feature", "integrate a Coralogix API", or wants to add new functionality to the cx CLI. Use this even when the user describes a feature that implies a new command without saying "command" explicitly.
Why this skill is useful
Provides detailed workflows and templates for integrating new commands into the cx CLI, which the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-06. 114 stars on the source repository.
What this skill does
Add a CLI Command End-to-end workflow for adding a new command to cx. Every command falls into one of two archetypes - determine which one first, then follow the corresponding steps. docs/adding-a-command.md has copy-pasteable code templates for every step below. Read it alongside this workflow. Step 0: Understand What You're Building Before writing any code, get clarity on the domain: 1. What Coralogix API are you wrapping? Find the API docs or example responses. Understand the data model - what entities exist, what fields they have, what operations are supported. 2. What should the user be able to do? List the subcommands (e.g., list, get, create) and what flags make sense. 3. Does this belong under a wrapper group? The CLI organizes related commands into wrapper groups. Check if your command fits under an existing group before creating a top-level command: cx alerts - alert definitions + schedulers cx notifications - connectors, routers, presets, test cx webhooks - outgoing webhooks + actions cx enrichments - enrichment rules + custom enrichment tables cx integrations - integrations + extensions, contextual-data cx iam - api-keys, roles, scopes, users, groups, ip-access Run cx schema to see the full command tree as JSON. 4. Which archetype fits? Archetype When to use Reference implementation ----------- ------------ -------------------------- A: DataPrime-based Querying logs, spans, or any DataPrime source src/commands/logs/mod.rs B: REST-based Wrapping a Coralogix REST API (most new commands) src/commands/alerts/api.rs + src/commands/alerts/mod.rs DataPrime commands delegate to a shared pipeline and require minimal code (~130 lines). REST commands build the full pipeline (API client, fan-out, merge, render) - more code but more control. Important: All API integrations must use REST (HTTP). The CLI is HTTP-only by design - do not use gRPC. Step 1: Read Reference Implementations Before writing any code, read these files to internalize the existing patterns. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills coralogix/add-command