agent-clickhouse-io
ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
41
27%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/agent-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 a clear technology domain (ClickHouse) but lacks explicit trigger guidance and specific concrete actions. It reads more like a topic list than actionable skill guidance, and the absence of a 'Use when...' clause significantly weakens its utility for skill selection among many options.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'ClickHouse', 'columnar database', 'OLAP queries', 'MergeTree engine', or 'analytical workloads'.
Replace broad categories with specific concrete actions such as 'design table schemas with appropriate MergeTree engines', 'optimize aggregation queries', 'configure materialized views'.
Include common user phrasings and file/technology markers like '.clickhouse', 'CH queries', 'columnar storage', or 'real-time analytics'.
| 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
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as an index/table of contents with minimal actionable content in the main file. The overview explains concepts Claude already knows, and the 21 sub-skill links lack logical grouping or clear organization. The inconsistent naming of sub-skills (some numbered, some not) suggests structural issues that would make navigation difficult.
Suggestions
Add at least one quick-start code example showing a basic ClickHouse query pattern directly in the main skill file
Group the 21 sub-skills into logical categories (e.g., 'Table Engines', 'Query Patterns', 'Data Ingestion', 'Analytics', 'Best Practices') with brief descriptions
Fix inconsistent sub-skill naming - items 17-21 have numbered prefixes while others don't
Remove the generic ClickHouse overview that explains column-oriented storage and basic features - Claude already knows this
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview section explains what ClickHouse is and lists basic features that Claude already knows. However, the file is relatively short and the bulk is navigation links, which is appropriate. | 2 / 3 |
Actionability | The skill contains no executable code, commands, or concrete examples. It's entirely a table of contents with links to sub-skills, providing no actionable guidance in the main file itself. | 1 / 3 |
Workflow Clarity | There is no workflow, sequence, or process described. The numbered sub-skills appear to be topics rather than steps, and items 17-21 have inconsistent naming suggesting organizational issues. | 1 / 3 |
Progressive Disclosure | The file does use sub-skills for detailed content, but the organization is poor - 21 sub-skills with no grouping or categorization, inconsistent naming (items 17-21 have numbered prefixes), and no clear navigation structure beyond a flat list. | 2 / 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
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.