query-debugging

## Overview Honeydew records every query executed through the semantic layer — MCP tools, BI tools over the SQL/XMLA interfaces (Tableau, Power BI, …), scheduled jobs, and deep analysis. Use `list_query_history` (from the `honeydew` MCP server) to see **what ran, who ran it, from which client, and how**, and to drill into any run's semantic definition or compiled SQL. Debugging failures is one use, not the only one. Reach for this skill on questions like: - "What ran against this domain today, and from which clients?" - "Which BI tool queried this model, and what did it send?" - "Show me the queries my last deep analysis generated." - "Why did my query fail? Show me its SQL." For running a *new* query, use the **query** skill. This skill inspects queries that already ran. The tool's description and parameter schema cover the exact arguments and response fields; this skill covers what they can't — **when to reach for it, how to read the results, and the workflows.** --- ## Prerequisites Query history is scoped to the session's workspace — check with `get_session_workspace_and_branch`, and set one via the **workspace-branch** skill if needed. Non-admin callers see only their own queries; admins see all and can filter by `user_in`. --- ## Reading the Results - **client** — where the query came from (`Tableau`, `Power BI`, `MCP`, …); how you tell a dashboard's query from an MCP or deep-analysis run. - **original SQL vs. compiled SQL** — SQL-interface clients (Tableau, ...