analyze-dashboard

# Analyze Dashboard ## When to Use - Meeting prep: Synthesize a dashboard into talking points before a review or exec meeting - Cross-chart pattern detection: Spot correlations across multiple charts that are hard to see manually - Dashboard investigation: A key number moved in a chart within this dashboard and you want to explain why - Connecting quant to qual: Understand if user feedback explains the trends you're seeing - Onboarding to unfamiliar dashboards: Get up to speed on what a dashboard tracks and its current state ## Instructions ### Step 0: Identify the Dashboard ID If the user gives a URL, use `Amplitude:getting_data_from_url` to get the dashboard ID ### Step 1: Retrieve the Dashboard Use `Amplitude:get_dashboard` with the dashboard ID to get the full structure and chart IDs. ### Step 2: Query All Charts Use `Amplitude:query_charts` to fetch data for up to 3 charts at a time. Prioritize: 1. Primary KPI charts (usually at the top) 2. Charts with recent changes 3. Trend-based visualizations ### Step 3: Analyze Patterns When analyzing charts, focus on the most decision-relevant signals for each type: - KPI tiles: Context (timeframe, user type) and % change if shown. - Line / Time series: Trends, slope changes, or notable events (not right-edge noise). - Funnel: Major drop-off steps or unexpected retention. Use conversion framing (solid bars), not dropoff framing, unless explicitly relevant. - Bar / Categorical: Concentrations, gaps, or surprising...