Back to browse

affaan-m/ECC

dashboard-builder

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.

77Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "skills/dashboard-builder"
Automated source guide

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Turn dashboard-builder's source instructions into a guide you can follow

According to the pinned SKILL.md from affaan-m/ECC: Use this when the task is to build a dashboard people can operate from.

npx skills add https://github.com/affaan-m/ECC --skill "skills/dashboard-builder"
Check the pinned source

Best fit

  • "Build a Kafka monitoring dashboard"
  • "Create a Grafana dashboard for Elasticsearch"
  • "Make a SigNoz dashboard for this service"

Bring this context

  • A concrete task that matches the documented purpose of dashboard-builder.
  • The files, examples, or context the task depends on.
  • Your constraints, target environment, and definition of done.

Expected outputs

  • cluster health
  • shard allocation
  • search latency

Key source sections

Read dashboard-builder through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

Workflow

Inspect existing dashboards first:

SKILL.md · Workflow
health / availabilitylatency / performancethroughput / volume
02

When to Use

"Build a Kafka monitoring dashboard"

SKILL.md · When to Use
"Build a Kafka monitoring dashboard""Create a Grafana dashboard for Elasticsearch""Make a SigNoz dashboard for this service"
03

Guardrails

do not start from visual layout; start from operator questions

SKILL.md · Guardrails
do not start from visual layout; start from operator questionsdo not include every available metric just because it existsdo not mix health, throughput, and resource panels without structure

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Task-start prompt

Confirm source fit, inputs, and outputs before acting.

Use dashboard-builder to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.

Source-guided execution

Make the Agent explicitly follow the key extracted sections.

Apply the pinned dashboard-builder source to [task]. Pay particular attention to these source sections: “Workflow”, “When to Use”, “Guardrails”, “1. Define the operating questions”, “2. Study the target platform schema”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].

Result-review prompt

Check omissions, permissions, and source drift before delivery.

Review the current dashboard-builder result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.

Output checklist

Verify each item before delivery

The task matches the purpose documented in the SKILL.md.

The source section “Workflow” has been checked.

The source section “When to Use” has been checked.

The source section “Guardrails” has been checked.

The source section “1. Define the operating questions” has been checked.

Inputs, constraints, and acceptance criteria are explicit.

Unverified facts, compatibility, and outcome claims are clearly marked.

Any file, command, network, or data action has been reviewed.

Choose a different workflow

When another Skill is the better fit

dashboard-builder

为 Grafana、SigNoz 等平台构建能够回答实际运维人员问题的监控仪表板。适用于将指标转化为可用的仪表板，而非华而不实的展示板。

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

dashboard-builder

Grafana、SigNoz、および同様のプラットフォーム用の実際のオペレータ質問に答える監視ダッシュボードを構築します。メトリクスを虚栄ボードではなく機能するダッシュボードに変える場合に使用します。

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

design-review

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does dashboard-builder do?

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

How do I start using dashboard-builder?

The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "skills/dashboard-builder". Inspect the command and pinned source before running it.

Which Agent platforms does it declare?

No dedicated Agent platform is declared in the pinned source record.

Repository stars
234,327
Repository forks
35,711
Quality
77/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

77/100
Documentation22/30
Specificity18/25
Maintenance20/20
Trust signals17/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

dashboard-builder by affaan-m

为 Grafana、SigNoz 等平台构建能够回答实际运维人员问题的监控仪表板。适用于将指标转化为可用的仪表板，而非华而不实的展示板。

dashboard-builder by affaan-m

Grafana、SigNoz、および同様のプラットフォーム用の実際のオペレータ質問に答える監視ダッシュボードを構築します。メトリクスを虚栄ボードではなく機能するダッシュボードに変える場合に使用します。

design-review by event4u-app

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

dask by k-dense-ai

Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

medchem by k-dense-ai

Medicinal chemistry filters for compound triage. Apply drug-likeness rules (Lipinski, Veber, CNS), structural alert catalogs (PAINS, NIBR, ChEMBL), complexity metrics, and the medchem query language for library filtering.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 2 min

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
Source repo
affaan-m/ECC
Skill path
skills/dashboard-builder/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected