clickhouse

Configures ClickHouse query building with squirrel for telemetry analytics.

258|33|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/speakeasy-api/gram --skill clickhouse-speakeasy-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clickhouse
Source: https://github.com/speakeasy-api/gram/tree/main/.agents/skills/clickhouse
Command: npx skills add https://github.com/speakeasy-api/gram --skill clickhouse-speakeasy-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rules for working with ClickHouse in Gram's telemetry analytics, providing a clear separation from PostgreSQL workflows and guidance on query construction.

Core Features & Use Cases

  • Use the squirrel query builder for ClickHouse queries in the telemetry package to enable dynamic, high-performance analytics.
  • Enforce that ClickHouse queries are not generated via SQLc and that PostgreSQL remains SQLc-driven.
  • Provide structure guidance (queries.sql.go, pagination.go, README.md) and a standardized approach for adding and testing new ClickHouse queries.

Quick Start

Follow the 'Adding ClickHouse Queries' guidance to begin building a ClickHouse query with the squirrel builder in the telemetry package.

Frequently Asked Questions about clickhouse

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

FAQPage Schema
How do I build ClickHouse queries for telemetry analytics in Go?

Use the squirrel query builder to construct ClickHouse queries within your telemetry package. This approach enables dynamic, high-performance analytics while maintaining a clear separation from PostgreSQL workflows.

Can I use SQLc to generate ClickHouse queries alongside PostgreSQL?

No, SQLc is disallowed for ClickHouse queries and should remain strictly PostgreSQL-driven. The squirrel builder is required for ClickHouse to ensure clear code separation and dynamic query construction.

What is the recommended file structure for adding new ClickHouse queries?

The recommended file structure includes queries.sql.go for query definitions, pagination.go for handling pagination logic, and a README.md for standardized guidance on adding and testing new ClickHouse queries.

Why separate ClickHouse and PostgreSQL query workflows in a telemetry package?

Separating ClickHouse analytics from PostgreSQL workflows prevents code conflicts and enforces specific query builders. ClickHouse requires the squirrel builder for high performance, while PostgreSQL retains SQLc for code generation.

Does the squirrel query builder support testing patterns for ClickHouse analytics?

Yes, the standardized approach provides specific file-structure and testing patterns for reliable implementation. Following the 'Adding ClickHouse Queries' guidance ensures new squirrel-built queries are properly tested within the telemetry package.