Diagnose Clickhouse Errors

Community

FrankChen021

diagnose-clickhouse-errors

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.

Overview

Publisher	FrankChen021
Repository	`datastoria`
Skill name	`diagnose-clickhouse-errors`
Stars	327
Forks	18
Bundled files	5
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
5 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by FrankChen021 on GitHub. Read the source before you install it.

Installation

Install the Diagnose Clickhouse Errors AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/FrankChen021/datastoria/tree/master/resources/skills/diagnose-clickhouse-errors
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/FrankChen021/datastoria/tree/master/resources/skills/diagnose-clickhouse-errors

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/FrankChen021/datastoria.git /tmp/datastoria
mkdir -p .claude/skills
cp -r /tmp/datastoria/resources/skills/diagnose-clickhouse-errors .claude/skills/diagnose-clickhouse-errors

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Diagnose Clickhouse Errors in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Diagnose Clickhouse Errors on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Diagnose Clickhouse Errors is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Workflow

Determine whether the user is asking for database-level diagnosis or source-code investigation. If the primary goal is source-code investigation or file-cited code analysis, stop and prefer source-code-inspection.
Extract the numeric ClickHouse error code from the conversation or error text (e.g. Code: 60).
If no numeric error code is detected and the user is asking for database-level diagnosis, call 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 diagnosis
- options: [ { "id": "error_code", "label": "error code", "input": "text" } ]
- Treat the returned value as the numeric error code and continue.
Load references/<code>.md with skill_resource (e.g. references/60.md) and follow its workflow.
If the orchestrator provides database context facts, use them when they materially change the cause or fix.
If skill_resource returns nothing, use your ClickHouse knowledge to provide a best-effort response.

Response format

Section 1 (Cause) — One short sentence explaining why the error occurred.
Section 2 (Fix) — Bullet list of concrete steps.
Section 3 (Example) — A single fenced SQL block with the corrected query; omit if not applicable.

Heading rules:

Default (English): use headings ## Cause, ## Fix, and optional ## Example.
If a response language is specified by system policy or user message (Response language (BCP-47): …), localize the heading text to that language while keeping the same 3-section structure.
Keep SQL, codes, and identifiers as-is.

Keep answers brief and action-first. Do not repeat the raw error verbatim. Do not add extra headings.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Diagnose Clickhouse Errors AI skill do?

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.

Why use Diagnose Clickhouse Errors on TypingMind?

Because you install it once and use it with any model. Diagnose Clickhouse Errors is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Diagnose Clickhouse Errors in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/FrankChen021/datastoria/tree/master/resources/skills/diagnose-clickhouse-errors. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Diagnose Clickhouse Errors?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Diagnose Clickhouse Errors?

As many as you like. As long as a model supports skills, you can use Diagnose Clickhouse Errors with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Diagnose Clickhouse Errors AI skill free?

It is published on GitHub by FrankChen021. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Pytorch Lightning

NousResearch

OrganizationPopular

Clean training loops with built-in distributed support.

Troubleshoot

Investigate unexpected behavior in the current Copilot agent session by analyzing its event log. Use when the user asks why something happened, why a request was slow, why a tool was or was not used,…

Pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart,…

Ui Styling

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

When Not To Use

Workflow

Response format

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now