ClickHouse best practices: 31 rules for schema design, query tuning, ingestion and agent connectivity
Official ClickHouse review discipline: 31 impact-prioritized rules with checklists for schemas, queries, inserts, plus a safe connect → discover → query workflow for agents
- What
- Official ClickHouse review discipline: 31 impact-prioritized rules with checklists for schemas, queries, inserts, plus a safe connect → discover → query workflow for agents
- Cost
- Free
- Needs
- an agent-accessible ClickHouse instance (MCP server or CLI with credentials — you set up access yourself); ClickHouse Cloud has a free tier and self-hosting is free
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official @clickhouse review discipline for ClickHouse schemas, queries and configurations: 31 rules across 4 categories (schema, query, insert, agent), prioritized by impact, with per-rule files that agents MUST read before answering. Schema reviews check the immutable ORDER BY planning, column cardinality ordering, native types, smallest fitting bitwidth, LowCardinality for string columns, Nullable avoidance, and partition bounds (100–1,000 values); query reviews enforce JOIN algorithm selection, filter-before-join, skipping indices, and ORDER BY-prefix alignment; insert reviews mandate 10K–100K-row batches, async inserts for small high-frequency writes, and ReplacingMergeTree over ALTER UPDATE. Agents also get a connectivity and safety workflow: connect via MCP or CLI, run the 7-step schema discovery (databases → tables → columns → sort keys → skip indexes → sample → EXPLAIN), then execute with LIMITs and timeouts, narrowing filters on timeout or memory errors. Standard output format (Rules Checked → Violations → Compliant → Recommendations) with "Per rule-name..." citations. Honest caveats: an exhaustive rule set — full schema reviews burn a lot of tokens on large estates; the skill assumes the agent can reach a ClickHouse instance (MCP/CLI credentials), which you set up yourself. Apache-2.0. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: an agent-accessible ClickHouse instance (MCP server or CLI with credentials — you set up access yourself); ClickHouse Cloud has a free tier and self-hosting is free Install "ClickHouse best practices: 31 rules for schema design, query tuning, ingestion and agent connectivity" for me. It gives my agent the official ClickHouse review discipline: 31 impact-prioritized rules (schema primary-key planning, data types, partitioning, JOIN optimization, skipping indices, insert batching, async inserts, mutation avoidance), procedural review checklists for schema/query/insert reviews with a Rules Checked → Violations → Recommendations output format, plus the agent connectivity workflow (connect via MCP/CLI, 7-step schema discovery, plan with sort-key knowledge, execute with LIMITs and timeouts, recover by narrowing filters). Rule files are cited as "Per rule-name..." in answers. Apache-2.0. Repository: https://github.com/clickhouse/agent-skills/blob/main/skills/clickhouse-best-practices/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "clickhouse-best-practices". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. configure my ClickHouse MCP or CLI access with credentials, then ask the agent to follow the skill's connect → discover → query workflow). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.