dashboard-builder — Claude Code skill: what it does, how to install
Builds operational monitoring dashboards for Grafana and SigNoz based on incident response questions instead of vanity metric lists.
npx skills add affaan-m/ECC --skill dashboard-builder -a claude-codeWhat dashboard-builder does
This skill structures dashboards around operational questions. Instead of dumping every metric into one view, it directs the agent to build sections for health, performance, saturation, and service risks. Unhelpful panels are pruned immediately.
The workflow covers four stages. The agent defines key operator questions, inspects the target JSON schema and query language, assembles the minimum useful board, and verifies units and thresholds. Built-in metric patterns cover Kafka, Elasticsearch, and API gateways.
Install this skill when you need an actionable incident board. If you only need a quick one-line chart, standard prompting will suffice.
What it helps with
- Build an operational Kafka dashboard tracking consumer lag and under-replicated partitions
- Generate an Elasticsearch monitoring board with shard allocation and JVM heap metrics
- Structure raw service metrics into valid Grafana or SigNoz JSON
- Set up API gateway panels grouped by error rates, p95/p99 latency, and upstream health
Example prompts for the agent
- Build a Kafka monitoring dashboard
- Create a Grafana dashboard for Elasticsearch
- Turn this metrics list into a real operational dashboard
How to install dashboard-builder
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill dashboard-builder -a claude-code2Manually: put the files in place
~/.claude/skills/dashboard-builder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/dashboard-builder/
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill dashboard-builder -a codex2Manually: put the files in place
.agents/skills/dashboard-builder/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill dashboard-builder -a cursor2Manually: put the files in place
.cursor/skills/dashboard-builder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install affaan-m/ECC dashboard-builder2Manually: put the files in place
.github/skills/dashboard-builder/SKILL.md1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill dashboard-builder -a gemini-cli2Platform CLI
gemini skills install https://github.com/affaan-m/ECC --path skills/dashboard-builderManually: put the files in place
.devin/skills/dashboard-builder/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill dashboard-builder -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set146
The whole set →Similar
Questions about dashboard-builder
How do I install dashboard-builder in Claude Code?
Run npx skills add affaan-m/ECC --skill dashboard-builder -a claude-code. It writes the skill definition to ~/.claude/skills/dashboard-builder/SKILL.md.
What does dashboard-builder do?
It guides the agent to build monitoring boards answering concrete operator questions. It also enforces proper section layouts, units, status thresholds, and template variables.
Which platforms and systems does it support?
It targets platforms like Grafana and SigNoz. Built-in guidance covers metric sets for Elasticsearch clusters, Kafka brokers, and API gateways.
Source text
SKILL.md · MIT
--- name: dashboard-builder description: 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. metadata: version: "1.0.0" origin: ECC direct-port adaptation --- # 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`
© affaan-m · MIT · affaan-m/ECC