clickhouse-io

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

Quality

67%

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/ja-JP/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 body is highly actionable with comprehensive executable ClickHouse examples, but it is a monolithic 430-line catalog with no progressive disclosure and includes some conceptual over-explanation Claude does not need.

Suggestions

Move the analytics-query catalog (time-series, funnel, cohort) and pipeline patterns into separate reference files linked from a concise overview to improve progressive disclosure.

Remove or condense the 概要 section's explanation of what ClickHouse/OLAP is, since Claude already knows this.

Add a brief validation checkpoint to the ETL/CDC pipeline steps (e.g. verifying row counts or schema after load) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with executable code and useful PASS/FAIL contrasts, but the 概要 section explains what ClickHouse and OLAP are — concepts Claude already knows — which could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready SQL DDL, queries, and TypeScript across table design, inserts, materialized views, monitoring, and pipelines, with concrete examples covering the common cases.	5 / 5
Workflow Clarity	This is a patterns catalog rather than a sequenced workflow, and the ETL/CDC sections give only loose numbered steps with no validation checkpoints, fitting the 'sequence present but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but at 430 lines everything is inlined in a single SKILL.md with no bundle files or one-level-deep references for the analytics-catalog and pipeline material that could live separately.	3 / 5
	Total	14 / 20 Passed

Description

70%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 is specific and clearly niched to ClickHouse analytical workloads, but it omits an explicit 'Use when...' trigger clause, which limits its completeness. Trigger-term quality and distinctiveness are strong.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user works with ClickHouse, optimizes analytical queries, or designs high-performance OLAP data pipelines.'

Frame capabilities as discrete actions (e.g. 'design MergeTree tables, optimize queries, build materialized views') rather than category labels to lift specificity toward the top anchor.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas — "query optimization", "analytics", and "data engineering best practices" — giving broad coverage of the domain, though framed as categories rather than discrete actions, stopping short of the comprehensive multi-action anchor.	4 / 5
Completeness	Clearly states what the skill covers but lacks any "Use when..." trigger clause, so per the rubric guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ("ClickHouse", "query optimization", "analytics", "data engineering", "analytical workloads") with good keyword coverage, missing only a few synonyms or variations.	4 / 5
Distinctiveness Conflict Risk	Named to a specific product (ClickHouse) with a clear analytical-DB niche, making it highly distinct with minimal risk of triggering for unrelated skills.	5 / 5
	Total	16 / 20 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/ja-JP/skills/clickhouse-io/SKILL.md
Commit: e04ea0b

Reviewed: 2 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.