Agent skill · data analytics · jeremylongshore
clickhouse-prod-checklist
Production readiness checklist for ClickHouse — server tuning, backup, monitoring, and deployment verification. Use when launching a ClickHouse deployment, doing a go-live review, or auditing production readiness before flipping traffic. Trigger with "clickhouse production", "clickhouse go-live", "clickhouse launch checklist", "production clickhouse", "clickhouse prod ready".
Why this skill is useful
Provides domain-specific knowledge and operational patterns for ClickHouse deployments that the AI wouldn't reliably generate on its own.
What it needs
Requires clickhouse-client, curl installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
ClickHouse Production Checklist Overview Comprehensive go-live checklist for ClickHouse covering schema and engine design, server tuning, backup configuration, monitoring, security, application integration, and operational readiness. Walk the eight sections top to bottom; each is a gate that must be green before production traffic is allowed. Deep configuration — server XML, backup SQL, and verification queries — lives in references/ so this file stays a fast operational scan. Prerequisites Before starting the checklist, confirm the following are in place: A ClickHouse instance is provisioned (ClickHouse Cloud or self-hosted) and reachable from the environment you will run traffic from. Application integration code has been exercised end-to-end in a staging environment against a ClickHouse of the same major version. You have admin credentials able to read system. tables and, for self-hosted, edit config.xml / users.xml. Instructions Work each section in order. Every box must be checked (or explicitly waived with a reason) before go-live. 1. Schema & Engine Design [ ] Tables use MergeTree family engines (not Memory, Log, or TinyLog) [ ] ORDER BY columns match primary filter/group patterns [ ] PARTITION BY is coarse (monthly or weekly, never by ID) [ ] TTL configured for data retention policy [ ] LowCardinality(String) used for low-cardinality columns [ ] CODEC(ZSTD) applied to large String/JSON columns [ ] ReplacingMergeTree used with FINAL or dedup logic if upserts needed 2. Server Configuration (Self-Hosted) Set memory to ~80% of RAM, cap per-query memory and execution time, and size the merge pools to the core count. ClickHouse Cloud manages these for you. Full annotated config.xml / users.xml block and tuning rationale: server configuration reference. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickhouse-prod-checklist