grafana

name

grafana

description

Use when someone needs the right Grafana dashboard for a symptom — high latency, error-rate spike, saturated nodes, queue backlog, a cost/egress jump — or asks for a dashboard link, a datasource UID, or which cluster/region variables to set. Reach for this whenever building a Grafana URL or picking a panel, because the datasource UIDs and org/cluster values are not guessable and a link built with the wrong one silently shows an empty or wrong-org dashboard. Not for building/designing dashboards in code, configuring a new datasource or alert rule, writing PromQL, debugging the Grafana instance, or Grafana pricing — this only finds the right existing dashboard.

grafana

Overview

This is a pure reference skill — a lookup table, no scripts. It maps symptoms to the correct dashboard, records the canonical datasource UIDs, cluster/region names, and org IDs, and lists the variables a link needs before it resolves. Grafana links are fragile: a dashboard rendered against the wrong datasource UID or without the org pre-selected looks broken even when nothing is wrong. This skill exists so Claude builds a link that actually loads the right data the first time.

All the data lives in references/dashboards.md. This file tells Claude when to open it and the few rules that keep a constructed link from silently failing.

When to Use

Use this skill when the request is to:

• Find the dashboard for a symptom ("p99 latency is up," "5xx spike," "nodes are saturated," "the bill jumped").
• Get a datasource UID, cluster name, region, or org ID to build a Grafana link or query.
• Construct a Grafana URL with the correct var-* template variables set.
• Sanity-check why a Grafana link someone shared shows no data.

Do NOT use this for: querying the event warehouse or building funnels (funnel-query), or cohort/retention statistics (cohort-compare). This skill does not fetch or compute anything — it tells you which pre-built dashboard to open and how to address it correctly. If the question needs raw data manipulation, it's the wrong skill.