Index of every page on this site: llms.txt
All skills
clickhouse avatar

/infra-clickhouse

@1008fd7 official
by clickhouseclickhouse/agent-skills573 stars
37
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/clickhouse/agent-skills/infra-clickhouse

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈130 tokens for metadata: the name and description. ≈686 when used: this file. ≈4.1k more on demand in 4 files.

Description uses 6.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈518 characters, or 6.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Last updated 2026-11-19 for clickhousectl 0.6.0. (update the CLI with clickhousectl update, update skills with clickhousectl skills)

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, and switch to JSON automatically when run by a coding agent. SQL output from local client and local postgres client stays in psql or clickhouse-client's native format. Exit codes: 0 success, 1 error, 2 usage error, 3 cancelled, 4 auth required.

To find a command or flag by keyword, run clickhousectl search <words>. To check state before acting, run clickhousectl local status (this project's local ClickHouse and Postgres instances) and clickhousectl cloud auth status (the active Cloud credentials).

If the CLI lacked something you needed, or its help misled you, send a short note to the clickhousectl team with clickhousectl feedback "<the gap>".

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 alertstoday3 checks · Risk HIGH
  • Gen Agent Trust Hubtoday

    This skill facilitates the management of ClickHouse databases across local and cloud environments using the official clickhousectl CLI. It implements standard workflows for environment setup, schema migration, and user provisioning, including secure credential handling through interactive prompts and environment file management.

  • Socket17d

    No alerts

  • Snyktoday

    Risk: CRITICAL · 2 issues

Signed by skilld at 1008fd7. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 minutes ago.

Activeupdated yesterday
Other metadata
metadata
{
  "author": "ClickHouse Inc",
  "version": "0.5.0",
  "clickhousectl-version": "0.6.0"
}

README badge

README badge for clickhouse/agent-skills/infra-clickhouse