analyzelisted

# /analyze - Answer Data Questions > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS-data.md). Answer a data question, from a quick lookup to a full analysis to a formal report. ## Usage ``` /analyze <natural language question> ``` ## Workflow ### 1. Understand the Question Parse the user's question and determine: - **Complexity level**: - **Quick answer**: Single metric, simple filter, factual lookup (e.g., "How many users signed up last week?") - **Full analysis**: Multi-dimensional exploration, trend analysis, comparison (e.g., "What's driving the drop in conversion rate?") - **Formal report**: Comprehensive investigation with methodology, caveats, and recommendations (e.g., "Prepare a quarterly business review of our subscription metrics") - **Data requirements**: Which tables, metrics, dimensions, and time ranges are needed - **Output format**: Number, table, chart, narrative, or combination ### 2. Gather Data **If a data warehouse MCP server is connected:** 1. Explore the schema to find relevant tables and columns 2. Write SQL query(ies) to extract the needed data 3. Execute the query and retrieve results 4. If the query fails, debug and retry (check column names, table references, syntax for the specific dialect) 5. If results look unexpected, run sanity checks before proceeding **If no data warehouse is connected:** 1. Ask the user to provide data in one of these ways: - Paste query