Clickhouse Logs Queries
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
Diagnose ClickHouse cluster health and provide concrete remediation.
Install Diagnose Clickhouse Clusters
$ npx skills add FrankChen021/datastoria --skill diagnose-clickhouse-clusters -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FrankChen021/datastoria diagnose-clickhouse-clusters --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/skills/diagnose-clickhouse-clusters .claude/skills/diagnose-clickhouse-clusters && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "diagnose-clickhouse-clusters" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/diagnose-clickhouse-clusters into .claude/skills/diagnose-clickhouse-clusters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-clickhouse-clusters", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FrankChen021/datastoria/tree/master/resources/skills/diagnose-clickhouse-clustersType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FrankChen021/datastoria --skill diagnose-clickhouse-clusters -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FrankChen021/datastoria diagnose-clickhouse-clusters --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/skills/diagnose-clickhouse-clusters .agents/skills/diagnose-clickhouse-clusters && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "diagnose-clickhouse-clusters" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/diagnose-clickhouse-clusters into .agents/skills/diagnose-clickhouse-clusters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-clickhouse-clusters", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FrankChen021/datastoria --skill diagnose-clickhouse-clusters -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FrankChen021/datastoria diagnose-clickhouse-clusters --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/skills/diagnose-clickhouse-clusters .cursor/skills/diagnose-clickhouse-clusters && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "diagnose-clickhouse-clusters" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/diagnose-clickhouse-clusters into .cursor/skills/diagnose-clickhouse-clusters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-clickhouse-clusters", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FrankChen021/datastoria.git --path resources/skills/diagnose-clickhouse-clusters--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FrankChen021/datastoria --skill diagnose-clickhouse-clusters -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FrankChen021/datastoria diagnose-clickhouse-clusters --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/skills/diagnose-clickhouse-clusters .gemini/skills/diagnose-clickhouse-clusters && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "diagnose-clickhouse-clusters" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/diagnose-clickhouse-clusters into .gemini/skills/diagnose-clickhouse-clusters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-clickhouse-clusters", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FrankChen021/datastoria diagnose-clickhouse-clustersInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FrankChen021/datastoria --skill diagnose-clickhouse-clusters -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/skills/diagnose-clickhouse-clusters .github/skills/diagnose-clickhouse-clusters && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "diagnose-clickhouse-clusters" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/diagnose-clickhouse-clusters into .github/skills/diagnose-clickhouse-clusters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-clickhouse-clusters", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FrankChen021/datastoria --skill diagnose-clickhouse-clusters -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FrankChen021/datastoria diagnose-clickhouse-clusters --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/skills/diagnose-clickhouse-clusters .opencode/skills/diagnose-clickhouse-clusters && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "diagnose-clickhouse-clusters" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/diagnose-clickhouse-clusters into .opencode/skills/diagnose-clickhouse-clusters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-clickhouse-clusters", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
diagnose-clickhouse-clusters- GitHub stars
- 327
- Token cost
- ~1.6k tokens
- SKILL.md length
- 831 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Diagnose ClickHouse cluster health and provide concrete remediation.
- Works in 3 steps: Determine whether the user asks for… → For RCA questions, pick one supported… → Explain from tool output only: top…
- Tasks that involve Data warehousing
- SKILL.md covers A) Status-only question and B) RCA question ("why",…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Diagnose Clickhouse Clusters is an agent skill from FrankChen021/datastoria. Diagnose ClickHouse cluster health and provide concrete remediation.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases, covering Data warehousing. It works with ClickHouse and SQL. The repository describes itself as: AI-native ClickHouse console for your cluster diagnostics and query generation, optimization and data visualization.
When your agent uses it
- Tasks that involve Data warehousing
Example prompts
- “/diagnose-clickhouse-clusters”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Determine whether the user asks for status only, or root cause ("why", "root cause", "reason", "caused by", "explain").
- For RCA questions, pick one supported canonical symptom key based on user wording, explicit target details, and, when needed, status…
- Explain from tool output only: top candidates, support score, evidence lists, gaps, and prioritized actions.
What it can do on your machine
Read from SKILL.md and the folder at commit d0859a2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Diagnose Clickhouse Clusters loads about 1.6k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 831 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 831 words (~1,619 tokens).
“Do not hardcode parts thresholds in responses. Use the thresholds and severities returned by collect_cluster_status.”
- name
- diagnose-clickhouse-clusters
Files
Just SKILL.md in resources/skills/diagnose-clickhouse-clusters of FrankChen021/datastoria.
Open the folder on GitHubat commit d0859a2
Compare with similar skills
Diagnose Clickhouse Clusters next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Diagnose Clickhouse Clusters this skillFrankChen021/datastoria | 327 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Clickhouse Logs Queriessupabase/supabase | 111k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Chdb SQLvemetric/vemetric | 395 | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| BisectClickHouse/ClickHouse | 50k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Webapp Buildersidequery/sidemantic | 129 | — | ~5.5k | Automated safety check: Pass | AGPL-3.0 | |
| Cpu ProfileClickHouse/ClickHouse | 50k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
Chdb SQL
vemetric/vemetric
A skill your agent uses when the user wants to run SQL — especially analytical SQL — on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse…
Bisect
ClickHouse/ClickHouse
Bisect a ClickHouse regression using pre-built master binaries from CI.
Webapp Builder
sidequery/sidemantic
Build interactive analytics webapps, demos, dashboards, or embedded app surfaces from Sidemantic semantic models using copyable component primitives and deterministic query inspection.
Cpu Profile
ClickHouse/ClickHouse
Profile a ClickHouse query using the sampling query profiler and system.tracelog.
Modeler
sidequery/sidemantic
Build, validate, and manage semantic models using Sidemantic.
More from FrankChen021/datastoria
Clickhouse System Queries
FrankChen021/datastoria
Query ClickHouse system tables to inspect query logs, monitor cluster health, check replication status, and analyze slow queries.
Visualization
FrankChen021/datastoria
Rules for charts and visualization. An agent skill from FrankChen021/datastoria.
Diagnose Clickhouse Errors
FrankChen021/datastoria
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.
SQL Expert
FrankChen021/datastoria
Expert system for generating, validating, and optimizing ClickHouse SQL.
Optimize Clickhouse SQL
FrankChen021/datastoria
Optimize slow queries, analyze SQL performance, and collect evidence for expensive workloads.
Source Code Inspection
FrankChen021/datastoria
Investigate application or repository source code with searchfile and readfile to explain behavior, trace root causes of runtime or query errors, and answer with precise file citations.
Related
Works with
Categories
Questions about Diagnose Clickhouse Clusters
What does Diagnose Clickhouse Clusters do?
Diagnose ClickHouse cluster health and provide concrete remediation. Diagnose Clickhouse Clusters is an agent skill from FrankChen021/datastoria. Diagnose ClickHouse cluster health and provide concrete remediation.
When should I use Diagnose Clickhouse Clusters?
Diagnose Clickhouse Clusters fits situations like: tasks that involve Data warehousing.
How do I install Diagnose Clickhouse Clusters in Claude Code?
Run `npx skills add FrankChen021/datastoria --skill diagnose-clickhouse-clusters -a claude-code`. Or copy the skill folder (resources/skills/diagnose-clickhouse-clusters in FrankChen021/datastoria) into .claude/skills/diagnose-clickhouse-clusters in your project. Claude Code loads it when a task matches its description.
How do I install Diagnose Clickhouse Clusters in Codex?
Run `npx skills add FrankChen021/datastoria --skill diagnose-clickhouse-clusters -a codex`. Or copy the skill folder (resources/skills/diagnose-clickhouse-clusters in FrankChen021/datastoria) into .agents/skills/diagnose-clickhouse-clusters in your project. Codex loads it when a task matches its description.
Can I use Diagnose Clickhouse Clusters in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FrankChen021/datastoria --skill diagnose-clickhouse-clusters -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/diagnose-clickhouse-clusters, .gemini/skills/diagnose-clickhouse-clusters, .github/skills/diagnose-clickhouse-clusters and .opencode/skills/diagnose-clickhouse-clusters in your project.
What does Diagnose Clickhouse Clusters need to run?
SKILL.md names no scripts, command-line tools or credentials: Diagnose Clickhouse Clusters is instructions for the agent only.
Does Diagnose Clickhouse Clusters access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Diagnose Clickhouse Clusters safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Diagnose Clickhouse Clusters use?
Diagnose Clickhouse Clusters has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Diagnose Clickhouse Clusters use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Diagnose Clickhouse Clusters?
Skills that share tags, products or a category with Diagnose Clickhouse Clusters: Clickhouse Logs Queries (supabase/supabase, 111k stars), Chdb SQL (vemetric/vemetric, 395 stars), Bisect (ClickHouse/ClickHouse, 50k stars) and Webapp Builder (sidequery/sidemantic, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Diagnose Clickhouse Clusters?
FrankChen021 (a GitHub user) maintains it in FrankChen021/datastoria, which has 327 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on July 21, 2026.
Source: FrankChen021/datastoria on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.