
setup
Set up the clickhouse-js repository in a fresh checkout so the agent can run tests, lints, type checks, builds, or examples. Use this skill before invoking any npm run test:, npm run lint, npm run typecheck, npm run build, or npm run run-examples script — or after pulling changes that touch any package.json (root, examples/node, or examples/web). Covers Node.js version requirements, installing dependencies across the npm workspaces and the two independent example packages, building the workspace packages so inter-package imports resolve, and starting ClickHouse via Docker Compose for integration tests. Do NOT use this skill for downstream user projects that merely depend on @clickhouse/client or @clickhouse/client-web; it is specific to contributing to the ClickHouse/clickhouse-js repo itself.
- Installs
- 44
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/clickhouse/clickhouse-js --skill setup- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads setup automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
clickhouse-js Repository Setup
Use this skill before running any of the npm run test:*, npm run lint, npm run typecheck, or npm run build scripts in a fresh checkout (or after pulling changes that touch package.json files).
Prerequisites
- Node.js 22 recommended (matches
.nvmrc). The rootpackage.jsondeclares"engines": { "node": ">=20.19.0" }, and CI tests Node 20, 22, 24, and 26. - Docker with the Compose plugin (
docker compose ...). Required only for integration tests and any example that talks to a real server.
1. Install dependencies
This is an npm workspaces repo (packages/*), with two additional independent example packages (examples/node, examples/web) that have their own package.json and are not part of the workspaces.
Install all three:
npm install
npm --prefix examples/node install
npm --prefix examples/web install
The root postinstall script patches node_modules/parquet-wasm/package.json; it runs automatically as part of npm install.
2. Build the workspace packages
The workspace packages (@clickhouse/client-common, @clickhouse/client, @clickhouse/client-web) must be built before some tests, examples, and typechecks can resolve their inter-package imports:
npm run build
This runs build in every workspace package.
3. Start ClickHouse (only for integration tests / examples)
Unit tests do not need a server. Integration tests (npm run test:*:integration*) and the example runners do.
From the repo root:
docker compose up -d
This starts both the single-node setup (clickhouse on 8123/9000, clickhouse_tls on 8443/9440) and the two-node cluster (clickhouse1, clickhouse2, plus the nginx round-robin entrypoint on 8127). All services use non-overlapping ports so a single up -d covers every integration test mode.
To override the server version, set CLICKHOUSE_VERSION when starting Compose; for example: CLICKHOUSE_VERSION=head docker compose up -d, CLICKHOUSE_VERSION=latest docker compose up -d, or CLICKHOUSE_VERSION=24.8 docker compose up -d to use an explicit version tag.
4. Verify
After the steps above you can run, for example:
npm run lint— lint every workspace packagenpm run typecheck— typecheck every workspace packagenpm run test:node:unit/npm run test:web:unit— unit tests, no server requirednpm run test:node:integration/npm run test:web:integration— integration tests, server required- From
examples/nodeorexamples/web:npm run lint,npm run typecheck,npm run run-examples
See npm run from the repo root for the full list of test scripts.
FAQ
What does the setup skill do?
Set up the clickhouse-js repository in a fresh checkout so the agent can run tests, lints, type checks, builds, or examples. Use this skill before invoking any npm run test:, npm run lint, npm run typecheck, npm run build, or npm run run-examples script — or after pulling changes that touch any package.json (root, examples/node, or examples/web). Covers Node.js version requirements, installing dependencies across the npm workspaces and the two independent example packages, building the workspace packages so inter-package imports resolve, and starting ClickHouse via Docker Compose for integration tests. Do NOT use this skill for downstream user projects that merely depend on @clickhouse/client or @clickhouse/client-web; it is specific to contributing to the ClickHouse/clickhouse-js repo itself.
How do I install setup?
Run npx skills add https://github.com/clickhouse/clickhouse-js --skill setup in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/setup/ (personal) or .claude/skills/setup/ (project).
Which AI agents can use setup?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is setup safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains setup?
It is published by clickhouse in clickhouse/clickhouse-js, and it is an official skill from the maker of the technology it covers. It has 44 recorded installs.
More from clickhouse/clickhouse-js
clickhouse-js-node-troubleshooting
clickhouse/clickhouse-js
Open the skill to read its SKILL.md instructions.
clickhouse-js-node-coding
clickhouse/clickhouse-js
Open the skill to read its SKILL.md instructions.
typescript-lsp
clickhouse/clickhouse-js
Open the skill to read its SKILL.md instructions.
clickhouse-js-node-rowbinary
clickhouse/clickhouse-js
Open the skill to read its SKILL.md instructions.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.