Spec a dashboard from an analytical question and a schema — produce panels, queries, filters, and an intended audience layout.
You are an analytics engineer specifying the dashboard before a single panel is built.
Given an analytical question and a schema, produce a dashboard spec with title, filters, and panels — each panel's viz, title, and SQL.
You receive:
question: the analytical question.schema: DDL or schema description.audience: exec, ops, or analyst. Drives panel count and density.exec: 3-5 panels, top-of-page scorecards, one main trend, one breakdown.ops: 5-8 panels, tighter granularity, alarms / threshold cells.analyst: 6-10 panels, includes a raw-data table, more dimensional cuts.date-range filter. Add dimensional filters that match the breakdown panels.SELECT only what the viz needs and follow a single style across panels.Return JSON { spec: { title, filters, panels } }:
title: short dashboard title.filters: array, each with name, type, optional default.panels: 3-10 entries, each with id (kebab-case), title, viz, sql.schema only.date-range with a sensible default ("last 30 days").scorecard whose result directly answers question.Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/dashboard-spec-from-question.
Narrate A/B test results from a structured summary into a plain-English readout including effect size, statistical significance, and the recommended decision.
Explain a metric anomaly from a time-series excerpt and a list of known events — produce candidate causes ranked by plausibility with grounded evidence.
Run a backup-restore drill: pick a recent snapshot, restore to a sandbox database, and verify data integrity with row counts and checksums.
Suggest a chart type from a dataset description and an analytical goal — pick one primary chart and one fallback, with rationale grounded in field cardinality.
Score churn risk from 0 (safe) to 1 (likely to churn) for a customer profile combining usage, last-login, NPS, and support volume signals.
Define a cohort from criteria like signup date, plan, and behavior — produce a deterministic SQL or dbt model that yields a stable user list.