cx-search-dashboard
Skill241 starsChanged 3 months agoApache-2.0View on GitHub
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.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-commandSkill
- add-skillSkill
- create-prSkill
- run-testsSkill
- coralogix-docsSkill
- cx-ai-centerSkill
- cx-alertsSkill
- cx-casesSkill
- cx-cliSkill
- cx-coding-agentsSkill
- cx-cost-optimizationSkill
- cx-dashboardsSkill
- cx-data-pipelineSkill
- cx-infraSkill
- cx-observability-setupSkill
- cx-ollySkill
- cx-platform-adminSkill
- cx-profilingSkill
- cx-rum-setupSkill
- cx-service-catalogSkill
- cx-slosSkill
- cx-telemetry-queryingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use this skill to discover existing Coralogix dashboards and widgets using semantic or field-based search via the cx dashboards CLI …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.jsonKey Principles
- Search before creating — always run
cx dashboards searchbefore building a new dashboard to avoid duplicates - Use field search for discovery —
cx dashboards query-search --fieldshows 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 getto 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 scratchcx-telemetry-querying— discover what telemetry fields and metrics exist before searching dashboards
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

