// Diagnose ClickHouse runtime query failures when the user wants database-level cause and fix guidance from an error or numeric error code, not source-code root cause analysis.
Optimize slow queries, analyze SQL performance, and collect evidence for expensive workloads.
Diagnose ClickHouse cluster health and provide concrete remediation.
Investigate application or repository source code with search_file and read_file to explain behavior, trace root causes of runtime or query errors, and answer with precise file citations.
Query ClickHouse system tables to inspect query logs, monitor cluster health, check replication status, and analyze slow queries. Use when the user mentions "system tables", "query_log", "ClickHouse monitoring", "cluster status", "slow queries", or asks to diagnose ClickHouse operational issues.
Expert system for generating, validating, and optimizing ClickHouse SQL. Use this when the user needs data, queries, or analysis.
Rules for charts and visualization. Use when the user asks for charts, graphs, plots, or visual representations (line, bar, pie, timeseries).
| name | diagnose-clickhouse-errors |
| description | Diagnose ClickHouse runtime query failures when the user wants database-level cause and fix guidance from an error or numeric error code, not source-code root cause analysis. |
| metadata | {"author":"DataStoria"} |
Do not use this skill when the user's primary goal is:
In those cases, prefer source-code-inspection. Do not start this skill's error-code intake flow unless the user is asking for database-level diagnosis.
source-code-inspection.Code: 60).ask_user_question with exactly one question. Do NOT reply with natural-language text before the tool call.
header: Please provide a ClickHouse error code for diagnosisoptions: [ { "id": "error_code", "label": "error code", "input": "text" } ]value as the numeric error code and continue.references/<code>.md with skill_resource (e.g. references/60.md) and follow its workflow.skill_resource returns nothing, use your ClickHouse knowledge to provide a best-effort response.Heading rules:
## Cause, ## Fix, and optional ## Example.Response language (BCP-47): …), localize the heading text to that language while keeping the same 3-section structure.Keep answers brief and action-first. Do not repeat the raw error verbatim. Do not add extra headings.