Use when answering a question that needs data from a ktx-connected database - investigating, analyzing, "how many", "show me", "what's the breakdown of", finding records by value, exploring tables, comparing periods, explaining metrics, or any data-analysis request. Triggers even when the user does not say "analytics"; if the answer requires querying a configured ktx connection, this skill applies.
NewMaintained
Automatic
◆Data Analyst pack
Last verified 8/13/2026
What it changes
Passed 2 of 8 test cases with the skill, and 4 of 8 without it.
Without skill50%
With skill27%
Checks it passed that the model alone missed
Formats list-valued output as a delimited string with an explicit ORDER BY clause in aggregation.
1 fixed5 passed either way10 still failing6 broke
Pass-rate lift
-23 pp
Tokens
+629%
Agent turns
0%
Response time
-20%
Model gemini-3.6-flashMeasured 8/13/2026v16 of 22 cases passed with skill · 8 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
We need a list of product tags per category in a single output column. Should this be returned as a SQL array or a delimited string?
What was checked, without and with the skill
Checked
Without skill
With skill
Formats list-valued output as a delimited string with an explicit ORDER BY clause in aggregation.
Missed
Passed
case-09 · gemini-3.6-flash · 8/13/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md260 linessingle file
ktx Analytics Workflow
You have access to ktx MCP tools for data discovery, semantic-layer analysis, raw read-only SQL, wiki context, and memory ingest. Follow this workflow.
<sql_craft>
Heuristics for writing correct (not merely runnable) SQL. Each is a default plus the reason it holds on any database; apply judgment to the question and the data.
Convert Metabase questions, models, and metrics into ktx Semantic Layer source definitions. Covers result-metadata to KSL column type mapping, FK/PK detection, near-duplicate deduplication, pre-aggregation decomposition, join-graph connectivity, and how to react to priorProvenance from earlier ingest syncs. Load when the WorkUnit contains `cards/<id>.json` files under a Metabase bundle.