Documents a dataset column by column for a team about to receive it, using its name, source system, refresh frequency, and column list as inputs.
- Per column: type, business meaning, source, valid values or range, null handling
- Also covers: dependencies, known quality issues, and 3-5 example values
- Output: a clean markdown table plus a JSON schema ready for automated validation
Builds a fill-in-ready KPI report template for a business area, its KPI list, reporting frequency, and audience, meant to be generated once and reused every period.
Includes a header section, a red/yellow/green scorecard, per-KPI detail with trend and variance from target, a commentary section, action items for underperforming metrics, and a data-definitions appendix explaining how each number is calculated.
Plans a dashboard for a given audience and business area before it gets built in a BI tool, based on a metrics list, user goals, refresh frequency, and target tool.
Specifies the layout, chart type per metric with reasoning, filter and drill-down controls, a color-coding scheme, alert thresholds, and mobile considerations, all built around whether a viewer can pass the 5-second glance test.
Writes up a spike, drop, or unusual pattern the way an analyst should, starting from the anomaly description, time range, affected metrics, magnitude, and supporting data. States what happened in one sentence, quantifies the business impact beyond a percentage change, presents likely causes with evidence, rules out false positives like seasonality or pipeline bugs, and recommends both immediate action and prevention — tailored to a chosen audience and tone.
Paste raw dashboard numbers plus business context, the time period, stated
goals, and the prior period's figures to get a narrative read ready for a
metrics review meeting.
- Performance summary against goals and the previous period
- Positive trends and concerning trends called out separately
- Progress toward each stated goal and the likely drivers behind changes
- Recommended actions and a forecast for the next period
Paste in user or customer data, define how cohorts should be grouped,
pick a metric to track — retention, revenue, or engagement — and set the
time period, for a lighter-weight cohort read than a full retention-table
build.
Covers cohort performance comparison, retention curves, revenue trends by
cohort, behavioral patterns, drop-off points, and the factors separating
strong cohorts from struggling ones, plus improvement opportunities.
Name the reporting cadence, the business area, and up to four report
sections, and this prompt plans an entire recurring report's worth of
visuals at once. For each section it recommends 2-3 charts with the exact
source columns and encoding, writes a chart title that states the finding
rather than just describing the data, and adds a fill-in-the-blank
caption template, then generates a rerunnable Python script that builds
every chart from one DataFrame and exports consistently styled PNGs each
period.
Specify the entity type being cohorted, how cohorts are defined (signup
month, hire date, etc.), the key metric to track, the time granularity,
and the relevant dataset columns, and this prompt builds a full cohort by
time period retention or engagement table from raw data. It flags which
cohorts meaningfully beat or lag the average, checks whether newer
cohorts trend better or worse over time, runs a time-to-event
calculation like time to 50% churn, and delivers the Python or SQL code
that generates the whole analysis plus a heatmap.
Give the specific decision or question this summary needs to inform,
plus the interview transcript, and get back a 200-word-or-shorter
condensation.
Prioritizes actionable findings tied directly to that decision over vague
generalities, and favors concrete specifics — useful when a stakeholder
needs the gist of an interview in under a minute of reading.