clickhouse-io

ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/zh-TW/skills/clickhouse-io/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with rich, executable ClickHouse examples, but it reads as a large monolithic reference rather than an overview pointing to deeper material, and batch/ETL workflows lack validation checkpoints.

Suggestions

Add validation/verification steps to the ETL and CDC pipeline examples (e.g., verify row counts after bulk insert, confirm schema before loading).

Split detailed catalogs (analytics queries, data pipeline patterns) into reference files under references/ and keep SKILL.md as a concise overview with one-level-deep links.

Trim the overview section's explanation of what ClickHouse is and the closing "記住" recap, since Claude already knows the basics.

Dimension	Reasoning	Score
Conciseness	The body is mostly an efficient code catalog, but the overview explains concepts Claude already knows ("ClickHouse 是一個列式資料庫管理系統（DBMS），用於線上分析處理（OLAP）") and could be trimmed.	2 / 3
Actionability	Extensive executable SQL and TypeScript examples with specific ClickHouse functions (sumMerge, uniqState, quantile, system.query_log) are copy-paste ready throughout.	3 / 3
Workflow Clarity	It is a pattern reference rather than a sequenced workflow, and batch/ETL operations (bulkInsertTrades, etlPipeline) lack validation or verification checkpoints, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	Sections are well-organized, but it is a monolithic ~430-line SKILL.md with no bundle files or references, so content that could be split (analytics queries, data pipelines) is all inline.	2 / 3
	Total	9 / 12 Passed

Description

57%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is clearly ClickHouse-scoped and unlikely to conflict, but it describes capability areas at a high level without concrete actions or an explicit "when to use" trigger, which caps both completeness and specificity.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when working with ClickHouse, optimizing analytical queries, or designing columnar tables for OLAP workloads.").

Replace abstract phrasing like "patterns" and "best practices" with a few concrete actions (e.g., "design MergeTree tables, optimize analytical queries, build materialized views for real-time aggregation").

Dimension	Reasoning	Score
Specificity	The description names the ClickHouse domain and several capability areas ("query optimization, analytics, and data engineering best practices"), but "patterns" and "best practices" are abstract rather than concrete actions like "extract text, fill forms, merge documents."	2 / 3
Completeness	It clearly states what the skill covers but has no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Natural terms users would say ("ClickHouse", "query optimization", "analytics") are present, but "high-performance analytical workloads" is jargon-ish and common trigger variations are missing.	2 / 3
Distinctiveness Conflict Risk	"ClickHouse database patterns" carves out a clear, product-specific niche that is unlikely to trigger for or conflict with other skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: affaan-m/ECC
Path: docs/zh-TW/skills/clickhouse-io/SKILL.md
Commit: 06c5e11

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.