Claude MarketplacesSubmit

Dashboard Builder

affaan-m/everything-claude-code

This walks you through building monitoring dashboards that actually help operators, not just display metrics. It starts from operator questions (is it healthy? where's the bottleneck? what changed?) before touching layout, which keeps you from building vanity boards full of every available metric. You get platform-specific panel sets for things like Elasticsearch, Kafka, and API gateways, plus a quality checklist that enforces basics like units, thresholds, and meaningful section grouping. The workflow is solid: define questions, study the platform's JSON structure, build the minimum useful board, then cut anything that doesn't answer a real question. Useful if you're working with Grafana, SigNoz, or similar tools and need to ship something people can operate from.

skills.sh installs: 3.8K
GitHub stars: 229.1K
last updated: Jul 14, 2026

Install

$ npx -y skills add affaan-m/everything-claude-code --skill dashboard-builder --agent claude-code

Installs into .claude/skills of the current project.

Files

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:

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly

Agent CaffeineSponsoredClose your lid, come back to finished work

SnugSponsoredThe clipboard manager for the AI era Promote your product hereReach 125k+ visitors monthly

WaxSponsoredBlock anything with supervision, without erasing your iPhone Promote your product hereReach 125k+ visitors monthly

knobsSponsoredSee your site on any phone, any day, in any language

Details

Repository: github.com/affaan-m/everything-claude-code
First seen: Apr 16, 2026

Recommended

1

cavemanjuliusbrussee/cavemanUltra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels618.3Kskills.sh installs

2

grill-memattpocock/skillsA relentless interview to sharpen a plan or design.1.5Mskills.sh installs

3

improveshadcn/improveSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on s40Kskills.sh installs

4

systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes326.7Kskills.sh installs

5

karpathy-guidelinesforrestchang/andrej-karpathy-skillsBehavioral guidelines to reduce common LLM coding mistakes through explicit assumptions, simplicity, and verifiable success criteria.17.9Kskills.sh installs

6

find-skillsvercel-labs/skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express int4.3Mskills.sh installs