clickhouse-best-practices

Skills

11 in the Claude listing

• Chdb datastoreUse when the user has tabular data (pandas DataFrame, parquet, csv, Arrow, json) and wants to filter, group, aggregate, join, or speed up slow pandas.
• Chdb sqlUse 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
• Clickhouse architecture advisorMUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs.
• Clickhouse best practicesMUST USE when reviewing ClickHouse schemas, queries, or configurations.
• Clickhouse js node codingWrite idiomatic application code with the ClickHouse Node.js client (`@clickhouse/client`).
• Clickhouse js node rowbinaryGenerate TypeScript/JavaScript code that reads/decodes AND writes/encodes ClickHouse RowBinary streams for the ClickHouse HTTP server.
• Clickhouse js node troubleshootingTroubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client).
• Clickhouse managed postgres rcaMUST USE when investigating performance issues on a ClickHouse-managed Postgres instance.
• Clickstack otel collectorUse 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 configuri
• Infra clickhouseSets 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,
• Infra postgresSets 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, r