affaan-m/ECC/docs/zh-CN/skills/dashboard-builder/SKILL.md
dashboard-builder
Use it for engineering tasks; the detail page covers purpose, installation, and practical steps.
- Source repository stars
- 234,327
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-27
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
当任务需要构建一个可供操作人员使用的仪表盘时使用此方案。
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/dashboard-builder"Inspect the Agent Skill "dashboard-builder" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/docs/zh-CN/skills/dashboard-builder/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
使用场景
"构建一个Kafka监控仪表盘" "为Elasticsearch创建一个Grafana仪表盘" "为这个服务制作一个SigNoz仪表盘" "将这个指标列表转化为真正的运维仪表盘"
"构建一个Kafka监控仪表盘""为Elasticsearch创建一个Grafana仪表盘""为这个服务制作一个SigNoz仪表盘" - 02
约束条件
不要从视觉布局开始;要从操作人员的问题出发 不要仅仅因为指标存在就包含所有可用指标 不要在没有结构的情况下混合健康、吞吐量和资源面板 不要发布没有标题、单位和合理阈值的面板
不要从视觉布局开始;要从操作人员的问题出发不要仅仅因为指标存在就包含所有可用指标不要在没有结构的情况下混合健康、吞吐量和资源面板 - 03
工作流程
健康/可用性 延迟/性能 吞吐量/容量 饱和度/资源 服务特定风险
健康/可用性延迟/性能吞吐量/容量
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 56/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 234,327 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | catalog record | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/dashboard-builder/SKILL.md
- Commit
- 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
仪表盘构建器
当任务需要构建一个可供操作人员使用的仪表盘时使用此方案。
目标不是"展示所有指标",而是回答以下问题:
- 系统健康吗?
- 瓶颈在哪里?
- 发生了什么变化?
- 应该采取什么行动?
使用场景
- "构建一个Kafka监控仪表盘"
- "为Elasticsearch创建一个Grafana仪表盘"
- "为这个服务制作一个SigNoz仪表盘"
- "将这个指标列表转化为真正的运维仪表盘"
约束条件
- 不要从视觉布局开始;要从操作人员的问题出发
- 不要仅仅因为指标存在就包含所有可用指标
- 不要在没有结构的情况下混合健康、吞吐量和资源面板
- 不要发布没有标题、单位和合理阈值的面板
工作流程
1. 定义操作问题
围绕以下方面组织:
- 健康/可用性
- 延迟/性能
- 吞吐量/容量
- 饱和度/资源
- 服务特定风险
2. 研究目标平台架构
首先检查现有仪表盘:
- JSON结构
- 查询语言
- 变量
- 阈值样式
- 分区布局
3. 构建最小可用面板
推荐结构:
- 概览
- 性能
- 资源
- 服务特定分区
4. 剔除装饰性面板
每个面板都应回答一个真实问题。如果不能,则移除。
示例面板集
Elasticsearch
- 集群健康
- 分片分配
- 搜索延迟
- 索引速率
- JVM堆/GC
Kafka
- 代理数量
- 副本不足的分区
- 消息流入/流出
- 消费者滞后
- 磁盘和网络压力
API网关/入口
- 请求速率
- p50/p95/p99延迟
- 错误率
- 上游健康
- 活跃连接数
质量检查清单
- [ ] 有效的仪表盘JSON
- [ ] 清晰的分区分组
- [ ] 包含标题和单位
- [ ] 阈值/状态颜色有意义
- [ ] 存在常用过滤器的变量
- [ ] 默认时间范围和刷新频率合理
- [ ] 没有对操作人员无价值的装饰性面板
相关技能
research-opsbackend-patternsterminal-ops
Alternatives
Compare before choosing
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.
affaan-m/ECC
dashboard-builder
Review dashboard-builder's use cases, installation, workflow, and original source instructions.
coreyhaines31/marketingskills
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
event4u-app/agent-config
design-intelligence
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.