clickhouse-js-node-troubleshooting — Claude Code skill
Troubleshoots socket hang-ups, data type mismatches, and TLS issues in the ClickHouse Node.js client (@clickhouse/client).
npx skills add ClickHouse/agent-skills --skill clickhouse-js-node-troubleshooting -a claude-codeWhat clickhouse-js-node-troubleshooting does
This skill diagnoses errors in the @clickhouse/client package. It targets network drops like ECONNRESET, stream insertion failures, GZIP compression errors for readonly=1 users, and query parameter interpolation bugs.
The workflow inspects symptoms against an issue index and reference guides. The agent explains the likely root cause first and checks client version requirements before proposing a patch. It will ask for your client version if a fix depends on it.
The skill only applies to Node.js environments, including Next.js Server Actions and route handlers. Applying these troubleshooting steps to Cloudflare Workers, browser components, or @clickhouse/client-web will lead to incorrect fixes.
What it helps with
- resolve socket hang up and ECONNRESET drops during long queries
- fix data type mismatches such as large integers returning as strings
- configure TLS certificates and paths behind reverse proxies
- troubleshoot response compression failures for read-only database users
Example prompts for the agent
- My ClickHouse inserts keep failing with socket hang up in Node.js, how do I fix this?
- Why are big integer columns returning as strings in @clickhouse/client?
- Help me resolve a TLS certificate handshake error when connecting to ClickHouse
How to install clickhouse-js-node-troubleshooting
1Skills CLI (Vercel)
npx skills add ClickHouse/agent-skills --skill clickhouse-js-node-troubleshooting -a claude-code2Manually: put the files in place
~/.claude/skills/clickhouse-js-node-troubleshooting/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/clickhouse-js-node-troubleshooting/
1Skills CLI (Vercel)
npx skills add ClickHouse/agent-skills --skill clickhouse-js-node-troubleshooting -a codex2Manually: put the files in place
.agents/skills/clickhouse-js-node-troubleshooting/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ClickHouse/agent-skills --skill clickhouse-js-node-troubleshooting -a cursor2Manually: put the files in place
.cursor/skills/clickhouse-js-node-troubleshooting/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ClickHouse/agent-skills clickhouse-js-node-troubleshooting2Manually: put the files in place
.github/skills/clickhouse-js-node-troubleshooting/SKILL.md1Skills CLI (Vercel)
npx skills add ClickHouse/agent-skills --skill clickhouse-js-node-troubleshooting -a gemini-cli2Platform CLI
gemini skills install https://github.com/ClickHouse/agent-skills --path skills/clickhouse-js-node-troubleshootingManually: put the files in place
.devin/skills/clickhouse-js-node-troubleshooting/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ClickHouse/agent-skills --skill clickhouse-js-node-troubleshooting -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about clickhouse-js-node-troubleshooting
How to install clickhouse-js-node-troubleshooting in Claude Code?
Run npx skills add ClickHouse/agent-skills --skill clickhouse-js-node-troubleshooting -a claude-code.
What does clickhouse-js-node-troubleshooting do?
It guides the assistant through diagnosing runtime errors, connection drops, and configuration issues in the @clickhouse/client Node.js package.
Does this skill support Edge runtimes or Cloudflare Workers?
No, it covers the standard Node.js runtime only. Edge runtimes and browser environments require @clickhouse/client-web, which has different networking constraints.
Source text
SKILL.md · Apache-2.0
--- name: clickhouse-js-node-troubleshooting description: > Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client). Use this skill whenever a user reports errors, unexpected behavior, or configuration questions involving the Node.js client specifically — including socket hang-up errors, Keep-Alive problems, stream handling issues, data type mismatches, read-only user restrictions, proxy/TLS setup problems, or long-running query timeouts. Trigger even when the user hasn't precisely named the issue; vague symptoms like "my inserts keep failing" or "connection drops randomly" in a Node.js context are strong signals to use this skill. Do NOT use for browser/Web client issues. --- # ClickHouse Node.js Client Troubleshooting Reference: https://clickhouse.com/docs/integrations/javascript > **⚠️ Node.js runtime only.** This skill covers the `@clickhouse/client` package running in a **Node.js runtime** exclusively — including **Next.js Node runtime** API routes, React Server Components, Server Actions, and standard Node.js processes. Do **not** apply this skill to browser client components, Web Workers, **Next.js Edge runtime**, Cloudflare Workers, or any usage of `@clickhouse/client-web`. For browser/edge environments, the correct package is `@clickhouse/client-web`. --- ## How to Use This Skill 1. **Identify the issue** — match symptoms to the Issue Index below and read the corresponding reference file. 2. **Lead with the diagnosis** — explain what's likely causing the issue before giving the fix. 3. **Note version constraints** — flag if a fix requires a minimum client version and check it against what the user provided. 4. **Ask only what's missing** — if the fix is version-dependent and you don't know their version, ask; otherwise help immediately. --- ## Issue Index Identify the user's issue from the list below and read the corresponding reference file for detailed troubleshooting steps. | Issue | Symptoms | Reference file | | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- | | **Socket Hang-Up / ECONNRESET** | `socket hang up`, `ECONNRESET`, intermittent connection drops, long-running queries timing out | `reference/socket-hangup.md` | | **Data Type Mismatches** | Large integers returned as strings, decimal precision loss, Date/DateTime insertion failures, `CANNOT_PARSE_INPUT_ASSERTION_FAILED` inserting a UUID into a `UInt128` column | `reference/data-types.md` | | **Read-Only User Errors** | Errors when using response compression with `readonly=1` users | `reference/readonly-users.md` | | **Proxy / Pathname URL Confusion** | Wrong database selected, requests failing behind a proxy with a path prefix | `reference/proxy-pathname.md` | | **TLS / Certificate Errors** | TLS handshake failures, certificate verification issues, mutual TLS setup | `reference/tls.md` | | **Compression Not Working** | GZIP compression not activating for requests or responses | `reference/compression.md` | | **Logging Not Showing Anything** | No log output, need custom logger integration | `reference/logging.md` | | **Query Parameters Not Interpolated** | Parameterized queries not working, SQL injection concerns | `reference/query-params.md` | | **FORMAT Clause / `SHOW POLICIES` Errors** | Syntax error from a duplicate `FORMAT`, or `SHOW [ROW] POLICIES` failing even with a format provided | `reference/query-format-clause.md` | --- ## Still Stuck? - [JS client source + full examples](https://github.com/ClickHouse/clickhouse-js/tree/main/examples) - [ClickHouse JS client docs](https://clickhouse.com/docs/integrations/javascript) - [ClickHouse supported formats](https://clickhouse.com/docs/interfaces/formats)
© ClickHouse · Apache-2.0 · ClickHouse/agent-skills