← ClaudeAtlas

bi-dashlisted

Builds a BI dashboard the way it gets trusted: a question sheet before any chart, an HTML mockup on synthetic data signed off by the asker, a field map that flags missing fields and columns with two candidates, every KPI reconciled to a reference within a stated tolerance, then the build in the repo's BI tool skill, UAT and a metric glossary. Tool-neutral. Use when the user says 'build a dashboard', 'new dashboard for', 'BI dashboard', 'KPI dashboard', 'reporting dashboard', 'mock up the dashboard', 'do we have the data for this dashboard', 'check the dashboard numbers' or 'is the dashboard ready to publish'. Not for a one-off number (answer it with a query), the tool's own chart syntax (the repo's BI tool skill) or modeling pipelines (data engineering).
vanducng/skills · ★ 8 · AI & Automation · score 78
Install: claude install-skill vanducng/skills
# bi-dash A dashboard fails quietly: it answers a question nobody asked, reads the wrong column, or disagrees with the number people already trust. Each stage has a gate and a file that proves it. Never pass a gate on a guess. ## When not to use it A one-off number ("how many orders last week?") is a query: answer with the number, its definition and the period. No question sheet, no mockup, no dashboard talk. ## The gates | # | Stage | Seat | Proof (file) | Gate | |---|---|---|---|---| | 1 | Information needs | lead with the asker | `question-sheet.md` ([template](references/question-sheet.md)) | Every row has an audience, a decision and a metric definition from the asker | | 2 | Mockup | `dev.design` | HTML mockup on synthetic data; each chart names its sheet row | No chart without a row | | 3 | Sign-off | human | The asker's yes, recorded in the slice record | Stakeholder messages are drafts for the operator to approve, never sent | | 4 | Data availability | `dev.build` | `field-map.md` ([template](references/field-map.md)) | No `missing` row and no unchosen `variant` | | 5 | Data validation | `dev.build` | `reconciliation.md` (below) | Every KPI inside its tolerance | | 6 | Data engineering | `dev.build` | Models built in dev, tested, then published; each metric defined once in the semantic layer | Model tests pass | | 7 | Build | `dev.build` | Dashboard as code, in the repo's BI tool skill; every metric carries its description | Follows [chart rules](references/chart