clickhouse-io
ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
39
37%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 the domain (ClickHouse) and broadly names capability areas but lacks specific concrete actions and entirely omits explicit trigger guidance ('Use when...'). The vague terms like 'patterns' and 'best practices' reduce its effectiveness for skill selection, and the broad analytics/data engineering language could cause overlap with other database-related skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ClickHouse queries, table engines, MergeTree optimization, or analytical database design.'
Replace vague terms like 'patterns' and 'best practices' with specific concrete actions such as 'design MergeTree table schemas, write optimized aggregation queries, configure materialized views, troubleshoot query performance.'
Include additional natural trigger terms users might say, such as 'columnar database', 'OLAP', 'MergeTree', 'ReplacingMergeTree', 'ClickHouse SQL', or '.ch' to improve keyword coverage and distinctiveness.
| 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'. The terms 'patterns' and 'best practices' are somewhat vague. | 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 the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also fairly weak/vague, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'ClickHouse', 'query optimization', 'analytics', and 'data engineering', which users might naturally say. However, it's missing common variations and specific terms like 'columnar database', 'MergeTree', 'materialized views', 'OLAP', or file format mentions that users working with ClickHouse would reference. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'ClickHouse' specifically provides some distinctiveness from generic database or SQL skills. However, terms like 'analytics', 'data engineering best practices', and 'query optimization' are broad enough to overlap with skills for other analytical databases (e.g., BigQuery, Snowflake, DuckDB). | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent, executable SQL and TypeScript examples covering a wide range of ClickHouse patterns. However, it is far too verbose — it reads like a comprehensive reference manual rather than a focused skill, explaining concepts Claude already knows and inlining content that should be split across multiple files. The lack of validation checkpoints in multi-step workflows and the monolithic structure significantly reduce its effectiveness as a skill.
Suggestions
Reduce the body to a concise overview (~50-80 lines) covering the most critical patterns (MergeTree schema, bulk inserts, materialized views) and move detailed query examples, analytics patterns, and pipeline patterns into separate referenced files like QUERIES.md, PIPELINES.md, MONITORING.md.
Remove the 'Overview' section entirely — Claude knows what ClickHouse is and doesn't need a feature list.
Add explicit validation steps to multi-step workflows: verify table creation with DESCRIBE TABLE, validate bulk insert row counts with SELECT count(), and add error handling to the ETL and CDC patterns.
Trim the 'Best Practices' section to a compact checklist without explanatory text, as most items (e.g., 'avoid SELECT *', 'batch inserts') are well-known patterns Claude already understands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines. It explains what ClickHouse is ('column-oriented DBMS for OLAP'), lists key features Claude already knows, includes an unnecessary 'Overview' section, and provides extensive example queries that could be condensed. The 'Best Practices' section restates common knowledge. Much of this content is reference-manual-style padding. | 1 / 3 |
Actionability | The skill provides fully executable SQL and TypeScript code throughout — CREATE TABLE statements, query examples with concrete column names, bulk insert patterns, materialized view definitions, and monitoring queries. All examples are copy-paste ready with realistic schemas. | 3 / 3 |
Workflow Clarity | The ETL pipeline section has a numbered sequence (extract, transform, load), and the data insertion section contrasts good vs bad patterns. However, there are no validation checkpoints — no steps to verify table creation succeeded, no validation after bulk inserts, no error handling in the CDC pattern, and no feedback loops for any of the multi-step processes. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of content with no references to external files. All content — table design, query optimization, insertion patterns, materialized views, monitoring, analytics queries, pipeline patterns, and best practices — is inlined in a single massive file with no structure for progressive discovery. | 1 / 3 |
Total | 7 / 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
- affaan-m/everything-claude-code
- Commit
64cd1ba
- 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.