| name | analytics-report |
| description | Generate executive and operational analytics reports — structured analysis |
Analytics Report
Generate executive and operational analytics reports — structured analysis
with insights, visualizations, and actionable recommendations — transforming
raw data into business decisions.
What problem this solves
Data without analysis is noise. Stakeholders need conclusions, not raw data.
This skill produces polished analytics reports that answer three questions:
what happened, why did it happen, and what should we do about it?
When to use
When stakeholders need data-driven insights. For monthly/quarterly business
reviews. When analyzing a specific business problem. When The Data Professor
asks "what does the data say?"
Input
Data to analyze, business questions, audience, report format.
Output
A structured analytics report with executive summary, analysis, visualizations,
insights, and recommendations.
Steps
- Define the business question: what decision does this report enable?
- Gather and validate data — note data sources and quality
- Analyze: trends, patterns, anomalies, comparisons, correlations
- Visualize key findings with appropriate charts (use data-visualization skill)
- Structure the report: Executive Summary → Analysis → Visualizations → Insights → Recommendations
- Write insights, not just observations: "Revenue grew 15% because of X" not "Revenue went up"
- Make recommendations specific and actionable: "Increase X budget by $Y to capture Z opportunity"
Rules
- Executive Summary on page 1 — busy stakeholders may read nothing else
- Every chart must have a written insight — don't make readers interpret
- Recommendations must be specific: what, how much, by when, expected impact
- Data sources cited — stakeholders must trust the numbers
- Consistent format issue to issue — stakeholders should know where to look
- Note data limitations and assumptions — be honest about uncertainty
- Coordinate with Pablo (overall BI) and data-visualization (charts)
Done Criteria