Clickhouse Js Node Troubleshooting Agent Skill

> 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.

8k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/ClickHouse/mintlify-docs-dev --skill clickhouse-js-node-troubleshooting

What comes with it

27 068 bytes besides the instruction

.DS_Store

metadata.json

reference/compression.mdx

reference/data-types.mdx

reference/logging.mdx

reference/proxy-pathname.mdx

reference/query-params.mdx

reference/readonly-users.mdx

reference/socket-hangup.mdx

reference/tls.mdx

The instruction itself

4 sections, as written by the author

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

Identify the issue — match symptoms to the Issue Index below and read the corresponding reference file.
Lead with the diagnosis — explain what's likely causing the issue before giving the fix.
Note version constraints — flag if a fix requires a minimum client version and check it against what the user provided.
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 | 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 |

Still Stuck?

How to use it

Copy the folder

Take clickhouse/mintlify-docs-dev-clickhouse-js-node-troubleshooting from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.