create-dashboard
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
Create Dashboard with Kopai
Component Schema (auto-generated)
!npx @kopai/cli dashboards schema 2>/dev/null || echo "ERROR: Cannot connect to Kopai backend. If running locally, start it with: npx @kopai/app start — If using a remote backend, check the url in your .kopairc file."
Available Metrics
!npx @kopai/cli metrics discover --json 2>/dev/null || echo "ERROR: Cannot connect to Kopai backend. If running locally, start it with: npx @kopai/app start — If using a remote backend, check the url in your .kopairc file."
Workflow
- Discover metrics —
npx @kopai/cli metrics discover --json - Design tree — build a uiTree using components from the schema above
- Create dashboard — pipe JSON to
npx @kopai/cli dashboards create --name "<name>" --tree-version "0.7.0" --json - Verify — response contains
id(success) orerror(failure). On error: re-runmetrics discoverto check metric names and types match the component compatibility table below, fix the tree, and retry
Quick Example
A single-card dashboard showing CPU usage:
echo '{"uiTree":{"root":"stack-1","elements":{"stack-1":{"key":"stack-1","type":"Stack","props":{"direction":"vertical","gap":"md"},"children":["card-1"],"parentKey":""},"card-1":{"key":"card-1","type":"Card","props":{"title":"CPU Usage"},"children":["ts-1"],"parentKey":"stack-1"},"ts-1":{"key":"ts-1","type":"MetricTimeSeries","props":{"height":300,"unit":"1"},"children":[],"parentKey":"card-1","dataSource":{"method":"searchMetricsPage","params":{"metricType":"Gauge","metricName":"system.cpu.utilization"}}}}},"metadata":{}}' | npx @kopai/cli dashboards create --name "CPU Dashboard" --tree-version "0.7.0" --json
Common Components
| Component | Use for | Compatible metric types |
|---|---|---|
| MetricStat | KPI numbers | Sum, Gauge |
| MetricTimeSeries | Trend charts | Sum, Gauge, Histogram |
| MetricHistogram | Distributions | Histogram, ExponentialHistogram |
| LogTimeline | Log stream | n/a (uses searchLogsPage) |
Rules
workflow- Dashboard creation workflow (detailed rules, tree structure, error handling)
Read rules/<rule-name>.md for details.
More from kopai-app/kopai-mono
otel-instrumentation
Instrument applications with OpenTelemetry SDK and validate telemetry using Kopai. Use when setting up observability, adding tracing/logging/metrics, testing instrumentation, debugging missing telemetry data, or when traces/logs/metrics aren't appearing after setup. Also use when users say things like "my traces aren't showing up", "I don't see any data", or "how do I add observability to my app".
25root-cause-analysis
Analyze telemetry data for root cause analysis using Kopai CLI. Use when debugging errors, investigating latency issues, tracing request flows across services, or correlating logs with traces. Also use when users report production issues like "why is my API slow", "getting 500 errors", "service is down", "requests are timing out", or any symptom that needs telemetry-based investigation — even if they don't mention traces or observability explicitly.
23