Dashboard Builder

Use this when the task is to build a dashboard people can operate from.

The goal is not "show every metric." The goal is to answer:

is it healthy?
where is the bottleneck?
what changed?
what action should someone take?

When to Use

"Build a Kafka monitoring dashboard"
"Create a Grafana dashboard for Elasticsearch"
"Make a SigNoz dashboard for this service"
"Turn this metrics list into a real operational dashboard"

Guardrails

do not start from visual layout; start from operator questions
do not include every available metric just because it exists
do not mix health, throughput, and resource panels without structure
do not ship panels without titles, units, and sane thresholds

Workflow

1. Define the operating questions

Organize around:

health / availability
latency / performance
throughput / volume
saturation / resources
service-specific risk

2. Study the target platform schema

Inspect existing dashboards first:

JSON structure
query language
variables
threshold styling
section layout

3. Build the minimum useful board

Recommended structure:

overview
performance
resources
service-specific section

4. Cut vanity panels

Every panel should answer a real question. If it does not, remove it.

Example Panel Sets

Elasticsearch

cluster health
shard allocation
search latency
indexing rate
JVM heap / GC

Kafka

broker count
under-replicated partitions
messages in / out
consumer lag
disk and network pressure

API gateway / ingress

request rate
p50 / p95 / p99 latency
error rate
upstream health
active connections

Quality Checklist

valid dashboard JSON
clear section grouping
titles and units are present
thresholds/status colors are meaningful
variables exist for common filters
default time range and refresh are sensible
no vanity panels with no operator value

research-ops
backend-patterns
terminal-ops

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

76/100

Grade

B

Good

Safety

90

Quality

72

Clarity

82

Completeness

65

Summary

The Dashboard Builder skill guides AI agents to construct operational monitoring dashboards for platforms like Grafana and SigNoz. It reframes dashboard design around answering real operator questions (health, bottlenecks, changes, actions) rather than displaying every available metric, and provides a structured 4-step workflow plus domain-specific panel recommendations.

Detected Capabilities

Dashboard JSON generationQuery language translation (Prometheus, Elasticsearch, etc.)Dashboard schema inspectionMetrics-to-panels mappingVariable and threshold configurationPlatform-specific formatting (Grafana/SigNoz)

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

build monitoring dashboardgrafana dashboard designoperational metrics boardkafka dashboard setupelasticsearch dashboarddashboard from metricsoperator-focused monitoring

Use Cases

Build a Kafka monitoring dashboard answering operator questions about broker health and consumer lag
Create a Grafana dashboard for Elasticsearch with cluster health, shard allocation, and JVM metrics
Design a SigNoz dashboard for an API gateway focused on latency percentiles, error rates, and upstream health
Turn a raw metrics list into an actionable dashboard with meaningful thresholds and filters
Structure multi-service dashboards around operational concerns: health, performance, resources, and service-specific risks

Quality Notes

Clear guardrails focus on operator-centric design, explicitly rejecting vanity metrics — good practice for avoiding alert fatigue
Well-structured workflow (4 steps) provides agents with a logical progression from questions to shipped dashboard
Domain-specific examples (Elasticsearch, Kafka, API gateway) anchor abstract principles to concrete use cases
Quality checklist is actionable and comprehensive (JSON validity, titles, units, thresholds, variables)
No file I/O or system integration details documented — skill is abstract and platform-agnostic, reducing implementation specificity
Related Skills links are vague (no skill IDs or versions) — may cause discovery friction if those skills do not exist
Missing: example dashboard JSON snippets for reference; missing guidance on testing/validating dashboards before shipping

Model: claude-haiku-4-5-20251001Analyzed: Jul 14, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

v1.2

Content updated

2026-07-14

Latest

v1.1