Skip to main content
skill CX Codex

cx-search-dashboard — Claude Code skill: find Coralogix dashboards

Searches existing Coralogix dashboards and widgets by description or field path through the cx dashboards CLI. Useful when you want to check for duplicates before building a new dashboard.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add coralogix/cx-cli --skill cx-search-dashboard -a claude-code
Open on GitHub

What cx-search-dashboard does

The skill hands the agent a set of cx dashboards commands for looking through dashboards that already exist. There are two kinds of search: by natural-language description (cx dashboards search "<description>") and by widgets whose queries match a description or reference a specific field (cx dashboards query-search --description and --field). A full listing is available too, via cx dashboards catalog -o json.

Add -o json or -o toon for machine-readable output. Once you find a dashboard, pull its full definition with cx dashboards get <id> -o json, then create a copy from that JSON using cx dashboards create --from-file dashboard.json. Handy for reusing existing PromQL or DataPrime queries instead of writing them from scratch.

Description search is fuzzy: results are ranked by similarity, not exact match. If the first phrasing returns nothing useful, try a few more. The cx CLI has to be installed and configured — without it the commands won't run.

What it helps with

  • check whether a dashboard for a service already exists
  • find widgets that query a specific field
  • list every dashboard in the account
  • pull a dashboard's JSON and clone it
  • borrow existing PromQL or DataPrime query patterns

Example prompts for the agent

  • find a dashboard about payment service errors
  • which widgets query the $d.http.status_code field
  • show me all dashboards as JSON

How to install cx-search-dashboard

1Skills CLI (Vercel)

npx skills add coralogix/cx-cli --skill cx-search-dashboard -a claude-code

2Manually: put the files in place

~/.claude/skills/cx-search-dashboard/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cx-search-dashboard/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about cx-search-dashboard

How do I install cx-search-dashboard in Claude?

Run npx skills add coralogix/cx-cli --skill cx-search-dashboard -a claude-code. The skill lands in ~/.claude/skills/cx-search-dashboard/SKILL.md.

What does cx-search-dashboard do?

It lets the agent find existing Coralogix dashboards and widgets by description or field path using cx dashboards commands.

How is description search different from field search?

cx dashboards search finds dashboards by text description, while cx dashboards query-search --field finds widgets whose queries reference a specific field path.

Source text

SKILL.md · Apache-2.0
---
name: cx-search-dashboard
description: This skill should be used when the user asks to "find a dashboard", "search dashboards", "does a dashboard exist for X", "find widgets that query Y", "which dashboards use this field", "find a dashboard about errors", "look up dashboards by description", "search for existing monitoring dashboards", "find widgets that reference a field", or wants to discover existing Coralogix dashboards or widgets using natural-language or field-based search.
metadata:
  version: "0.1.0"
---

# Dashboard Search Skill

Use this skill to discover existing Coralogix dashboards and widgets using semantic or field-based search via the `cx dashboards` CLI commands. Before creating a new dashboard, always search first to avoid duplication.

## CLI Commands

| Command | Purpose | Key flags |
|---|---|---|
| `cx dashboards search "<description>"` | Find dashboards by natural-language description | `--limit` |
| `cx dashboards query-search --description "<text>"` | Find widgets whose queries match a description | `--limit` |
| `cx dashboards query-search --field "<field-path>"` | Find all widgets that reference a specific field | `--limit` |
| `cx dashboards catalog -o json` | List all dashboards | - |
| `cx dashboards get <id> -o json` | Get full dashboard definition | - |

**Output format:** append `-o json` or `-o toon` for machine-readable output.

## When to Use Each Command

| Goal | Command |
|---|---|
| Check if a dashboard for a service or topic already exists | `cx dashboards search` |
| Find widgets whose queries cover a topic you care about | `cx dashboards query-search --description` |
| Find widgets whose queries reference a specific field path | `cx dashboards query-search --field` |
| Browse all dashboards | `cx dashboards catalog` |

## Examples

### Find a dashboard for a service

```bash
cx dashboards search "payment service error rate"
cx dashboards search "kubernetes node cpu"
```

### Find widgets whose queries cover a topic

```bash
cx dashboards query-search --description "http 5xx error rate"
cx dashboards query-search --description "p99 latency over time"
```

### Find all widgets that reference a field

```bash
cx dashboards query-search --field '$d.http.status_code'
cx dashboards query-search --field '$d.kubernetes.pod.name'
```

This reveals query patterns already in use — useful for reusing existing approaches when adding new widgets.

### Inspect and clone a found dashboard

```bash
# Get full JSON of a dashboard you found
cx dashboards get <dashboard-id> -o json > dashboard.json
# Modify it, then create a copy
cx dashboards create --from-file dashboard.json
```

## Key Principles

- **Search before creating** — always run `cx dashboards search` before building a new dashboard to avoid duplicates
- **Use field search for discovery** — `cx dashboards query-search --field` shows how a field is already being queried, which is the fastest way to find reusable PromQL or DataPrime patterns
- **Description search is fuzzy** — the results are ranked by similarity, not exact match; try several phrasings if the first search returns nothing useful
- **Use `cx dashboards get` to inspect** — once you find a relevant dashboard or widget, pull its full JSON to study the query structure

## Related Skills

- **`cx-dashboards`** — build and deploy a new Coralogix dashboard from scratch
- **`cx-telemetry-querying`** — discover what telemetry fields and metrics exist before searching dashboards

© coralogix · Apache-2.0 · coralogix/cx-cli

Similar skills

Everything for DevOps and infrastructure →

From the same set16

cx-telemetry-querying A skill that routes telemetry questions to the right signal — metrics, logs, traces or RUM — and loads the reference files the agent needs before querying. CX Codex +1 4,700installs coralogix-docs This skill searches and reads official Coralogix documentation through cx docs search and cx docs fetch. Handy when you need to know how the platform works or how to wire up an integration. CX Codex +1 3,700installs cx-cli Teaches coding agents how to run Coralogix CLI commands, parse structured toon output, and check for tool and skill updates. CX Codex +1 3,500installs cx-alerts A skill that lets your agent manage Coralogix alert definitions from the terminal with cx alerts. Handy when someone is triaging firing rules. CX Codex +1 3,600installs cx-cost-optimization Guides your agent through diagnosing Coralogix spend spikes, tuning TCO policies, and moving cold telemetry to archive storage. CX Codex +1 3,300installs cx-olly This skill wires the Coralogix Observability Agent Olly into your coding agent: ask about alerts, metrics and logs, then pull the artifacts it generates. CX Codex +1 3,300installs cx-data-pipeline A skill for configuring parsing, enrichment and Events2Metrics in Coralogix through the cx CLI. Useful when logs need to become fields and metrics. CX Codex +1 3,300installs cx-observability-setup Configures the Coralogix observability stack via the CLI: sets up saved views, notification connectors, alert routing, and webhooks for new services. CX Codex +1 3,400installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor