Download for MacApple silicon, macOS 14+
Skill

query-debugging

@honeydew-ai Updated 2026-08-30

Use when the user wants to review or inspect past query executions in Honeydew — what ran, from which client (BI tools, SQL interface, MCP, deep analysis), the semantic definition or compiled SQL behind a run, who ran it and when — and to debug failures. Uses the list_query_history MCP tool. For running new queries or analysis use the query skill.

analyticsclaude-codecodexcontext-layercursorhoneydewsemantic-layer

Install

With your agent

Install OMGSkills skill "honeydew-ai/honeydew-ai-coding-agents-plugins:skills/query-debugging" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/honeydew-ai/honeydew-ai-coding-agents-plugins /tmp/honeydew-ai-coding-agents-plugins && ln -s /tmp/honeydew-ai-coding-agents-plugins/skills/query-debugging ~/.claude/skills/query-debugging

From README

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 listqueryhistory (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.