agentleFS
Sign inStart free
RojiosRojios/everything-claude-code/skills/dashboard-builder/SKILL.md

dashboard-builder

Skill1 starsChanged 7 months agoMITView on GitHub

Build monitoring dashboards that answer real operator questions for Grafana, SigNoz, and similar platforms. Use when turning metrics into a working dashboard instead of a vanity board.

14 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 10
  2. Distinctive:

    do not start from visual layout.

    line 28
  3. Distinctive:

    do not include every available metric just because it exists

    line 29
  4. Distinctive:

    do not mix health, throughput, and resource panels without structure

    line 30
  5. Distinctive:

    do not ship panels without titles, units, and sane thresholds

    line 31
  6. Distinctive:

    Every panel should answer a real question.

    line 66

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. overview
  2. performance
  3. resources
  4. 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

Related Skills

  • research-ops
  • backend-patterns
  • terminal-ops

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free