Related Skills

Use $create-data-context only when the dashboard work explicitly asks to save data context or create, update, inspect, or repair a semantic layer.

Use $analyze-data-quality when dashboard metrics disagree or source freshness, grain, joins, or definitions could affect trust.

Dashboard Building

Use this skill when the user needs a dashboard rather than a report, notebook-only analysis, spreadsheet, or transient chat summary. A good dashboard is summary-first, chart-led, scannable, and organized around what the audience needs to monitor, understand, or act on.

Clarify with the user when a missing input would materially change the dashboard brief, analysis, or recommendation. Otherwise make a reasonable assumption, state it, and proceed.

This skill owns the dashboard brief, delivery-mode selection, metric definitions, source expectations, layout logic, dashboard QA, and handoff. Delivery-specific mechanics belong in the selected dashboard specification.

Skill Configuration

Runtime Delivery Routing

If mode = work_mode is positively identified, do not visibly render the Data Analytics MCP artifact app or a generated web app, regardless of surface. Use a connected BI destination only when the user selected one. Otherwise automatically use sites-app when the full Sites create, checkpoint, and deployment lifecycle is callable: load the MCP artifact dashboard specification, build and validate the canonical manifest/snapshot, skip render_artifact, and invoke $publish-artifact-to-sites. Do not ask for another delivery choice or publish confirmation. Build portable HTML automatically when Sites is unavailable, publishing fails, or the user explicitly declines Sites. Use Streamlit only when the user explicitly asks for it. MCP servers and other callable tools remain valid data sources.