Dashboard Builder
Build monitoring dashboards that answer real operator questions for Grafana, SigNoz, and similar platforms, not vanity boards.
- What
- Build monitoring dashboards that answer real operator questions for Grafana, SigNoz, and similar platforms, not vanity boards.
- Cost
- Free
- Needs
- Use "Dashboard Builder" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a workflow skill for building dashboards people can actually operate from, on Grafana, SigNoz, and similar platforms. Its founding rule: never start from visual layout, start from operator questions (is it healthy, where is the bottleneck, what changed, what action should someone take). You define the questions first, study the platform's schema and query language, then build the minimum useful board: overview, then health, latency, throughput, and saturation sections, with titled panels, units, and sane thresholds. Guardrails included: no metric dumps, no mixing concerns without structure, no untitled panels. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; you need access to a dashboard platform and real metrics; examples assume Grafana-style JSON dashboards. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Dashboard Builder" with your Muse. Prerequisites: access to a dashboard platform (Grafana, SigNoz, or similar) and real metrics to visualize. Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/dashboard-builder/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Help me build a dashboard for [service]. Start from the operator questions, not the layout." 3. Give it your metrics list and ask: "Design the minimum useful board: overview, health, latency, throughput, saturation, with thresholds." Tip: every panel needs a title, a unit, and a sane threshold, or it does not ship. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets or internal URLs into a chat.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.