grafana-dashboard-design

Designs Grafana dashboards with hierarchical layouts, panel selection, and alerting annotations.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill grafana-dashboard-design-snoodleboot-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grafana-dashboard-design
Source: https://github.com/snoodleboot-io/discrecontinual_equations/tree/main/.claude/skills/grafana-dashboard-design
Command: npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill grafana-dashboard-design-snoodleboot-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often build Grafana dashboards that are cluttered, inconsistent, or missing context, making it hard to monitor service health and respond to incidents quickly. ## Core Features & Use Cases - Three-Level Dashboard Hierarchy: Structures dashboards into Executive (single status), Service Overview (RED metrics), and Deep Dive (component-level detail) views. - Panel Selection Guidance: Maps metric types to the right visualization, including gauges, time-series, heatmaps, tables, and logs. - Annotations, Thresholds & Templating: Covers deploy annotations, alert threshold bands, and parameterized dashboards using Grafana variables for reuse across services and regions. - Use Case: When setting up monitoring for a new API service, use this Skill to produce a dashboard layout with RED metrics, alert thresholds, and templated variables for multi-region reuse. ## Quick Start Ask the AI to design a Grafana dashboard for your API service with RED metrics, alert thresholds, and templated variables.

Frequently Asked Questions about grafana-dashboard-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a Grafana dashboard for API monitoring?▼

Structure the dashboard in three levels: an executive view with a single health status, a service overview with RED metrics (rate, errors, duration), and a deep-dive view with per-component detail. Use gauges for single values and time-series panels for trends.

What Grafana panel type should I use for latency metrics?▼

Use a time-series panel for latency trends like p95 over time, and a heatmap for latency distribution across buckets. Reserve gauges and stat panels for single current values such as availability percentage.

How do I create reusable Grafana dashboards with variables?▼

Define template variables of type query, such as label_values(http_requests_total, job) for service selection. Reference them in panel queries like rate(http_requests_total{job="$service"}[5m]) to reuse one dashboard across services and regions.

How many panels should a Grafana dashboard have?▼

Keep dashboards under roughly 12 panels to avoid cognitive overload. Group related panels together, show the time range, and use consistent colors with units in axis labels.

How do I show deployments and alert thresholds on Grafana graphs?▼

Add annotations with timestamps and tags like deployment to mark releases on graphs. Configure threshold lines with fill colors, such as a red band at a 1% error rate, to make alert boundaries visible.