clickhouse-io

Optimize ClickHouse schema design, query performance, and ingestion pipelines for OLAP workloads.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill clickhouse-io-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clickhouse-io
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/skills/clickhouse-io
Command: npx skills add https://github.com/luongldptit/move-ticket --skill clickhouse-io-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ClickHouse users face challenges with slow analytical query performance, inefficient table schema design, and complex high-volume data ingestion pipelines for OLAP workloads, leading to delayed insights and increased infrastructure costs.

Core Features & Use Cases

  • Schema Design Patterns: Provides templates for MergeTree, ReplacingMergeTree, and AggregatingMergeTree engines optimized for different data deduplication and pre-aggregation needs.
  • Query Optimization: Includes best practices for efficient filtering, aggregations, and window functions to reduce query latency on large datasets.
  • Data Pipeline Implementation: Covers bulk insert, streaming ingestion, CDC from PostgreSQL, and materialized views for real-time analytics.
  • Use Case: A data engineering team building a real-time prediction market analytics dashboard can use this skill to design optimized table schemas, implement hourly aggregated materialized views, and reduce query response times for time-series metrics by over 60%.

Quick Start

Use the clickhouse-io skill to design an optimized MergeTree table schema for your time-series event data and implement a materialized view to calculate real-time daily active user counts.

Frequently Asked Questions about clickhouse-io

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize slow ClickHouse analytical query performance on large datasets?

Optimize slow ClickHouse analytical query performance by applying best practices for efficient filtering, aggregations, and window functions. This Skill provides implementation patterns to reduce query latency for large datasets and improve overall OLAP workload efficiency.

What is the best way to design a MergeTree table schema for time-series analytics?

The best way to design a MergeTree table schema for time-series analytics is using specialized engine templates. This Skill provides patterns for MergeTree, ReplacingMergeTree, and AggregatingMergeTree engines to optimize data deduplication and pre-aggregation needs.

How do I implement materialized views for real-time aggregation in ClickHouse?

Implement materialized views for real-time aggregation in ClickHouse by following provided data pipeline implementation patterns. This Skill covers streaming ingestion and materialized views to calculate real-time metrics like daily active user counts for analytics dashboards.

Can I migrate data from PostgreSQL to ClickHouse for high-volume OLAP workloads?

Yes, you can migrate data from PostgreSQL to ClickHouse for high-volume OLAP workloads using change data capture pipelines. This Skill provides migration patterns and bulk data ingestion implementations to meet high-performance analytical requirements.

When should I use ReplacingMergeTree vs AggregatingMergeTree engines in ClickHouse?

Use ReplacingMergeTree for data deduplication needs and AggregatingMergeTree for pre-aggregation requirements in ClickHouse. This Skill provides schema design templates to help choose the appropriate MergeTree engine based on your specific analytical query patterns.

What is causing delayed insights and high infrastructure costs in my ClickHouse data pipelines?

Delayed insights and high infrastructure costs in ClickHouse data pipelines are caused by inefficient table schema design, slow analytical query performance, and complex high-volume data ingestion. This Skill solves these inefficiencies to optimize OLAP workloads and reduce costs.