How do I install the Infra Clickhouse skill?

Run npx skillmds@latest add clickhouse/infra-clickhouse in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Infra Clickhouse safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Infra Clickhouse?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Infra Clickhouse free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Infra Clickhouse?

ClickHouse (@clickhouse) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Infra Clickhouse by clickhouse — Agent Skill

Name: Infra Clickhouse
Rating: 4.2 (5 reviews)
Author: ClickHouse

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.

ClickHouse 4e6bb0b 5 files · 13.2 KB Updated Sep 9, 2026

File contents

ClickHouse with clickhousectl

clickhousectl manages ClickHouse in two environments:

Local — ClickHouse installed and running on the user's machine, for development.
Cloud — managed ClickHouse Cloud services, for production: fully managed, automatic scaling, backups, and upgrades.

This file routes to the right reference. The step-by-step workflows live in ref/local.md and ref/cloud.md — read the one that matches the user's situation before running commands.

Which reference to use

The user wants to...	Read
Build an app with ClickHouse, develop or prototype locally, no cloud account needed	ref/local.md
Go to production, host a managed ClickHouse, or use ClickHouse Cloud explicitly	ref/cloud.md
Operate an existing cloud service (schemas, users, queries against it)	ref/cloud.md
Develop locally now, ship to production later	Start with ref/local.md; it points to ref/cloud.md when it's time to go to prod

If it's genuinely ambiguous (e.g. "set up ClickHouse for my app"), default to local for development tasks and ask before creating anything in the cloud — cloud services cost money.

Prerequisites (both workflows)

Check that clickhousectl is installed:

which clickhousectl

If not found, install it:

curl -fsSL https://clickhouse.com/cli | sh

This installs to ~/.local/bin/clickhousectl (with a chctl alias). If the command is still not found, suggest export PATH="$HOME/.local/bin:$PATH" or a new terminal.

All commands accept --json for machine-readable output. Exit codes follow gh conventions: 0 success, 1 error, 2 cancelled, 4 auth required.

When designing schemas, consult the clickhouse-best-practices skill for ORDER BY selection, data types, and partitioning.
For Postgres (local development or managed ClickHouse Cloud Postgres), use the infra-postgres skill.

---name: infra-clickhousedescription: 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.license: Apache-2.0--- # ClickHouse with clickhousectl `clickhousectl` manages ClickHouse in two environments: - **Local** — ClickHouse installed and running on the user's machine, for development. - **Cloud** — managed ClickHouse Cloud services, for production: fully managed, automatic scaling, backups, and upgrades. This file routes to the right reference. The step-by-step workflows live in `ref/local.md` and `ref/cloud.md` — read the one that matches the user's situation before running commands. ## Which reference to use | The user wants to... | Read | |----------------------|------| | Build an app with ClickHouse, develop or prototype locally, no cloud account needed | [ref/local.md](ref/local.md) | | Go to production, host a managed ClickHouse, or use ClickHouse Cloud explicitly | [ref/cloud.md](ref/cloud.md) | | Operate an existing cloud service (schemas, users, queries against it) | [ref/cloud.md](ref/cloud.md) | | Develop locally now, ship to production later | Start with [ref/local.md](ref/local.md); it points to [ref/cloud.md](ref/cloud.md) when it's time to go to prod | If it's genuinely ambiguous (e.g. "set up ClickHouse for my app"), default to local for development tasks and ask before creating anything in the cloud — cloud services cost money. ## Prerequisites (both workflows) Check that `clickhousectl` is installed: ```bash which clickhousectl ``` If not found, install it: ```bash curl -fsSL https://clickhouse.com/cli | sh ``` This installs to `~/.local/bin/clickhousectl` (with a `chctl` alias). If the command is still not found, suggest `export PATH="$HOME/.local/bin:$PATH"` or a new terminal. All commands accept `--json` for machine-readable output. Exit codes follow `gh` conventions: 0 success, 1 error, 2 cancelled, 4 auth required. ## Related - When designing schemas, consult the `clickhouse-best-practices` skill for ORDER BY selection, data types, and partitioning. - For Postgres (local development or managed ClickHouse Cloud Postgres), use the `infra-postgres` skill.

Frequently asked questions