dashboard

Inspect dlt dashboard modules, routes, and UI components in the marimo-based codebase.

5.7k|578|Updated Jan 26, 2022
One-click install
npx skills add https://github.com/dlt-hub/dlt --skill dashboard-dlt-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dashboard
Source: https://github.com/dlt-hub/dlt/tree/main/.claude/skills/dashboard
Command: npx skills add https://github.com/dlt-hub/dlt --skill dashboard-dlt-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps developers understand and contribute to the dlt dashboard codebase by clarifying file locations, module responsibilities, and UI components.

Core Features & Use Cases

  • Guides developers on file layout and responsibilities of dashboard components.
  • Supports onboarding, debugging, and extending the marimo-based dashboard used to inspect pipelines, schemas, data, and run traces.

Quick Start

Locate the main dashboard modules (dlt_dashboard.py, runner.py, config.py) and the utilities under utils/ to begin contributing.

Frequently Asked Questions about dashboard

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

FAQPage Schema
How do I navigate the dlt dashboard codebase to understand module responsibilities?

To navigate the dlt dashboard codebase, locate main modules like dlt_dashboard.py, runner.py, and config.py, then inspect the utils/ directory for queries, visualization, and trace utilities to understand their responsibilities.

What is the file layout for the marimo-based dashboard in dlt?

The marimo-based dashboard file layout is organized across dlt/_workspace/helpers/dashboard, containing core files like dlt_dashboard.py, runner.py, config.py, const.py, typing.py, strings.py, and a utils/ subdirectory for trace utilities.

How do I extend the marimo reactive UI to inspect pipeline run traces?

To extend the marimo reactive UI for inspecting pipeline run traces, modify the visualization and trace utilities under the dashboard's utils/ directory, leveraging the documented module responsibilities to guide your development.

Can I debug dlt dashboard components without prior knowledge of the const and typing modules?

Debugging dlt dashboard components effectively requires understanding const.py and typing.py, as this skill documents their responsibilities alongside runner.py and config.py to help you resolve issues across the marimo-based reactive UI.

What's the best way to start contributing to the dlt dashboard workspace?

The best way to start contributing to the dlt dashboard workspace is to review the documented file layout and module responsibilities, beginning with core modules like dlt_dashboard.py and the utilities under utils/.

Why does the dlt dashboard separate routes and UI components into different modules?

The dlt dashboard separates routes and UI components into different modules to clarify file locations and module responsibilities, making it easier for developers to onboard, debug, and extend the marimo-based reactive interface.