clickhouse-io
ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
55
31%
Does it follow best practices?
Impact
100%
1.21xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/clickhouse-io/SKILL.mdQuality
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 and lists broad capability areas, but lacks specific concrete actions and has no explicit 'Use when...' trigger clause. The generic terms like 'analytics' and 'data engineering best practices' could easily overlap with other database or data skills, reducing its effectiveness for skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ClickHouse, columnar databases, OLAP queries, MergeTree engines, or analytical data pipelines.'
List specific concrete actions such as 'design MergeTree table schemas, write materialized views, optimize GROUP BY and JOIN queries, configure partitioning and sharding'.
Include natural trigger term variations users might say: 'ClickHouse', 'CH', 'columnar', 'OLAP', 'MergeTree', 'ReplacingMergeTree', '.clickhouse' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ClickHouse database) and some general action areas (query optimization, analytics, data engineering best practices), but doesn't list specific concrete actions like 'write MergeTree table definitions' or 'optimize GROUP BY queries'. | 2 / 3 |
Completeness | Describes what the skill 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 rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also fairly weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes 'ClickHouse', 'query optimization', 'analytics', and 'data engineering' which are relevant keywords, but misses common user variations like 'columnar database', 'OLAP', 'MergeTree', 'materialized views', or 'analytical queries'. | 2 / 3 |
Distinctiveness Conflict Risk | 'ClickHouse' is a distinct technology that provides some niche specificity, but terms like 'query optimization', 'analytics', and 'data engineering best practices' are broad enough to overlap with general SQL or other database 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.
The skill excels at providing concrete, executable code examples across many ClickHouse use cases, but suffers from being a massive monolithic document that explains concepts Claude already knows (what ClickHouse is, column-oriented storage). It lacks any workflow sequencing or validation checkpoints for operations like schema changes or data migrations, and would benefit greatly from splitting into focused sub-files with a concise overview.
Suggestions
Remove the Overview section explaining what ClickHouse is and its key features — Claude already knows this. Cut the 'When to Activate' list or reduce to 1-2 lines.
Split into sub-files: move common analytics queries (retention, funnel, cohort) to ANALYTICS_QUERIES.md, pipeline patterns to PIPELINES.md, and monitoring to MONITORING.md, keeping SKILL.md as a concise overview with references.
Add explicit workflow sequences with validation for critical operations like schema migrations, bulk data loads, and materialized view creation (e.g., verify row counts after insert, validate materialized view output matches expected aggregation).
Remove duplicate materialized view query examples (shown in both AggregatingMergeTree and Materialized Views sections) and consolidate the best practices into the relevant sections rather than a separate list.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview section explains what ClickHouse is and lists basic features (column-oriented storage, parallel execution, etc.) that Claude already knows. The 'When to Activate' section is verbose. The document is ~350 lines with significant redundancy (e.g., querying materialized views shown twice with near-identical SQL). Many patterns are generic analytics queries (retention, funnel, cohort) that don't add ClickHouse-specific value beyond standard SQL. | 1 / 3 |
Actionability | The skill provides fully executable SQL and TypeScript code throughout — CREATE TABLE statements, INSERT patterns, materialized view definitions, monitoring queries, and ETL pipelines are all copy-paste ready with concrete examples and good/bad pattern annotations. | 3 / 3 |
Workflow Clarity | There are no sequenced multi-step workflows with validation checkpoints. The ETL pattern is a simple code snippet without error handling or validation. Schema changes, data migrations, and bulk operations lack any verification steps or feedback loops. The best practices section is a bullet list without workflow structure. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of content (~350+ lines) with no references to external files. Table design, query optimization, insertion patterns, materialized views, monitoring, analytics queries, pipeline patterns, and best practices are all inlined. Content like common analytics queries and pipeline patterns could easily be split into separate reference files. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%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
- ysyecust/everything-claude-code
- Commit
79cc4e3
- Reviewed
Table of Contents
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.