Diagnose Clickhouse Errors

When a ClickHouse query blows up in production and you need to understand why at the database level, this skill walks you through a structured diagnosis. It extracts the numeric error code, loads reference material for that specific code, and gives you a three part answer: what caused it, how to fix it, and an example of the corrected query. The workflow explicitly steers you away if you're actually trying to trace application code that generated the query, pushing you toward source code inspection instead. It's narrow by design. DataStoria built this to short circuit the cycle of pasting error codes into documentation searches when you just want the database level fix, not a debugging session.

GitHub stars: 320
last updated: May 14, 2026

View on GitHub

Install

$ npx -y skills add frankchen021/datastoria --skill diagnose-clickhouse-errors --agent claude-code

Installs into .claude/skills of the current project.

Files

When Not To Use

Do not use this skill when the user's primary goal is:

investigating application or repository source code
tracing where failing SQL was constructed in code
finding code paths that produced the ClickHouse error

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.