clickhouse-io

ClickHouse数据库模式、查询优化、分析以及高性能分析工作负载的数据工程最佳实践。

1.14x

Quality

63%

Does it follow best practices?

Impact

87%

1.14x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

65%Weight 40%Scale 1-5

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 comprehensive executable ClickHouse examples, but it is a monolithic inline catalog lacking progressive disclosure via reference files, and its batch operations omit validation feedback loops.

Suggestions

Split large reference material (analytics query library, ETL/CDC patterns, monitoring queries) into files under references/ and link to them from SKILL.md to improve progressive disclosure.

Add explicit validation/checkpoint steps for batch and CDC operations (e.g. verify row counts after bulk insert, reconcile source vs. target) to lift workflow clarity above the cap.

Trim the '概述' concept primer and the redundant closing '记住' summary since Claude already knows what ClickHouse and OLAP are.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, actionable code, but the '概述' section explains concepts Claude already knows (what ClickHouse is, OLAP, columnar storage, compression) and the closing '记住' summary is largely redundant, so it could be tightened.	3 / 5
Actionability	It provides comprehensive, copy-paste-ready SQL and TypeScript examples covering the common cases — MergeTree table designs, indexed filtering, aggregations, window functions, batch/streaming inserts, materialized views, monitoring, and ETL/CDC pipelines.	5 / 5
Workflow Clarity	This is a pattern catalog rather than a sequenced workflow, and the batch operations (bulk inserts, CDC sync) lack explicit validation/checkpoint feedback loops, which per the scoring notes caps workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist and all ~445 lines live inline in SKILL.md; section headers give good structure, but analytics-query, ETL, and monitoring content that clearly belongs in separate reference files is inlined with no external references signaled.	3 / 5
	Total	14 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 clearly identifies a distinct ClickHouse analytics niche and lists several concrete capability areas, but it lacks an explicit 'Use when...' trigger clause and misses common synonym keywords users might naturally say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing ClickHouse schemas, optimizing analytical queries, or migrating OLAP workloads to ClickHouse.'

Include natural synonym keywords users actually say — 'OLAP', 'columnar/column store', 'real-time analytics' — to improve trigger-term coverage.

Drop or sharpen the generic '最佳实践' (best practices) phrasing in favor of more concrete actions.

Dimension	Reasoning	Score
Specificity	Names the ClickHouse domain plus several concrete capability areas — '数据库模式' (schema), '查询优化' (query optimization), '分析' (analytics), '数据工程最佳实践' (data engineering) — with only minor gaps in coverage, though '最佳实践' leans slightly toward generic phrasing.	4 / 5
Completeness	The 'what' is clear (schema, query optimization, analytics, data engineering for ClickHouse), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	It surfaces the core natural term 'ClickHouse' alongside relevant analytical keywords, but misses common synonyms and variations a user might actually say (e.g. 'OLAP', 'columnar', 'column store', 'real-time analytics'), placing it between generic and good keyword coverage.	3 / 5
Distinctiveness Conflict Risk	ClickHouse is a specific, well-bounded niche with distinct triggers (columnar OLAP analytics), so it is clearly distinguishable from other database/data skills with minimal conflict risk.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: xu-xiang/everything-claude-code-zh
Path: docs/zh-CN/skills/clickhouse-io/SKILL.md
Commit: dfbf946

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.