ClickHouse RowBinary for Node.js
ClickHouse/agent-skills
Generates TypeScript or JavaScript readers and writers for ClickHouse's RowBinary formats over HTTP in Node.js, after checking that RowBinary suits the data.
Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client).
Install Clickhouse JS Node Troubleshooting
$ npx skills add vemetric/vemetric --skill clickhouse-js-node-troubleshooting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vemetric/vemetric clickhouse-js-node-troubleshooting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vemetric/vemetric.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/clickhouse-js-node-troubleshooting .claude/skills/clickhouse-js-node-troubleshooting && rm -rf skills-srcUse ~/.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/
Install the "clickhouse-js-node-troubleshooting" agent skill from https://github.com/vemetric/vemetric/tree/main/.agents/skills/clickhouse-js-node-troubleshooting into .claude/skills/clickhouse-js-node-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickhouse-js-node-troubleshooting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vemetric/vemetric/tree/main/.agents/skills/clickhouse-js-node-troubleshootingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vemetric/vemetric --skill clickhouse-js-node-troubleshooting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vemetric/vemetric clickhouse-js-node-troubleshooting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vemetric/vemetric.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/clickhouse-js-node-troubleshooting .agents/skills/clickhouse-js-node-troubleshooting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clickhouse-js-node-troubleshooting" agent skill from https://github.com/vemetric/vemetric/tree/main/.agents/skills/clickhouse-js-node-troubleshooting into .agents/skills/clickhouse-js-node-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickhouse-js-node-troubleshooting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vemetric/vemetric --skill clickhouse-js-node-troubleshooting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vemetric/vemetric clickhouse-js-node-troubleshooting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vemetric/vemetric.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/clickhouse-js-node-troubleshooting .cursor/skills/clickhouse-js-node-troubleshooting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "clickhouse-js-node-troubleshooting" agent skill from https://github.com/vemetric/vemetric/tree/main/.agents/skills/clickhouse-js-node-troubleshooting into .cursor/skills/clickhouse-js-node-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickhouse-js-node-troubleshooting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vemetric/vemetric.git --path .agents/skills/clickhouse-js-node-troubleshooting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vemetric/vemetric --skill clickhouse-js-node-troubleshooting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vemetric/vemetric clickhouse-js-node-troubleshooting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vemetric/vemetric.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/clickhouse-js-node-troubleshooting .gemini/skills/clickhouse-js-node-troubleshooting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "clickhouse-js-node-troubleshooting" agent skill from https://github.com/vemetric/vemetric/tree/main/.agents/skills/clickhouse-js-node-troubleshooting into .gemini/skills/clickhouse-js-node-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickhouse-js-node-troubleshooting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vemetric/vemetric clickhouse-js-node-troubleshootingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vemetric/vemetric --skill clickhouse-js-node-troubleshooting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vemetric/vemetric.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/clickhouse-js-node-troubleshooting .github/skills/clickhouse-js-node-troubleshooting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "clickhouse-js-node-troubleshooting" agent skill from https://github.com/vemetric/vemetric/tree/main/.agents/skills/clickhouse-js-node-troubleshooting into .github/skills/clickhouse-js-node-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickhouse-js-node-troubleshooting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vemetric/vemetric --skill clickhouse-js-node-troubleshooting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vemetric/vemetric clickhouse-js-node-troubleshooting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vemetric/vemetric.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/clickhouse-js-node-troubleshooting .opencode/skills/clickhouse-js-node-troubleshooting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "clickhouse-js-node-troubleshooting" agent skill from https://github.com/vemetric/vemetric/tree/main/.agents/skills/clickhouse-js-node-troubleshooting into .opencode/skills/clickhouse-js-node-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickhouse-js-node-troubleshooting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
clickhouse-js-node-troubleshooting- GitHub stars
- 394
- Used in
- 1 other repo
- Token cost
- ~1.3k tokens
- SKILL.md length
- 319 words
- Files
- 10
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client).
- Works in 4 steps: Identify the issue — match symptoms to… → Lead with the diagnosis — explain what's… → Note version constraints — flag if a fix… → …
- A user reports errors
- SKILL.md covers How to Use This Skill, Issue Index and Still Stuck?
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Clickhouse JS Node Troubleshooting is an agent skill from vemetric/vemetric. 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…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files (for example `reference/compression.md`, `reference/data-types.md` and `reference/logging.md`).
It sits in Databases, covering Data warehousing. It works with ClickHouse and Node.js. The repository describes itself as: Simple, yet powerful Web- & Product Analytics. The licence is AGPL-3.0.
When your agent uses it
- A user reports errors
- Unexpected behavior
- Configuration questions involving the Node.js client specifically — including socket hang-up errors
- Keep-Alive problems
Example prompts
- “t precisely named the issue; vague symptoms like”
- “connection drops randomly”
- “/clickhouse-js-node-troubleshooting”
Requirements
- Node.js
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- 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.
What it can do on your machine
Read from SKILL.md and the folder at commit 6b7b01a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
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):
clickhouse.comgithub.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Clickhouse JS Node Troubleshooting loads about 1.3k tokens when it runs. Until then it costs about 174 tokens; SKILL.md has 319 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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 vemetric/vemetric at commit 6b7b01a, republished under its AGPL-3.0 licence (© vemetric). 319 words, ~1,281 tokens.
Download SKILL.mdSave it as
.claude/skills/clickhouse-js-node-troubleshooting/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- 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/clientpackage 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, 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?
© vemetric, AGPL-3.0. 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 9 other files in .agents/skills/clickhouse-js-node-troubleshooting of vemetric/vemetric.
- SKILL.md
- reference/compression.md
- reference/data-types.md
- reference/logging.md
- reference/proxy-pathname.md
- reference/query-format-clause.md
- reference/query-params.md
- reference/readonly-users.md
- reference/socket-hangup.md
- reference/tls.md
Open the folder on GitHubat commit 6b7b01a
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in vemetric/vemetric, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Clickhouse JS Node Troubleshooting 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Clickhouse JS Node Troubleshooting this skillvemetric/vemetric | 394 | 1 repos | ~1.3k | Automated safety check: Pass | AGPL-3.0 | |
| ClickHouse RowBinary for Node.jsClickHouse/agent-skills | 544 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Adding Ingestion WarningsPostHog/posthog | 40k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Clickhouse Install Authjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Notes | MIT | |
| Ar Io Gateway Operatorar-io/ar-io-node | 127 | — | ~8.2k | Automated safety check: Notes | AGPL-3.0 | |
| Monitoring Ingestion PipelinePostHog/posthog | 40k | — | ~9.1k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Adding Ingestion Warnings
PostHog/posthog
How to add a new ingestion warning type to the event ingestion pipeline.
Clickhouse Install Auth
jeremylongshore/tons-of-skills-marketplace
Install @clickhouse/client and configure authentication to ClickHouse Cloud or self-hosted.
Ar Io Gateway Operator
ar-io/ar-io-node
Operate any AR.IO node deployment — architecture, daily ops, diagnostics, and recurring pitfalls that apply to every operator.
- Official
Monitoring Ingestion Pipeline
PostHog/posthog
Guide for using the Grafana MCP to monitor and diagnose the Node.js ingestion pipeline workers in production.
Testing
ar-io/ar-io-node
Decision guide for testing in the ar-io-node repo — which test layer to use, how to run it, and which helpers to reach for.
More from vemetric/vemetric
Chdb Datastore
vemetric/vemetric
A skill your agent uses when the user has tabular data (pandas DataFrame, parquet, csv, Arrow, json) and wants to filter, group, aggregate, join, or speed up slow pandas.
Chdb SQL
vemetric/vemetric
A skill your agent uses when the user wants to run SQL — especially analytical SQL — on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse…
Clickhouse Architecture Advisor
vemetric/vemetric
MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs.
Clickhouse Best Practices
vemetric/vemetric
MUST USE when reviewing ClickHouse schemas, queries, or configurations.
Clickhouse JS Node Coding
vemetric/vemetric
Write idiomatic application code with the ClickHouse Node.js client (@clickhouse/client).
Related
Works with
Categories
Questions about Clickhouse JS Node Troubleshooting
What does Clickhouse JS Node Troubleshooting do?
Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client). Clickhouse JS Node Troubleshooting is an agent skill from vemetric/vemetric.js client (@clickhouse/client).
When should I use Clickhouse JS Node Troubleshooting?
Clickhouse JS Node Troubleshooting fits situations like: A user reports errors; unexpected behavior; configuration questions involving the Node.js client specifically — including socket hang-up errors; keep-Alive problems.
How do I install Clickhouse JS Node Troubleshooting in Claude Code?
Run `npx skills add vemetric/vemetric --skill clickhouse-js-node-troubleshooting -a claude-code`. Or copy the skill folder (.agents/skills/clickhouse-js-node-troubleshooting in vemetric/vemetric) into .claude/skills/clickhouse-js-node-troubleshooting in your project. Claude Code loads it when a task matches its description.
How do I install Clickhouse JS Node Troubleshooting in Codex?
Run `npx skills add vemetric/vemetric --skill clickhouse-js-node-troubleshooting -a codex`. Or copy the skill folder (.agents/skills/clickhouse-js-node-troubleshooting in vemetric/vemetric) into .agents/skills/clickhouse-js-node-troubleshooting in your project. Codex loads it when a task matches its description.
Can I use Clickhouse JS Node Troubleshooting 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 vemetric/vemetric --skill clickhouse-js-node-troubleshooting -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-js-node-troubleshooting, .gemini/skills/clickhouse-js-node-troubleshooting, .github/skills/clickhouse-js-node-troubleshooting and .opencode/skills/clickhouse-js-node-troubleshooting in your project.
What does Clickhouse JS Node Troubleshooting need to run?
SKILL.md names no scripts, command-line tools or credentials: Clickhouse JS Node Troubleshooting is instructions for the agent only. Our summary lists: Node.js.
Does Clickhouse JS Node Troubleshooting access the network?
SKILL.md names 2 domains. As links in the text: clickhouse.com and github.com. This is read from the text; nothing was executed.
Is Clickhouse JS Node Troubleshooting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Clickhouse JS Node Troubleshooting use?
Clickhouse JS Node Troubleshooting is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Clickhouse JS Node Troubleshooting use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Clickhouse JS Node Troubleshooting?
Skills that share tags, products or a category with Clickhouse JS Node Troubleshooting: ClickHouse RowBinary for Node.js (ClickHouse/agent-skills, 544 stars), Adding Ingestion Warnings (PostHog/posthog, 40k stars), Clickhouse Install Auth (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Ar Io Gateway Operator (ar-io/ar-io-node, 127 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clickhouse JS Node Troubleshooting?
vemetric (a GitHub organization) maintains it in vemetric/vemetric, which has 394 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.
Source: vemetric/vemetric on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.