Agent Skills

cx-search-dashboard

devopscoralogix2.7K installs

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.

Install

npx skills add https://github.com/coralogix/cx-cli --skill cx-search-dashboard
SKILL.md

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

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

Find widgets whose queries cover a topic

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

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

# 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

Related skills

azure-diagnosticsmicrosoft608KDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, aazure-preparemicrosoft608KPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azazure-aimicrosoft608KUse for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.azure-deploymicrosoft607KExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: \"run azd up\", \"run azd deploy\", \"execute deployment\",

Search skills and MCP servers

Fuzzy search across 23,137 skills and servers