Agent skill

Clickhouse Local Dev Loop

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Run ClickHouse locally with Docker, configure test fixtures, and iterate fast.

MITAuto-check: notesDatabases

Install Clickhouse Local Dev Loop

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickhouse-local-dev-loop -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace clickhouse-local-dev-loop --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/clickhouse-local-dev-loop .claude/skills/clickhouse-local-dev-loop && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
clickhouse-local-dev-loop
GitHub stars
2.8k
Token cost
~1.5k tokens
SKILL.md length
541 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Run ClickHouse locally with Docker, configure test fixtures, and iterate fast.

  • Works in 7 steps: Docker Compose setup — Write a… → Init script — Write… → Seed data — Write scripts/seed.ts that… → …
  • Setting up a local ClickHouse dev environment
  • SKILL.md covers Overview, Prerequisites, Authentication and Instructions, plus 5 more sections
  • Calls docker, curl and npm; needs CLICKHOUSE_PASSWORD

What it does

Clickhouse Local Dev Loop is an agent skill from jeremylongshore/tons-of-skills-marketplace. Run ClickHouse locally with Docker, configure test fixtures, and iterate fast. Use when setting up a local ClickHouse dev environment, writing integration tests against ClickHouse, or running ClickHouse in Docker Compose for local work. Trigger with "clickhouse local dev", "clickhouse docker", "clickhouse dev environment", "run clickhouse locally", "clickhouse docker compose".

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/examples.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code

It sits in Databases, covering Data warehousing, Containers and Test data and fixtures. It works with ClickHouse and Docker. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Setting up a local ClickHouse dev environment
  • Writing integration tests against ClickHouse
  • Running ClickHouse in Docker Compose for local work
  • With clickhouse local dev

Example prompts

  • “clickhouse local dev”
  • “clickhouse docker”
  • “clickhouse dev environment”
  • “/clickhouse-local-dev-loop”

Requirements

  • Node.js
  • Docker
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(docker:*), Bash(docker-compose:*)

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Docker Compose setup — Write a docker-compose.yml exposing 8123
  2. Init script — Write init-db/001-schema.sql with your
  3. Seed data — Write scripts/seed.ts that batch-inserts synthetic rows via
  4. Project structure — lay out init-db/, scripts/, src/, tests/, and
  5. Client singleton — Write src/db.ts exposing a memoized getClient()
  6. Integration testing — Write a vitest tests/setup.ts that TRUNCATEs
  7. Package scripts — Edit package.json to add db:up, db:down,

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(docker:*)
    • Bash(docker-compose:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • docker
    • curl
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • hub.docker.com
    • clickhouse.com
    • vitest.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CLICKHOUSE_PASSWORD

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Clickhouse Local Dev Loop loads about 1.5k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 541 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~101
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:46
    git-ignored `.env.local`; commit only a `.env.example`. Never reuse
  • NoteMentions a .env fileSKILL.md:83
    the `.env.local` / `.env.example` pair.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 541 words, ~1,529 tokens.

Download SKILL.mdSave it as .claude/skills/clickhouse-local-dev-loop/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
clickhouse-local-dev-loop
description
Run ClickHouse locally with Docker, configure test fixtures, and iterate fast. Use when setting up a local ClickHouse dev environment, writing integration tests against ClickHouse, or running ClickHouse in Docker Compose for local work. Trigger with "clickhouse local dev", "clickhouse docker", "clickhouse dev environment", "run clickhouse locally", "clickhouse docker compose".
allowed-tools
Read, Write, Edit, Bash(docker:*), Bash(docker-compose:*)
compatibility
Designed for Claude Code
version
1.7.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, database, analytics, clickhouse, olap

ClickHouse Local Dev Loop

Overview

Run ClickHouse in Docker for local development with fast schema iteration, seed data, and integration testing using vitest. This skill scaffolds a Docker-Compose-based dev loop: an auto-migrating init script, a seed generator, a reusable client singleton, and a truncate-between-tests integration harness — so schema changes and query work stay a docker compose up away.

Prerequisites

  • Docker or Docker Compose installed and running (docker info succeeds).
  • Node.js 18+ with the @clickhouse/client package for the seed/test scripts.
  • A local project directory you can Write files into. No cloud account or network access is required — everything runs on localhost.

Authentication

This is a local dev setup with no external ClickHouse Cloud service. The container's credentials are declared inline in docker-compose.yml (CLICKHOUSE_USER: default, CLICKHOUSE_PASSWORD: dev_password) and consumed by the client via env vars (CLICKHOUSE_USER, CLICKHOUSE_PASSWORD, CLICKHOUSE_HOST, CLICKHOUSE_DATABASE). Keep real per-developer overrides in a git-ignored .env.local; commit only a .env.example. Never reuse dev_password outside local development.

Instructions

Follow the seven-step build. The lean skeleton is below; the full walkthrough carries the complete file contents for every step.

  1. Docker Compose setup — Write a docker-compose.yml exposing 8123 (HTTP) and 9000 (native TCP), mounting ./init-db for auto-migration and a named volume for persistence:

    yaml
    services:
      clickhouse:
        image: clickhouse/clickhouse-server:latest
        ports: ["8123:8123", "9000:9000"]
        volumes:
          - clickhouse-data:/var/lib/clickhouse
          - ./init-db:/docker-entrypoint-initdb.d
        environment:
          CLICKHOUSE_PASSWORD: dev_password
          CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT: 1
    volumes:
      clickhouse-data:

    Then docker compose up -d and verify with curl http://localhost:8123/ping → Ok.

  2. Init script — Write init-db/001-schema.sql with your CREATE DATABASE / CREATE TABLE ... ENGINE = MergeTree() DDL. ClickHouse auto-runs it on the container's first start.

  3. Seed data — Write scripts/seed.ts that batch-inserts synthetic rows via client.insert({ format: 'JSONEachRow' }).

  4. Project structure — lay out init-db/, scripts/, src/, tests/, and the .env.local / .env.example pair.

  5. Client singleton — Write src/db.ts exposing a memoized getClient() that reads connection settings from env vars with localhost fallbacks.

  6. Integration testing — Write a vitest tests/setup.ts that TRUNCATEs tables in beforeEach and closes the client in afterAll, then write per-feature test files.

  7. Package scripts — Edit package.json to add db:up, db:down, db:reset, db:seed, db:shell, and test scripts.

Read the full walkthrough for the exact, copy-pasteable contents of each file.

Show full SKILL.md (212 more words)Show less

Output

Running this skill produces a working local ClickHouse dev loop:

  • A running clickhouse-server container reachable at http://localhost:8123 (HTTP) and localhost:9000 (native), answering curl .../ping with Ok.
  • An auto-created app database and schema from init-db/001-schema.sql.
  • Seedable data via npm run db:seed (default: 1000 synthetic events).
  • A green vitest integration suite that inserts and queries against the live container, resetting table state between tests.
  • One-command lifecycle scripts (db:up, db:down, db:reset, db:seed, db:shell, test) wired into package.json.

Error Handling

ErrorCauseSolution
Connection refused :8123Container not runningdocker compose up -d
READONLYUser lacks write permsSet CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT=1
Too many partsTiny frequent insertsBatch inserts or increase parts_to_throw_insert
Memory limit exceededLarge query on small containerAdd --memory 4g to Docker

Examples

Bring the stack up, seed it, and confirm the rows landed:

bash
docker compose up -d
curl http://localhost:8123/ping                 # → "Ok.\n"
npm run db:seed                                   # seeds 1000 events
curl 'http://localhost:8123/?query=SELECT+count()+FROM+app.events'   # → 1000

Open an interactive SQL shell:

bash
docker exec -it <container> clickhouse-client --password dev_password

See more examples — server-state inspection, HTTP queries, environment reset, and a passing integration-test run.

Resources

Next Steps

Once the local loop is green, see the clickhouse-sdk-patterns skill for production-ready client patterns (connection pooling, retries, typed query helpers, and async inserts) that build on the getClient() singleton above.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/clickhouse-local-dev-loop of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/examples.md
  • references/implementation.md

Open the folder on GitHubat commit 80f86df

Compare with similar skills

Clickhouse Local Dev Loop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clickhouse Local Dev Loop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clickhouse Local Dev Loop this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.5kAutomated safety check: NotesMIT
Local Platform E2Ecomputesdk/benchmarks126—~3kAutomated safety check: NotesMIT
Cloud SaaS Modechmonitor/chmonitor299—~2.5kAutomated safety check: NotesGPL-3.0
Debugging Signals PipelinePostHog/posthog40k—~2.4kAutomated safety check: NotesCustom licence
Funnelcake Deployment Workflowdivinevideo/divine-mobile266—~3.6kAutomated safety check: PassMPL-2.0
Test Environmentspetrkindlmann/qa-skills168—~4.6kAutomated safety check: PassMIT

Similar skills

  • Local Platform E2E

    computesdk/benchmarks

    Stand up benchmarks-platform locally (Postgres + MinIO + ClickHouse in docker) and run a real @benchsdk/runner benchmark against it, with no cloud or provider credentials.

    126 GitHub stars~3k tokensUpdated today
    DatabasesAuto-check: notes
  • Cloud SaaS Mode

    chmonitor/chmonitor

    Work on chmonitor's Cloud (SaaS) vs self-hosted (OSS) behaviour from ONE codebase.

    299 GitHub stars~2.5k tokensUpdated 4 days ago
    DatabasesAuto-check: notes
  • Official

    Debug the signals pipeline locally end-to-end. An agent skill from PostHog/posthog.

    40k GitHub stars~2.4k tokensUpdated today
    AI & LLM EngineeringAuto-check: notes
  • Funnelcake Deployment Workflow

    divinevideo/divine-mobile

    Deploy funnelcake (api + relay) to ANY environment (production, staging, poc) on GKE via ArgoCD.

    266 GitHub stars~3.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Test Environments

    petrkindlmann/qa-skills

    Design environment strategy for testing across dev, CI, preview, staging, and production — Docker Compose test infrastructure, multi-stage Dockerfiles, seed-data lifecycle, per-PR preview…

    168 GitHub stars~4.6k tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed
  • Official

    Explains how to run go-redis tests: the Docker Compose stack, make targets, focusing a single Ginkgo spec, the e2e suite and the version environment variables.

    22k GitHub stars~786 tokensUpdated yesterday
    Testing & QAAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Clickhouse Local Dev Loop

What does Clickhouse Local Dev Loop do?

Run ClickHouse locally with Docker, configure test fixtures, and iterate fast. Clickhouse Local Dev Loop is an agent skill from jeremylongshore/tons-of-skills-marketplace. Run ClickHouse locally with Docker, configure test fixtures, and iterate fast.

When should I use Clickhouse Local Dev Loop?

Clickhouse Local Dev Loop fits situations like: setting up a local ClickHouse dev environment; writing integration tests against ClickHouse; running ClickHouse in Docker Compose for local work; with clickhouse local dev.

How do I install Clickhouse Local Dev Loop in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickhouse-local-dev-loop -a claude-code`. Or copy the skill folder (skills/.curated/clickhouse-local-dev-loop in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/clickhouse-local-dev-loop in your project. Claude Code loads it when a task matches its description.

How do I install Clickhouse Local Dev Loop in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickhouse-local-dev-loop -a codex`. Or copy the skill folder (skills/.curated/clickhouse-local-dev-loop in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/clickhouse-local-dev-loop in your project. Codex loads it when a task matches its description.

Can I use Clickhouse Local Dev Loop in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickhouse-local-dev-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clickhouse-local-dev-loop, .gemini/skills/clickhouse-local-dev-loop, .github/skills/clickhouse-local-dev-loop and .opencode/skills/clickhouse-local-dev-loop in your project.

What does Clickhouse Local Dev Loop need to run?

Going by SKILL.md and its folder, Clickhouse Local Dev Loop needs the command-line tools its instructions call (docker, curl and npm) and credentials named CLICKHOUSE_PASSWORD. Our summary lists: Node.js; Docker. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(docker:*), Bash(docker-compose:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Clickhouse Local Dev Loop access the network?

SKILL.md names 3 domains. As links in the text: hub.docker.com, clickhouse.com and vitest.dev. This is read from the text; nothing was executed.

Is Clickhouse Local Dev Loop safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Clickhouse Local Dev Loop use?

Clickhouse Local Dev Loop is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clickhouse Local Dev Loop use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Clickhouse Local Dev Loop?

Skills that share tags, products or a category with Clickhouse Local Dev Loop: Local Platform E2E (computesdk/benchmarks, 126 stars), Cloud SaaS Mode (chmonitor/chmonitor, 299 stars), Debugging Signals Pipeline (PostHog/posthog, 40k stars) and Funnelcake Deployment Workflow (divinevideo/divine-mobile, 266 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clickhouse Local Dev Loop?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.