New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cx Service Catalog

by coralogix in coralogix/cx-cli

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…

Apache-2.0Auto-check passedDevOps & Cloud

Install Cx Service Catalog

skills CLI
$ npx skills add coralogix/cx-cli --skill cx-service-catalog -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coralogix/cx-cli cx-service-catalog --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cx-service-catalog .claude/skills/cx-service-catalog && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cx-service-catalog
GitHub stars
121
Token cost
~2.1k tokens
SKILL.md length
782 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

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…

  • Works in 4 steps: Discover what entity types exist — never… → Check the schema for one entity type to… → List known entities of that type (e.g.… → …
  • The user asks to list services
  • SKILL.md covers CLI Commands, Inspection Workflow, Examples and Key Principles, plus 1 more section
  • Calls jq

What it does

Cx Service Catalog is an agent skill from coralogix/cx-cli. 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…

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Container orchestration, Database administration and Monitoring and alerting. It works with Kubernetes. The repository describes itself as: This is the Coralogix CLI. The licence is Apache-2.0.

When your agent uses it

  • The user asks to list services
  • What entity types exist
  • Show me service latency
  • Check error rate for a service

Example prompts

  • “list services”
  • “what entity types exist”
  • “show me service latency”
  • “/cx-service-catalog”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Discover what entity types exist — never guess, they vary by account
  2. Check the schema for one entity type to find valid column ids and
  3. List known entities of that type (e.g. service names)
  4. Query data — aggregated across all entities, or scoped to one. Column

What it can do on your machine

Read from SKILL.md and the folder at commit c071372. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cx Service Catalog loads about 2.1k tokens when it runs. Until then it costs about 171 tokens; SKILL.md has 782 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~171
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from coralogix/cx-cli at commit c071372, republished under its Apache-2.0 licence (© coralogix). 782 words, ~2,143 tokens.

Download SKILL.mdSave it as .claude/skills/cx-service-catalog/SKILL.md (or your agent's skills folder).
name
cx-service-catalog
description
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.
metadata.version
0.1.0

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

CommandPurposeKey flags
cx service-catalog entity-typesList 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 (ENTITY_TYPE_K8S_POD) 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. --limit, --sort-column, and --sort-order only apply to table — the backend silently ignores them for timeseries, so the CLI rejects that combination up front rather than sending a request whose flags are quietly dropped.
  • entity-data percent-encodes the entity id for you — pass it as returned by entities (e.g. checkout/api), quoted if it contains /.

Inspection Workflow

Four steps, and only because each one supplies an input the next one requires: entity-types gives valid <entity-type> values, schema gives valid --column ids, entities gives the entity-id for a drilldown.

  1. Discover what entity types exist — never guess, they vary by account:

    bash
    cx service-catalog entity-types -o json

  2. Check the schema for one entity type to find valid column ids and filterable/groupable labels:

    bash
    cx service-catalog schema service -o json

  3. List known entities of that type (e.g. service names):

    bash
    cx service-catalog entities service -o json

  4. Query data — aggregated across all entities, or scoped to one. Column ids, filter/group-by labels, and entity ids below are placeholders — always substitute values returned by schema/entities for the entity type in question, they vary by account and entity type:

    bash
    cx service-catalog data <entity-type> --start now-1h --end now \
  --column <column-id> --column <column-id> -o json

cx service-catalog entity-data <entity-type> <entity-id> --start now-1h --end now \
  --column <column-id> -o json

Examples

The commands below use service and k8s-pod for concreteness, but every <column-id>, <filterable-label>, <groupable-label>, and <entity-id> must come from that entity type's own schema/entities output — never assume a column or label from one entity type exists on another.

Show full SKILL.md (336 more words)Show less
Top 5 entities by a metric in the last hour
bash
cx service-catalog schema service -o json  # discover column ids first
cx service-catalog data service --start now-1h --end now \
  --column <column-id> --aggregation table \
  --sort-column <column-id> --sort-order desc --limit 5 -o json
Filter to one label value
bash
cx service-catalog schema service -o json  # discover filterable_labels first
cx service-catalog data service --start now-1h --end now \
  --column <column-id> --column <column-id> \
  --filter <filterable-label>=<value> -o json
Group by a label
bash
cx service-catalog schema service -o json  # discover groupable_labels first
cx service-catalog data service --start now-1h --end now \
  --column <column-id> --group-by <groupable-label> -o json
Kubernetes pod resource saturation
bash
cx service-catalog schema k8s-pod -o json  # discover column ids first
cx service-catalog data k8s-pod --start now-1h --end now \
  --column <column-id> --column <column-id> --column <column-id> -o json
Latency over time for one entity
bash
cx service-catalog entities service -o json  # discover entity ids first
cx service-catalog entity-data service <entity-id> --start now-24h --end now \
  --column <column-id> --aggregation timeseries -o json
Just the rows
bash
# Table responses live under .rows; timeseries under .series
cx service-catalog data service --start now-1h --end now \
  --column <column-id> -o json | jq '.rows'

Key Principles

  • Discover before querying — entity-types and schema are cheap and answer "what's valid here" before spending a data/entity-data call on a guess.
  • --column values are per-entity-type — a column valid for service may not exist for k8s-pod; always re-check schema when switching entity types.
  • Malformed responses are errors, not silent empty results — a column that is neither a value nor an error (or both) fails loudly rather than producing a partial or empty row, so a non-zero exit means investigate, not "no data".
  • A column-level error is not a command failure — an individual column can come back as {"error": "..."} inside an otherwise successful row (e.g. a query timeout for just that column); check per-column before assuming the whole request failed.
  • table vs timeseries are mutually exclusive result shapes — table responses are flat rows suitable for -o json | jq '.rows'; timeseries responses nest datapoints per series and are best consumed as raw JSON rather than forced into a table.
  • Use -o json with jq for filtering; use -o toon for token-efficient output in agent contexts.
  • Multi-profile fan-out works on every subcommand — repeat -p <profile> to compare the same entity type/data across accounts; rows and series are tagged with profile when more than one is given.
  • cx-infra — infrastructure resource health (hosts, containers) is a distinct concept from Service Catalog entity health; use cx-infra for host/instance-level monitoring and this skill for application/service-level APM entities.
  • cx-telemetry-querying — once a service or pod name surfaces from this skill's commands, pivot to raw telemetry: cx logs "filter $l.subsystemname == '<service>'" or cx search-fields "<name>" -s value to find related log/span fields. Correlate a latency or error spike with the underlying logs/spans.
  • cx-alerts — cx alerts list --name "<service-name>" finds alert definitions matching a service surfaced by this skill.
  • cx-dashboards — cx dashboards search "<service-name> ..." finds dashboards built around a service found here.

© coralogix, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/cx-service-catalog of coralogix/cx-cli.

Open the folder on GitHubat commit c071372

Compare with similar skills

Cx Service Catalog next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cx Service Catalog compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cx Service Catalog this skillcoralogix/cx-cli121—~2.1kAutomated safety check: PassApache-2.0
KubeEye Cluster Inspectionkubesphere/kubesphere17k—~3.6kAutomated safety check: PassCustom licence
Signozqjoly/GitOps112—~6.1kAutomated safety check: PassWTFPL
Grafana Dashboardpando85/kaniop132—~987Automated safety check: PassAGPL-3.0
Cloud Devopsdavila7/claude-code-templates33k4 repos~1.4kAutomated safety check: PassMIT
Alloygrafana/skills282—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • KubeEye Cluster Inspection

    kubesphere/kubesphere

    Deploys KubeEye on KubeSphere and writes InspectRule and InspectPlan resources to inspect cluster health, then retrieves the inspection reports.

    17k GitHub stars~3.6k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • Signoz

    qjoly/GitOps

    Manage the self-hosted SigNoz observability stack in this GitOps repo.

    112 GitHub stars~6.1k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Grafana Dashboard

    pando85/kaniop

    Improve and validate the Kaniop Grafana dashboard against repository metrics and the grigri live cluster.

    132 GitHub stars~987 tokensUpdated today
    DevOps & CloudAuto-check passed

  • Cloud Devops

    davila7/claude-code-templates

    Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.

    33k GitHub starsUsed in 4 repos~1.4k tokens
    DevOps & CloudAuto-check passed

  • Alloy

    grafana/skills

    Official

    Build a unified telemetry pipeline with Grafana Alloy — one OpenTelemetry-compatible binary that collects metrics, logs, traces, and profiles and ships to Grafana Cloud / Prometheus / Loki / Tempo /…

    282 GitHub stars~1.3k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Agent Install

    datadog-labs/agent-skills

    Install the Datadog Agent on Kubernetes using the Datadog Operator — required before enabling Single Step Instrumentation (SSI), which automatically instruments applications for APM without code…

    177 GitHub stars~2.1k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: warnings

More from coralogix/cx-cli

All 21 skills in this repo

  • Cx AI Center

    coralogix/cx-cli

    A skill your agent uses for any question or action about the user's AI/GenAI applications or agents — their behavior, prompts/responses, quality, hallucinations, guardrails, security, cost/tokens…

    121 GitHub stars~2.5k tokensUpdated 4 days ago
    Auto-check passed

  • Cx Alerts

    coralogix/cx-cli

    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"…

    121 GitHub stars~2.5k tokensUpdated 4 days ago
    Auto-check passed

  • Cx Coding Agents

    coralogix/cx-cli

    A skill your agent uses when the user asks about AI Center Coding Agents data, wants to reproduce or extend the Coding Agents dashboards, or asks questions about usage, cost, tokens, sessions…

    121 GitHub stars~1.8k tokensUpdated 4 days ago
    Auto-check passed

  • Cx Cost Optimization

    coralogix/cx-cli

    A skill your agent uses when the user asks to "check data usage", "list TCO policies", "reduce Coralogix costs", "optimize observability spend", "lower our logging bill", "data budget exceeded"…

    121 GitHub stars~3.4k tokensUpdated 4 days ago
    Auto-check passed

  • Cx Data Pipeline

    coralogix/cx-cli

    A skill your agent uses when the user asks to "set up parsing", "create parsing rule", "extract fields from logs", "regex extraction", "log parsing", "enrich logs", "add context to logs", "custom…

    121 GitHub stars~3k tokensUpdated 4 days ago
    Auto-check passed

  • Cx Telemetry Querying

    coralogix/cx-cli

    A skill your agent uses for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior"…

    121 GitHub stars~2.6k tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Cx Service Catalog

What does Cx Service Catalog do?

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…. Cx Service Catalog is an agent skill from coralogix/cx-cli. 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.

When should I use Cx Service Catalog?

Cx Service Catalog fits situations like: the user asks to list services; what entity types exist; show me service latency; check error rate for a service.

How do I install Cx Service Catalog in Claude Code?

Run `npx skills add coralogix/cx-cli --skill cx-service-catalog -a claude-code`. Or copy the skill folder (skills/cx-service-catalog in coralogix/cx-cli) into .claude/skills/cx-service-catalog in your project. Claude Code loads it when a task matches its description.

How do I install Cx Service Catalog in Codex?

Run `npx skills add coralogix/cx-cli --skill cx-service-catalog -a codex`. Or copy the skill folder (skills/cx-service-catalog in coralogix/cx-cli) into .agents/skills/cx-service-catalog in your project. Codex loads it when a task matches its description.

Can I use Cx Service Catalog in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coralogix/cx-cli --skill cx-service-catalog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cx-service-catalog, .gemini/skills/cx-service-catalog, .github/skills/cx-service-catalog and .opencode/skills/cx-service-catalog in your project.

What does Cx Service Catalog need to run?

Going by SKILL.md and its folder, Cx Service Catalog needs the command-line tools its instructions call (jq).

Does Cx Service Catalog access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cx Service Catalog safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cx Service Catalog use?

Cx Service Catalog is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cx Service Catalog use?

About 2.1k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cx Service Catalog?

Skills that share tags, products or a category with Cx Service Catalog: KubeEye Cluster Inspection (kubesphere/kubesphere, 17k stars), Signoz (qjoly/GitOps, 112 stars), Grafana Dashboard (pando85/kaniop, 132 stars) and Cloud Devops (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cx Service Catalog?

coralogix (a GitHub organization) maintains it in coralogix/cx-cli, which has 121 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.

Source: coralogix/cx-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.