CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clickhouse-best-practices

MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.

64

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/clickhouse-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-organized router/index skill body with concrete procedures, checklists, and a strong output format, and no token waste on concepts Claude already knows. Its two real defects are the broken disclosure layer — all 20+ referenced rule files and AGENTS.md are missing from the bundle — and local flaws like the dangling 'For Formal Reviews' intro and duplicated rule listings between the priority table and Quick Reference.

Suggestions

Ship the `rules/` directory (all 20+ referenced rule files) and `AGENTS.md` in the bundle, or inline the rules' content — as delivered, every 'Read these rule files' instruction fails because the files do not exist.

Fix the 'For Formal Reviews' section, which ends with a colon ('When performing a formal review of schemas, queries, or data ingestion:') and then drops into unrelated content; either complete its list or remove the section.

Collapse the duplication between 'Rule Categories by Priority' and 'Quick Reference' — both enumerate the same 28 rules with one-line summaries — into a single table (e.g. add the one-line description and impact to the priority table).

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — it never explains what ClickHouse or columnar storage is and gets straight to procedures — but the 'Rule Categories by Priority' table and the 'Quick Reference' section both enumerate the same 28 rules with one-line summaries, a clear duplication that could be trimmed. Not anchor 5 because of that redundancy and the low-value 'Rule File Structure' section.

4 / 5

Actionability

Guidance is highly concrete — ordered rule-file reading lists per review type, specific checklists, a copy-paste output-format template, and a citation pattern ('Per `rule-name`...') — which would merit anchor 5. However, every referenced path (20+ `rules/*.md` files and `AGENTS.md`) is absent from the bundle, so the primary instruction 'read these rule files' is not actually executable as shipped.

4 / 5

Workflow Clarity

A clear numbered priority sequence (check rules → apply and cite → fall back to knowledge → web search → always cite source) plus per-review-type procedures and an output format whose 'Rules Checked / Compliant / Violation' structure functions as a verification report. Docked from 5 for the dangling 'For Formal Reviews' section that ends in a colon with no following list, leaving that workflow entry point incoherent.

4 / 5

Progressive Disclosure

As written, the design is good — one-level-deep references to `rules/` files, clearly signaled and grouped by review type — but scored against the actual bundle structure, no `rules/` directory or `AGENTS.md` exists at all, so every reference is broken and the detailed content the SKILL.md is supposed to disclose is missing. The structure is better organized than anchor 3's example, but the broken references prevent the anchor 4-5 navigation experience.

3 / 5

Total

15

/

20

Passed

Description

78%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.

A strong, directive description with an explicit trigger clause, concrete actions, third-person voice, and a clearly distinct ClickHouse niche. Its main weaknesses are an under-specified 'what' (the 28 rules' coverage areas are never named) and a 'when' clause restricted to 'reviewing' that misses the design, optimization, and ingestion triggers the body targets.

Suggestions

Name the capability areas in the 'what' clause, e.g. 'Contains 28 rules covering schema design, query optimization, and data ingestion that MUST be checked...'

Broaden the 'when' clause beyond 'reviewing' to include the body's own triggers: 'MUST USE when designing or reviewing ClickHouse schemas, optimizing or troubleshooting queries, or planning data ingestion'.

Add one or two natural trigger synonyms users actually say (e.g. 'slow query', 'MergeTree', 'ORDER BY') to raise trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "reviewing ClickHouse schemas, queries, or configurations", "read relevant rule files", "cite specific rules in responses" — though it falls short of anchor 5 because it never states what the 28 rules cover (schema design, query optimization, data ingestion).

4 / 5

Completeness

Both parts are explicit: "MUST USE when reviewing ClickHouse schemas, queries, or configurations" answers when, and "Contains 28 rules that MUST be checked before providing recommendations" answers what. The 'when' clause is narrower than anchor 5 — it only fires on 'reviewing' and misses design, optimization, and troubleshooting triggers that the body itself lists under 'When to Apply'.

4 / 5

Trigger Term Quality

"ClickHouse", "schemas", "queries", "configurations", and "reviewing" are terms users would naturally say, matching anchor 4's good-but-incomplete coverage; common variations like "optimize", "slow query", "MergeTree", or "table design" are missing, so it is not the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"ClickHouse schemas, queries, or configurations" names a precise niche with distinct triggers; no other plausible skill would collide with it, matching anchor 5's clear-niche example.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

MapleTechLabs/maple

Path

.agents/skills/clickhouse-best-practices/SKILL.md

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.