Home/Data Analysis/dashboard-builder
D

dashboard-builder

by @affaan-mv
4.4(6)

Builds actionable monitoring dashboards, focusing on health status, bottleneck identification, change analysis, and actionable recommendations, rather than just piling up metrics.

data-visualizationmonitoringdashboarddata-analysisGitHub
Installation
npx skills add affaan-m/everything-claude-code --skill dashboard-builder
compare_arrows

Before / After Comparison

1
Before

Manually switching between multiple tools to view logs, metrics, and traces, making it difficult to correlate events and requiring additional time to pinpoint the root cause after an issue is found.

After

A single dashboard displays key health metrics, highlights anomalies, and shows pending actions, automatically correlating relevant logs and traces, allowing issues to be located within 5 minutes.

SKILL.md

dashboard-builder

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:

  • overview

  • performance

  • resources

  • 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

Weekly Installs509Repositoryaffaan-m/everyt…ude-codeGitHub Stars156.2KFirst Seen9 days agoSecurity AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled oncodex478opencode463gemini-cli460github-copilot459amp459cline459

User Reviews (0)

Write a Review

Effect
Usability
Docs
Compatibility

No reviews yet

Statistics

Installs2.7K
Rating4.4 / 5.0
Version
Updated2026年5月23日
Comparisons1

User Rating

4.4(6)
5
50%
4
33%
3
17%
2
0%
1
0%

Rate this Skill

0.0

Compatible Platforms

🔧Claude Code

Timeline

Created2026年4月16日
Last Updated2026年5月23日