build-notebook

Provide an analysis_plan.md file containing chart specs with SQL queries and altair code. The Skill parses it, generates a <pipeline_name>_dashboard.py marimo app, validates it with uvx marimo check, and launches it with uv run marimo edit.

Variable conflicts occur when two cells export the same name. Follow the naming conventions in references/notebook-patterns.md: use df_chart1, df_chart2 for dataframes and keep the altair object cell-local with the _chart underscore prefix.

Chart cells must end with _chart on a bare line followed by return. Without the bare _chart expression line, marimo displays nothing even though the code runs without errors.

Yes, charts using ibis expressions are supported. Install ibis-framework[duckdb] and add import ibis inside the specific data cell that needs it rather than the global setup cell.

dlt.attach fails when the pipeline name is wrong or the pipeline has not been run yet. Verify the pipeline exists by running dlthub local pipeline info <name> before launching the notebook.

Do not use it for exploring data or planning charts, which belongs to the explore-data step, nor for building pipelines or deploying to dlthub. It only assembles dashboards from an existing analysis plan.