bi-dashboard-architect

Architect BI dashboards with data models, KPI hierarchies, and governance patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mlamla123/openclaw-starter-kit --skill bi-dashboard-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bi-dashboard-architect
Source: https://github.com/mlamla123/openclaw-starter-kit/tree/main/skills/bi-dashboard-architect
Command: npx skills add https://github.com/mlamla123/openclaw-starter-kit --skill bi-dashboard-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Architect BI systems, dashboards, and analytics workflows by codifying the architecture, data modeling practices, and visualization governance needed to deliver clear, scalable insights across teams.

Core Features & Use Cases

  • Data modeling guidance (star schema, grain, semantic layer) to ensure consistent facts and dimensions.
  • Chart selection and KPI design patterns, with layout guidance for executive, operational, and analytical dashboards.
  • Filter state management, accessibility guidelines, and pre-defined aggregation APIs to enforce governance.
  • Library-agnostic considerations for chart libraries (Chart.js, ECharts, Recharts, Tremor, D3, Plotly, AG Grid, Evidence) and data pipeline planning.
  • Use cases include building dashboards, adding analytics to products, reviewing KPI views, selecting visualization stacks, and planning data pipelines for scalable analytics.

Quick Start

Describe your BI scenario and I will generate a complete dashboard architecture plan.

Frequently Asked Questions about bi-dashboard-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a scalable BI dashboard architecture for executive and operational use cases?

To design scalable BI dashboards, architect data models with star schemas and semantic layers, define KPI hierarchies, and establish governance patterns for consistent grains and pre-aggregation strategies.

What is the best way to select charts and KPIs for analytics dashboards?

Select charts and design KPIs by applying library-agnostic patterns tailored to executive, operational, or analytical contexts, ensuring filter state management and accessibility guidelines are enforced.

How do I model data pipelines to ensure consistent facts and dimensions for analytics?

Model data pipelines by defining consistent grains and semantic layers using star schema practices, ensuring facts and dimensions remain robust and reliable for API-driven dashboards across all use cases.

Can I use this approach with chart libraries like Chart.js, ECharts, and Tremor?

Yes, this approach provides library-agnostic considerations for chart libraries like Chart.js, ECharts, Recharts, Tremor, D3, Plotly, AG Grid, and Evidence to guide visualization stack selection.

Do I need a semantic layer to enforce pre-aggregation strategies in BI systems?

Yes, a semantic layer is needed to enforce pre-aggregation strategies and consistent metric definitions, ensuring API-driven dashboards remain scalable and robust across various analytical use cases.