clickhouse / clickhouse-js

Three of the seven are what a user of @clickhouse/client would actually want: clickhouse-js-node-coding covers client setup, inserts, selects, parameter binding, sessions, and data types; clickhouse-js-node-rowbinary reads and writes the RowBinary wire formats; and clickhouse-js-node-troubleshooting — the one the readme documents — covers socket hang-ups, Keep-Alive issues, stream handling, and TLS or proxy problems. The other four are for working on this repository itself: setup installs dependencies and starts ClickHouse via Docker Compose before you can run the test suite, typescript-lsp wires up the TypeScript language server for precise go-to-definition and references across the workspace packages, and release and fix-release-pr drive the package's own release process — bumping versions, syncing the protected release branch, watching the gated npm publish, and routing CI fixes around branch protection instead of pushing straight to a locked branch.

This is for two different audiences wearing the same package: a developer writing application code against the Node.js or Web ClickHouse client gets three genuinely useful skills, while someone contributing to clickhouse-js itself, fixing a bug in the client or cutting a release, gets four skills that assume a checkout of the repository rather than just a dependency in package.json. If you only npm install @clickhouse/client, most of what's here doesn't apply to you.

READ THE FULL ANALYSIS＋

The readme undercounts its own skills by six. Its "AI Agent Skills" section lists exactly one, clickhouse-js-node-troubleshooting, with the other six left for a reader to find by browsing the skills/ directory or running npx skills add ClickHouse/clickhouse-js, which installs every skill in the repository at once regardless of which single one the readme mentions.