grafana-dashboards

Create Grafana dashboards with MCP-discovered Prometheus metrics and Git-ready ConfigMap output.

1|Updated Apr 6, 2025
One-click install
npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill grafana-dashboards-david-driscoll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grafana-dashboards
Source: https://github.com/david-driscoll/stargate-command-cluster/tree/main/.agents/skills/grafana-dashboards
Command: npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill grafana-dashboards-david-driscoll

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates and iterates Grafana dashboards without guessing Prometheus metric names, while producing consistent, import-safe dashboard JSON and a Git-ready ConfigMap.

Core Features & Use Cases

  • MCP-driven metric discovery: Lists metric names, inspects metric metadata, explores label values, and tests queries before building panels.
  • Dashboard JSON authoring with guardrails: Enforces required Grafana JSON conventions (e.g., id: null, graphTooltip: 1, hardcoded Prometheus datasource uid).
  • GitOps persistence via ConfigMap sidecar compatibility: Produces a ConfigMap with the required grafana_dashboard: "true" label and correct |- JSON body, plus registration guidance for kubernetes/.../kustomization.yaml.
  • Use Cases: Creating new dashboards, modifying existing dashboard JSON, adding panels/sections, debugging blank/broken panels, and laying out dashboard grids.

Quick Start

Use the grafana-dashboards skill to author a new dashboard by first discovering the required Prometheus metrics via MCP, then pushing a draft to Grafana for screenshot review, and finally writing the Git-ready ConfigMap for the monitoring sidecar.

Frequently Asked Questions about grafana-dashboards

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

FAQPage Schema
How do I create a Grafana dashboard using Prometheus metrics without guessing names?

To create a Grafana dashboard, use MCP-based Prometheus metric discovery to list metric names, inspect metadata, and test PromQL queries before constructing panel JSON with enforced conventions like a fixed datasource UID and required dashboard fields.

Why do my Grafana dashboard panels show up blank or broken after importing?

Blank or broken Grafana dashboard panels often result from incorrect PromQL queries or missing required dashboard JSON fields. The skill enforces fixed datasource structure and required fields like `id: null` and `graphTooltip: 1` to prevent these import errors.

What is the best way to persist Grafana dashboard JSON for GitOps sidecar discovery?

The best way to persist Grafana dashboard JSON for GitOps is generating a Kubernetes ConfigMap with the `grafana_dashboard: "true"` label and correct `|-` JSON body formatting, ensuring reliable sidecar discovery and import.

How do I lay out Grafana dashboard panels in a consistent 24-column grid?

To lay out Grafana dashboard panels in a 24-column grid, apply safe dashboard JSON construction conventions that enforce consistent panel sizing and positioning, preventing layout overlaps and structural errors during dashboard authoring.

Do I need MCP tool usage to discover Prometheus metrics for Grafana dashboards?

Yes, MCP tool usage is required for Prometheus metric discovery. It allows you to list metric names, explore label values, inspect metric metadata, and test queries before building Grafana dashboard panels.