Agent skill · coralogix
cx-service-catalog
Query Coralogix's Service Catalog (APM v2 entities) with the `cx service-catalog` CLI — discover entity types, list known entities, check their schema, and pull aggregated or timeseries data for services, databases, operations, JVMs, and Kubernetes pods. Use when the user asks to "list services", "what entity types exist", "show me service latency", "check error rate for a service", "which pods are using the most memory", "database operation performance", "JVM GC pauses", "service health over time", "compare services by latency", "what columns are available for this entity type", "service catalog schema", or wants to explore APM entities and their metrics.
What it needs
About 5k tokens when loaded.
What this skill does
Service Catalog Skill Use this skill to discover and query Service Catalog entities — services, databases, operations, database operations, JVMs, JVM GC, Kubernetes pods, and transactions — and their columnar metrics (latency, error rate, health, resource usage, etc.) via the v2 Service Catalog API. CLI Commands Command Purpose Key flags --- --- --- cx service-catalog entity-types List entity types this account has data for - cx service-catalog schema <entity-type> Columns/labels schema for one entity type - cx service-catalog entities <entity-type> Known entities of one type (e.g. service names) - cx service-catalog data <entity-type> Aggregated column data across every entity of a type --start, --end, --column (required, repeatable); --group-by, --filter, --aggregation, --limit, --sort-column, --sort-order cx service-catalog entity-data <entity-type> <entity-id> Column data for one named entity (drilldown) --start, --end, --column (required, repeatable); --group-by, --filter, --aggregation All commands are read-only and support -o json / -o toon for structured output. Entity type accepts short forms: service, database, operation, database-operation, jvm, jvm-gc, k8s-pod, transaction (case-insensitive, hyphens or underscores). The full proto name (ENTITYTYPEK8SPOD) also works. Unknown values are rejected client-side before any request is made. --start/--end accept now, now-1h-style relative expressions, or RFC3339 timestamps. --column is required and repeatable — discover valid column ids with cx service-catalog schema <entity-type> first; the API rejects unknown ones. --filter label=value1,value2 is repeatable across distinct labels only (filters AND together); combine multiple values for the same label with commas rather than repeating the flag — repeating a label is rejected client-side. --aggregation is table (default behavior when combined with --limit/ --sort-column/--sort-order) or timeseries. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills coralogix/cx-service-catalog