Stats
Actions
Tags
Explain AQL queries and their results, and provide data insights. Use this whenever the user asks what a query does, wants to understand results, or needs to dig deeper into why a metric changed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/holistics-development:analyze-dataThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
* Set up Holistics MCP
Always use explain_result tool to syntactically/descriptively explain AQLs and their results. It can understand AQL accurately and provide accurate answers.
Run additional queries to analyze and provide diagnostic and predictive answers. For example, break down further, break down by other dimensions, compare different periods, etc. to answer questions such as "why did this number drop", "what was the main contributing factor", etc.
explain_result to understand the query, then proceed to further diagnostic/predictive analysis.execute_aql, execute_viz) to verify.npx claudepluginhub holistics/skills --plugin holistics-developmentAnswers data questions via SQL on connected warehouses: quick metrics, trend investigations, segment comparisons, formal reports. Uses manual input if no connection.
Runs queries against Omni Analytics' semantic layer via the Omni CLI, interprets results, and chains queries for multi-step analysis. Useful for extracting data from Omni dashboards or workbooks programmatically.
Generates optimized SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, Snowflake; reads schemas from files or docs. For data exploration, reports, and business analysis.