How do I install the Clickhouse Principal Engineer skill?

Run npx skillmds@latest add modra40/clickhouse-principal-engineer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Clickhouse Principal Engineer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Clickhouse Principal Engineer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Clickhouse Principal Engineer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Clickhouse Principal Engineer?

modra40 (@modra40) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Clickhouse Principal Engineer by modra40

Name: Clickhouse Principal Engineer
Author: modra40

Clickhouse Principal Engineer

Principal/Senior-level ClickHouse playbook for analytical schema design, partitioning, ingestion, query performance, replication, storage strategy, and operating large-scale columnar systems. Use when: designing OLAP workloads, reviewing MergeTree layout, tuning analytical queries, building event analytics platforms, or operating ClickHouse in production.

modra40 d1d2dc3 9 files · 9.9 KB Updated Sep 17, 2026

File contents

ClickHouse Mastery (Senior → Principal)

Operate

Start from workload reality: event analytics, BI, observability, product analytics, or mixed ad-hoc usage.
Treat partitioning, ordering keys, ingestion shape, and retention as architecture decisions.
Prefer explicit tradeoffs between freshness, storage cost, and query speed.
Design for operational boringness around merges, replication, and late-arriving data.

Default Standards

Table engine and key design must match query patterns.
Partitioning should serve retention and query pruning, not fashion.
Ingestion rate, merge pressure, and background work must stay visible.
Materialized views should simplify workloads, not hide complexity debt.
Capacity planning must include disk, CPU, and merge behavior together.

References

Schema design and MergeTree strategy: references/schema-design-and-mergetree-strategy.md
Partitioning, ordering, and pruning: references/partitioning-ordering-and-pruning.md
Ingestion pipelines and late data: references/ingestion-pipelines-and-late-data.md
Query performance and aggregations: references/query-performance-and-aggregations.md
Replication, sharding, and reliability: references/replication-sharding-and-reliability.md
Storage, retention, and capacity planning: references/storage-retention-and-capacity-planning.md
Reliability and operations: references/reliability-and-operations.md
Incident runbooks: references/incident-runbooks.md

---name: clickhouse-principal-engineerdescription: Principal/Senior-level ClickHouse playbook for analytical schema design, partitioning, ingestion, query performance, replication, storage strategy, and operating large-scale columnar systems. Use when: designing OLAP workloads, reviewing MergeTree layout, tuning analytical queries, building event analytics platforms, or operating ClickHouse in production.---# ClickHouse Mastery (Senior → Principal)## Operate- Start from workload reality: event analytics, BI, observability, product analytics, or mixed ad-hoc usage.- Treat partitioning, ordering keys, ingestion shape, and retention as architecture decisions.- Prefer explicit tradeoffs between freshness, storage cost, and query speed.- Design for operational boringness around merges, replication, and late-arriving data.## Default Standards- Table engine and key design must match query patterns.- Partitioning should serve retention and query pruning, not fashion.- Ingestion rate, merge pressure, and background work must stay visible.- Materialized views should simplify workloads, not hide complexity debt.- Capacity planning must include disk, CPU, and merge behavior together.## References- Schema design and MergeTree strategy: [references/schema-design-and-mergetree-strategy.md](references/schema-design-and-mergetree-strategy.md)- Partitioning, ordering, and pruning: [references/partitioning-ordering-and-pruning.md](references/partitioning-ordering-and-pruning.md)- Ingestion pipelines and late data: [references/ingestion-pipelines-and-late-data.md](references/ingestion-pipelines-and-late-data.md)- Query performance and aggregations: [references/query-performance-and-aggregations.md](references/query-performance-and-aggregations.md)- Replication, sharding, and reliability: [references/replication-sharding-and-reliability.md](references/replication-sharding-and-reliability.md)- Storage, retention, and capacity planning: [references/storage-retention-and-capacity-planning.md](references/storage-retention-and-capacity-planning.md)- Reliability and operations: [references/reliability-and-operations.md](references/reliability-and-operations.md)- Incident runbooks: [references/incident-runbooks.md](references/incident-runbooks.md)

Frequently asked questions