Chdb Sql

What it does

The instruction file distinguishes a one-off query, a persistent Session and a DB-API connection. Its examples combine local files, Python data and remote table functions. References cover query parameters, output formats and connectors; this is an application workflow rather than server administration.

Best for

SQL-oriented analysis of Parquet or CSV files, small reproducible analytical pipelines, and experiments that need ClickHouse expressions inside a Python process.

Tradeoffs and requirements

Installing a skill does not install or validate chDB. The source declares Python and platform requirements. Queries against remote services can move sensitive data, and persistent session directories need an explicit lifecycle. Parameter binding should replace string interpolation for values.

Requires Python 3.9+, macOS or Linux. pip install chdb.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code; this catalog never runs it.

npx skills add https://github.com/ClickHouse/agent-skills/tree/69a8354b05b5942e5cea77b6c87be7788303fc18/skills/chdb-sql --skill chdb-sql

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Network Access — review the source context.
• Shell Or Package Install — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

86/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

50/100

50

Originality

80/100

80

Static Safety

60/100

60

Supporting-file static inspection

Bounded source inspection, not a runtime security audit. No source code was executed.

2 text files inspected at this exact repository snapshot. 5 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.

• Network Client: 1 file — inspect context before use.

Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.

Suggested workflow

Prove a parameterized query on a local fixture first. Select the simplest API that provides the required state, then introduce external data only after reviewing connector permissions.

How to judge the result

Verify output schema, exact aggregates and behavior on missing files. For persistent sessions, reopen the database and confirm expected state; for remote joins, check transfer volume and credential handling separately.