cc-skill-clickhouse-io

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

1.27x

Quality

61%

Does it follow best practices?

Impact

97%

1.27x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/cc-skill-clickhouse-io/SKILL.md

The canonical home for this skill is cc-skill-clickhouse-io in sickn33/agentic-awesome-skills

Quality

Content

57%Weight 40%Scale 1-5

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

The body is a rich, actionable pattern catalog with concrete executable code across the main ClickHouse use cases, but it pads in concepts Claude already knows, lacks validation checkpoints on batch operations, and inlines everything with no progressive file structure.

Suggestions

Remove the 'Overview'/'Key Features' concept explanation and the vague 'When to Use' filler; assume Claude knows what ClickHouse and OLAP are.

Add explicit validation checkpoints to the batch/ETT/CDC flows (e.g. verify row counts after bulk insert, validate schema before load, retry on insert failure) to lift workflow clarity past the batch-operation cap of 3.

Split the long reference into one-level-deep files (e.g. ANALYTICS.md, PIPELINES.md, MONITORING.md) and point to them from a concise overview in SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The bulk is dense executable code, but it includes unnecessary explanation of concepts Claude already knows ('ClickHouse is a column-oriented database management system (DBMS) for online analytical processing (OLAP)...', the 'Key Features' list) plus a vague 'When to Use' filler line; it is mostly efficient but could be tightened, not verbose enough for the 2-anchor.	3 / 5
Actionability	Provides concrete, largely copy-paste-ready SQL and TypeScript across table design, queries, inserts, materialized views, monitoring, and pipelines; minor gaps (e.g. undefined `clickhouse` context in stream/ETL snippets) keep it just below the fully-executable 5-anchor.	4 / 5
Workflow Clarity	The ETL pattern shows a rough sequence (Extract, Transform, Load) but the batch insert and CDC operations include no validation/verification checkpoints; per the rubric, batch operations without validation cap workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the document is a ~430-line monolith with clear section headers but everything inlined; content such as analytics queries, pipeline patterns, and monitoring could live in separate referenced files, placing it above the minimally-structured 2-anchor but below well-split 4-anchor.	3 / 5
	Total	13 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 clearly names the ClickHouse domain and several specific capability areas with good natural trigger terms, but it omits any explicit 'Use when...' guidance, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when working with ClickHouse, optimizing analytical queries, or building data pipelines for OLAP workloads.'

Include a few natural synonyms/trigger variants such as 'OLAP', 'columnar database', or 'real-time analytics' to broaden keyword coverage toward the 5-anchor.

Lead with concrete verb-based actions (e.g. 'Design MergeTree tables, optimize analytical queries, build materialized views') to lift specificity from capability areas to discrete actions.

Dimension	Reasoning	Score
Specificity	Lists several specific capability areas tied to ClickHouse — 'query optimization, analytics, and data engineering best practices' — with only minor gaps, sitting noticeably above the 3-anchor (which expects just 1-2 concrete actions).	4 / 5
Completeness	Has a clear 'what' but no explicit 'when'/'Use when...' trigger clause; per the rubric a missing 'Use when' clause caps completeness at 3, and it is not as vague as the 2-anchor.	3 / 5
Trigger Term Quality	Includes natural user-facing terms ('ClickHouse', 'query optimization', 'analytics', 'data engineering') with good coverage; a few natural synonyms (e.g. 'OLAP', 'columnar') are missing, so it does not reach comprehensive 5-anchor coverage.	4 / 5
Distinctiveness Conflict Risk	ClickHouse is a specific tool giving it a clear niche with minimal conflict risk, but it retains minor overlap with general database/analytics skills rather than the fully distinct 5-anchor.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/cc-skill-clickhouse-io/SKILL.md
Commit: 57c135b

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