ClickHouse

ClickHouse getting-started skill

Get started with ClickHouse. What it is, and how to install, run, and query ClickHouse locally and in ClickHouse Cloud using the clickhousectl CLI. Use this when a user wants to understand ClickHouse or start building with it.

• “what is ClickHouse and when should I use it”
• “install and run ClickHouse locally”
• “start building an application on ClickHouse”

clickhouse-best-practices

MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 31 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.

• “review my ClickHouse schema for problems”
• “is my ClickHouse ORDER BY key right for this query pattern”
• “why is this ClickHouse query slow”

clickhouse-architecture-advisor

MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs. Complements clickhouse-best-practices with decision frameworks and explicit provenance labels.

• “design a ClickHouse architecture for high-volume event ingestion”
• “should I use materialized views or projections for this workload”
• “how should I model multi-tenant analytics in ClickHouse”

clickhouse-js-node-troubleshooting

Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client). Use this skill whenever a user reports errors, unexpected behavior, or configuration questions involving the Node.js client specifically — including socket hang-up errors, Keep-Alive problems, stream handling issues, data type mismatches, read-only user restrictions, proxy/TLS setup problems, or long-running query timeouts. Trigger even when the user hasn't precisely named the issue; vague symptoms like "my inserts keep failing" or "connection drops randomly" in a Node.js context are strong signals to use this skill. Do NOT use for browser/Web client issues.

• “my Node.js ClickHouse client keeps throwing socket hang up errors”
• “inserts from @clickhouse/client fail intermittently”
• “ClickHouse Node.js connection drops randomly under load”

chdb-datastore

Use when the user has tabular data (pandas DataFrame, parquet, csv, Arrow, json) and wants to filter, group, aggregate, join, or speed up slow pandas. Provides chDB DataStore — same pandas API, ClickHouse engine underneath. Also handles reading from S3, MySQL, PostgreSQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake as DataFrames and joining across sources. TRIGGER when: user mentions DataFrame, parquet, csv, "fast pandas", "speed up pandas", or cross-source DataFrame joins; user imports `chdb.datastore` or `from datastore import DataStore`. SKIP this skill for raw SQL syntax (use chdb-sql instead), ClickHouse server administration, or non-Python DataStore API work.

• “speed up my slow pandas code on a large dataset”
• “query parquet files in S3 as a pandas DataFrame”
• “join MySQL and Postgres data in Python without a server”

chdb-sql

Use 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 Cloud, Iceberg, Delta Lake) without setting up a server. Provides chDB — embedded ClickHouse SQL in Python with 1000+ functions, Session for stateful multi-step pipelines, parametrized queries, and cross-source joins via `s3()`, `mysql()`, `postgresql()`, `iceberg()`, `deltaLake()`, `remoteSecure()` table functions. TRIGGER when: user wants SQL on parquet/csv/files or across remote analytical sources; uses ClickHouse SQL features (window functions, windowFunnel, geoToH3, JSON path ops, Session, parametrized queries); imports `chdb` or calls `chdb.query()`. SKIP this skill for pandas-style DataFrame method-chaining (use chdb-datastore instead) or ClickHouse server administration.

• “run ClickHouse SQL on local parquet files without a server”
• “query CSV and JSON files with SQL from Python”
• “read S3 or Iceberg tables with ClickHouse table functions in Python”

infra-clickhouse

Sets up and manages ClickHouse using the clickhousectl CLI — installs and runs a local ClickHouse server for development, and creates managed ClickHouse Cloud services for production (authentication, service creation, schema migration, application connection). Use when the user wants to build an application with ClickHouse, set up a local ClickHouse dev environment, create tables and start querying, deploy ClickHouse to production or ClickHouse Cloud, or migrate from a local setup to the cloud.

infra-postgres

Sets up and manages Postgres using the clickhousectl CLI — runs a local Docker-backed Postgres for development, and creates and operates managed ClickHouse Cloud Postgres services (connections, TLS, runtime config, read replicas, failover, point-in-time restore). Use when the user wants a Postgres or PostgreSQL database for their application, a local Postgres dev environment, psql access, or a managed/production Postgres in ClickHouse Cloud, or mentions moving a local Postgres to production.

clickstack-otel-collector

Use when a user wants to wire an OpenTelemetry collector into a Managed ClickStack service on ClickHouse Cloud, either by deploying a new local collector (Docker run or Docker Compose) or by configuring their own existing collector, then send rich synthetic telemetry and verify it is visible in ClickStack.

ClickHouse Cloud MCP Server

Remote MCP server for ClickHouse Cloud: explore schemas and run SQL queries against your ClickHouse Cloud services.

• “query my ClickHouse Cloud database”
• “list the tables in my ClickHouse service and describe their schemas”
• “run this SQL against ClickHouse from my agent”

Managed ClickStack MCP Server

Remote MCP server for Managed ClickStack: search logs, traces, and metrics in your ClickStack observability data.

• “search my logs for errors in the last hour”
• “find slow traces in my observability data”
• “investigate a production incident with ClickStack”

ClickHouse API catalog

RFC 9727 catalog of ClickHouse public APIs, including the ClickHouse Cloud management API with its OpenAPI description.

• “manage ClickHouse Cloud services programmatically”
• “find the OpenAPI spec for the ClickHouse Cloud API”