skillZs
LIVE SKILL TAGS
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
REAL INSTALL DATA
← back to all skills
clickhouse/agent-skills1k installs

infra-postgres

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.

How do I install this agent skill?

npx skills add https://github.com/clickhouse/agent-skills --skill infra-postgres
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides workflows for managing PostgreSQL databases using ClickHouse's official CLI tool. It includes instructions for local development using Docker and managing cloud-hosted Postgres instances. All external resources, including the installation script and documentation, originate from ClickHouse's own verified infrastructure.

  • Socketpass

    No alerts

  • Snykfail

    Risk: HIGH · 2 issues

What does this agent skill do?

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 (beta), 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 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
Develop or prototype locally, run tests/CI against Postgres, no cloud account neededref/local.md
Go to production, host a managed Postgres, or use ClickHouse Cloud explicitlyref/cloud.md
Operate an existing cloud service (passwords, TLS, config, replicas, failover, restore)ref/cloud.md
Develop locally now, ship to production laterStart 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. Exit codes follow gh conventions: 0 success, 1 error, 2 cancelled, 4 auth required.

Related

  • To replicate Postgres data into ClickHouse for analytics, see ClickPipes (clickhousectl cloud clickpipe --help).
  • For ClickHouse itself (local development or ClickHouse Cloud services), use the infra-clickhouse skill.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/clickhouse/agent-skills/infra-postgres">View infra-postgres on skillZs</a>