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).
All-time #4908Trending #3540Hot #5837First seen Jul 27, 2026
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.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars530
LicenseLICENSE
Default branchmain
Open issues1
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Version0.3.0
LicenseApache-2.0
More metadata
author
ClickHouse Inc
version
0.3.0
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,645 B
docsREADME.md1,161 B
docsSUMMARY.md522 B
History
First seen on skills.sh
First recorded snapshot · 2,700 installs
SKILL.md
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:
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.
