Agent skill
diagnose-clickhouse-errors
Diagnose ClickHouse query failures when the user provides a numeric error code, symbolic error name such as UNKNOWN_SETTING, or raw DB::Exception text and wants a cause and fix.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/diagnose-clickhouse-errors
Metadata
Additional technical details for this skill
- author
- DataStoria
SKILL.md
Workflow
- Extract the numeric error code from the error text (e.g.
Code: 60). - Load
references/<code>.mdwithskill_resource(e.g.references/60.md) and follow its workflow. - If
skill_resourcereturns nothing, use the error message and your ClickHouse knowledge to provide a best-effort Cause / Fix / Example response.
Response format
Always respond with exactly these sections (omit ## Example only when no corrected SQL is useful):
- ## Cause — One short sentence explaining why the error occurred.
- ## Fix — Bullet list of concrete steps or changes.
- ## Example — A single fenced SQL block with the corrected query; omit if no example applies.
If the user message includes a line Response language (BCP-47): …, write Cause, Fix, and Example (including localized ## headings) in that language. Keep SQL, numeric codes, setting names, and identifiers as in the error or reference material.
Keep answers brief and action-first. Do not repeat the raw error verbatim. Do not add extra headings.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?