dashboard-build

Design Grafana monitoring and analytics dashboards with PromQL panels, KPI layouts, and metric selection.

15|3|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill dashboard-build-kiurakku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dashboard-build
Source: https://github.com/kiurakku/cursor-kit-for-ai/tree/main/plugins/data/skills/dashboard-build
Command: npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill dashboard-build-kiurakku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dashboards often become wall decorations that cannot answer "is it healthy?" in five seconds. This Skill structures dashboard design around a primary question and audience, so every panel earns its place and incidents are visible at a glance. ## Core Features & Use Cases - Audience-Driven Layouts: Separate designs for on-call (RED metrics), service owners (trends and error budgets), and business stakeholders (funnels and KPIs). - Panel Craft Rules: Ratios over counts, percentiles over averages, correct units and thresholds, deploy annotations, and title-as-question naming. - Ready PromQL Patterns: Example queries for error ratios and p95 latency, plus guidance for provisioning dashboards as JSON in git. - Use Case: An on-call engineer needs a service health dashboard. The Skill produces a row-by-row layout with a verdict row (availability, error rate, p95, traffic), suspect panels, dependency panels, and per-panel specs with queries and thresholds. ## Quick Start Design a Grafana dashboard for my API service that answers whether it is healthy for on-call engineers, including the panel layout and PromQL queries.

Frequently Asked Questions about dashboard-build

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

FAQPage Schema
How do I design a Grafana dashboard for on-call monitoring?▼

Start by naming the primary question and audience, then place a verdict row at top with availability, error rate, p95 latency, and traffic. Add suspect panels (errors by endpoint, saturation) and dependency panels below, using RED metrics for services and USE for resources.

What PromQL query shows error rate and p95 latency?▼

For error ratio use sum(rate(http_requests_total{status=~"5.."}[5m])) / sum(rate(http_requests_total[5m])). For p95 latency use histogram_quantile(0.95, sum(rate(http_request_duration_seconds_bucket[5m])) by (le)).

Should dashboards use averages or percentiles for latency?▼

Use percentiles (p50, p95, p99) instead of averages, because averages hide incidents. For latency distribution, a heatmap panel is preferable to a single line since it reveals the full spread of response times.

How many panels should a monitoring dashboard have?▼

Keep 3-5 stat panels above the fold so the health verdict is readable in five seconds. Every panel must have changed a decision at some point; delete panels that never do, since 40-panel dashboards cause outages to be missed.

Can Grafana dashboards be managed as code?▼

Yes, provision dashboards as JSON stored in git under a monitoring directory rather than hand-editing in the UI. Hand-edited dashboards are lost with the container, while provisioned JSON auto-loads and is reviewable in pull requests.