clickhouse-hello-world
Create your first ClickHouse table, insert data, and run analytical queries. Use when starting a new ClickHouse project, learning MergeTree basics, or testing your ClickHouse connection with real operations. Trigger with "clickhouse hello world", "first clickhouse table", "clickhouse quick start", "create clickhouse table", "clickhouse example".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickhouse-hello-world --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ClickHouse Hello World ## Overview Create a MergeTree table, insert rows with JSONEachRow, and run your first analytical query -- all using the official `@clickhouse/client`. This is the smoke test that proves your connection works and teaches the four MergeTree concepts (`ORDER BY`, `PARTITION BY`, `TTL`, `LowCardinality`) reused in every real schema. ## Prerequisites - `@clickhouse/client` ins
What does the clickhouse-hello-world skill do?
Create your first ClickHouse table, insert data, and run analytical queries. Use when starting a new ClickHouse project, learning MergeTree basics, or testing your ClickHouse connection with real operations. Trigger with "clickhouse hello world", "first clickhouse table", "clickhouse quick start", "create clickhouse table", "clickhouse example".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickhouse-hello-world --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
