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

/infra-postgres

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

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. Also use when migrating an existing Postgres database (Neon, Supabase, RDS, Aurora, Cloud SQL, self-hosted) into ClickHouse Cloud Postgres.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈164 tokens for metadata: the name and description. ≈754 when used: this file. ≈5.8k more on demand in 5 files.

Description uses 8.2% 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 ≈653 characters, or 8.2%.

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)

Postgres with clickhousectl

clickhousectl manages Postgres in two environments:

  • Local — named, Docker-backed Postgres instances on the user's machine, for development.
  • Cloud — managed Postgres services in ClickHouse Cloud, for production: HA, read replicas, point-in-time restore.

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

Which reference to use

The user wants to... Read
Develop or prototype locally, run tests/CI against Postgres, no cloud account needed ref/local.md
Go to production, host a managed Postgres, or use ClickHouse Cloud explicitly ref/cloud.md
Operate an existing cloud service (passwords, TLS, config, replicas, failover, restore) ref/cloud.md
Migrate an existing Postgres (Neon, Supabase, RDS, ...) into ClickHouse Cloud Postgres ref/migrate.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 Postgres 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

  • To replicate Postgres data into ClickHouse for analytics, see ClickPipes (clickhousectl cloud clickpipe --help). ClickPipes cannot target a Postgres service — for Postgres-to-Postgres migration use ref/migrate.md.
  • For ClickHouse itself (local development or ClickHouse Cloud services), use the infra-clickhouse 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.

1 alerttoday3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill provides a comprehensive workflow for managing PostgreSQL databases locally and in ClickHouse Cloud using the clickhousectl CLI. All identified external resources and installation patterns are official ClickHouse vendor-controlled tools, following expected behavior for a database infrastructure skill.

  • Sockettoday

    No alerts

  • Snyk1d

    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 23 minutes ago.

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

README badge

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