cc-skill-clickhouse-io
ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill cc-skill-clickhouse-io65
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 1.27xAgent success when using this skill
Validation for skill structure
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 a clear technology domain (ClickHouse) but lacks explicit trigger guidance and specific concrete actions. It reads more like a topic list than actionable skill selection criteria. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill over other database-related skills.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when working with ClickHouse databases, columnar analytics, OLAP queries, or MergeTree table optimization'
Replace broad categories with specific actions like 'Write efficient aggregation queries, configure MergeTree engines, optimize materialized views, design partition strategies'
Include common user terms and variations like 'CH', 'columnar database', 'OLAP', 'analytical database', '.clickhouse' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ClickHouse database) and mentions some actions like 'query optimization, analytics, and data engineering best practices' but these are broad categories rather than concrete specific actions like 'write aggregation queries' or 'configure table engines'. | 2 / 3 |
Completeness | Describes what the skill covers (ClickHouse patterns and optimization) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'ClickHouse', 'query optimization', 'analytics', and 'data engineering' which are relevant keywords, but misses common variations users might say like 'OLAP', 'columnar database', 'MergeTree', 'analytical queries', or 'CH'. | 2 / 3 |
Distinctiveness Conflict Risk | 'ClickHouse' is a specific technology which helps distinctiveness, but 'query optimization', 'analytics', and 'data engineering best practices' are generic enough to potentially overlap with other database or analytics skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable ClickHouse patterns with excellent executable code examples and clear good/bad comparisons. However, it's verbose in places (explaining what ClickHouse is), lacks validation checkpoints for data operations, and would benefit from splitting into a concise overview with linked reference files for advanced topics.
Suggestions
Remove the Overview section explaining what ClickHouse is and its key features - Claude already knows this
Add validation steps to the ETL and CDC patterns (e.g., verify row counts, check for errors before proceeding)
Split into SKILL.md (quick start + best practices) with links to separate files: TABLES.md, QUERIES.md, PIPELINES.md, ANALYTICS.md
Replace the generic 'When to Use' section with specific trigger conditions (e.g., 'Use when: building analytics dashboards, processing >1M rows, need sub-second aggregations')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview section explains what ClickHouse is and lists basic features that Claude already knows. However, the code examples and patterns themselves are efficient and practical without excessive explanation. | 2 / 3 |
Actionability | Provides fully executable SQL and TypeScript code examples throughout. The good/bad pattern comparisons with ✅/❌ markers make guidance immediately actionable and copy-paste ready. | 3 / 3 |
Workflow Clarity | The ETL pattern shows a clear sequence, but most sections present isolated patterns without validation checkpoints. The bulk insert vs individual insert comparison is helpful but lacks error handling or verification steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a monolithic document (~400 lines) that could benefit from splitting advanced topics (CDC, materialized views, analytics queries) into separate reference files. | 2 / 3 |
Total | 9 / 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 | |
- 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.