cc-skill-clickhouse-io

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

Quality

31%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/cc-skill-clickhouse-io/SKILL.md

Quality

Discovery

32%

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 identifies ClickHouse as the target domain which provides some distinctiveness, but it reads more like a topic list than an actionable skill description. It lacks specific concrete actions, misses a 'Use when...' clause entirely, and uses broad terms that could overlap with other database skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ClickHouse queries, MergeTree engine configuration, columnar storage optimization, or analytical database design.'

Replace broad categories with specific concrete actions, e.g., 'Writes and optimizes ClickHouse SQL queries, configures MergeTree table engines, designs materialized views, and tunes aggregation performance.'

Include more natural trigger terms users would say, such as 'OLAP', 'columnar database', 'MergeTree', 'ReplacingMergeTree', 'ClickHouse SQL', or 'analytical queries'.

Dimension	Reasoning	Score
Specificity	Names the domain (ClickHouse database) and some general action areas (query optimization, analytics, data engineering), but these are broad categories rather than concrete specific actions like 'write materialized views' or 'optimize GROUP BY queries'.	2 / 3
Completeness	Describes what it covers at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also fairly weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes 'ClickHouse' which is a strong natural trigger term, plus 'query optimization' and 'analytics' which users might say. However, it misses common variations like 'columnar database', 'OLAP', 'MergeTree', 'aggregating tables', or specific ClickHouse file extensions/tools.	2 / 3
Distinctiveness Conflict Risk	'ClickHouse' is a distinctive trigger that separates it from generic database skills, but terms like 'query optimization', 'analytics', and 'data engineering best practices' are broad enough to overlap with general SQL, PostgreSQL, or other database-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

29%

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

This skill is essentially a ClickHouse reference guide dumped into a single file. While it provides excellent, executable code examples across many topics (strong actionability), it suffers from being overly verbose with explanations Claude doesn't need, lacks any workflow sequencing or validation steps, and presents everything as a monolithic document rather than using progressive disclosure to organize the extensive content.

Suggestions

Remove the overview section explaining what ClickHouse is and its key features—Claude already knows this. Cut the boilerplate 'When to Use' and 'Limitations' sections.

Split content into separate files (e.g., TABLE_DESIGN.md, QUERY_PATTERNS.md, DATA_PIPELINES.md, MONITORING.md) and make SKILL.md a concise overview with clear references to each.

Add validation checkpoints to the ETL and CDC workflows—e.g., verify row counts after bulk insert, handle insertion failures, add retry logic for streaming inserts.

Add a decision tree or quick-reference table at the top to help Claude choose the right engine type (MergeTree vs ReplacingMergeTree vs AggregatingMergeTree) based on use case, rather than listing all three sequentially.

Dimension	Reasoning	Score
Conciseness	The overview section explains what ClickHouse is, lists basic features (column-oriented storage, parallel execution, etc.) that Claude already knows. The document is extremely long (~400 lines) and covers many topics at surface level rather than providing focused, high-value guidance. The 'Best Practices' section lists generic advice Claude would already know. The boilerplate 'When to Use' and 'Limitations' sections add no value.	1 / 3
Actionability	The skill provides extensive executable SQL and TypeScript code examples that are copy-paste ready. Table creation DDL, query patterns, insertion patterns, materialized views, and monitoring queries are all concrete and specific with good/bad pattern annotations.	3 / 3
Workflow Clarity	There is no clear multi-step workflow with sequencing or validation checkpoints. The ETL pattern shows numbered steps but lacks error handling, validation, or feedback loops. The data insertion patterns don't mention verifying data was inserted correctly. For operations like CDC and bulk inserts that could fail silently, there are no validation or retry mechanisms.	1 / 3
Progressive Disclosure	The entire skill is a monolithic wall of content with no references to external files. All topics—table design, query optimization, insertion patterns, materialized views, monitoring, analytics queries, ETL, CDC, and best practices—are crammed into a single file with no navigation structure or content splitting.	1 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 1930a07

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