cc-skill-clickhouse-io

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

Quality

55%

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 ./skills/cc-skill-clickhouse-io/SKILL.md

Quality

Content

57%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 a dense, largely executable ClickHouse cookbook with strong SQL examples, but it front-loads knowledge Claude already has, carries generic boilerplate sections, and provides no validation feedback loops for batch/database operations. Everything is inlined in one large file with no progressive disclosure into reference files.

Suggestions

Delete the Overview/Key Features explanations and the vacuous 'When to Use' line; Claude already knows what ClickHouse and OLAP are.

Add validation checkpoints around batch operations, e.g. verify inserted row counts against the source or query system.query_log after bulk loads before proceeding.

Split the analytics query cookbook (retention, funnel, cohort) and pipeline patterns into reference files linked one level deep from SKILL.md to reduce the monolithic inline content.

Dimension	Reasoning	Score
Conciseness	The Overview ('ClickHouse is a column-oriented database management system (DBMS) for online analytical processing (OLAP)') and the 'Key Features' list re-explain knowledge Claude already has, and 'This skill is applicable to execute the workflow or actions described in the overview' is vacuous filler. Mostly efficient code examples with some unnecessary explanation → anchor 3. Not 4 because the boilerplate Overview, Key Features, and generic When to Use/Limitations sections are clearly trimmable; not 2 because the bulk of the file is dense, useful code.	3 / 5
Actionability	Extensive concrete, executable SQL (MergeTree/ReplacingMergeTree/AggregatingMergeTree DDL, quantile aggregations, window functions, system.query_log monitoring) plus TypeScript insert patterns. Minor gaps: the streaming example references undefined 'dataSource' and 'clickhouse' variables, and the bulk insert builds SQL via string interpolation rather than parameterized values. Not 5 because of these incomplete/inadvisable snippets; not 3 because nearly all examples are copy-paste-ready.	4 / 5
Workflow Clarity	The ETL pattern lists a rough 1-2-3 sequence and sections are thematically ordered, but no validation or verification checkpoints exist for batch/bulk inserts or pipeline operations — database operations the rubric explicitly requires feedback loops for, capping workflow clarity at 3. Not 4 because validation is absent, not implicit-but-present; not 2 because sequences (ETL, CDC, monitoring) are listed and coherent.	3 / 5
Progressive Disclosure	The single ~430-line file has clear section headers, but no bundle files exist and content that clearly belongs in separate references (the analytics query cookbook, data pipeline patterns, monitoring queries) is fully inlined. Anchor 3 ('some structure but content that should be separate is inline'). Not 4 because nothing is split out at all; not 2 because the section structure keeps it navigable.	3 / 5
	Total	13 / 20 Passed

Description

53%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 the ClickHouse domain with several relevant capability areas, but it stops short of concrete actions and omits any 'Use when...' trigger guidance, which caps both completeness and trigger quality. The broad 'data engineering best practices' tail slightly weakens distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with ClickHouse, writing analytical SQL, designing MergeTree tables, or optimizing OLAP queries.'

Replace generic phrases like 'database patterns' and 'best practices' with concrete actions such as 'design MergeTree/AggregatingMergeTree tables, optimize queries with materialized views, and batch-insert data.'

Trim the broad 'data engineering best practices for high-performance analytical workloads' tail to reduce overlap with generic analytics skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('ClickHouse database patterns, query optimization, analytics') but phrases like 'patterns' and 'best practices' are generic rather than concrete actions such as 'create MergeTree tables' or 'optimize queries with materialized views'. Not 4 because it lacks the specific action verbs and only minor-gaps coverage of the anchor above; not 2 because it does name the domain with several capability areas.	3 / 5
Completeness	The 'what' is reasonably clear (ClickHouse patterns, optimization, analytics, data engineering), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines. Not 4 because the 'when' is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	'ClickHouse', 'query optimization', and 'analytics' are relevant keywords a user might say, but there are no synonyms, related tooling phrases, or context variations beyond the product name. Not 4 because coverage is limited to a handful of terms with several natural phrasings missing; not 2 because the terms present are domain-relevant rather than generic.	3 / 5
Distinctiveness Conflict Risk	'ClickHouse' pins a clear niche with minimal conflict risk against non-ClickHouse database skills, but the trailing 'analytics, and data engineering best practices for high-performance analytical workloads' broadens overlap with general analytics/data-engineering skills. Not 5 because of that broadened tail; not 3 because the explicit product name makes it mostly distinct.	4 / 5
	Total	13 / 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: sickn33/agentic-awesome-skills
Path: skills/cc-skill-clickhouse-io/SKILL.md
Commit: 7b534bc

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