CtrlK
BlogDocsLog inGet started
Tessl Logo

clickhouse-system-queries

Query ClickHouse system tables to inspect query logs, monitor cluster health, check replication status, and analyze slow queries. Use when the user mentions "system tables", "query_log", "ClickHouse monitoring", "cluster status", "slow queries", or asks to diagnose ClickHouse operational issues.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, actionable skill body with good structure and a real one-level reference. Adding explicit error-recovery guidance and a broader set of copy-paste query templates would push it higher.

Suggestions

Add an explicit error-handling/feedback step to the workflow (e.g., what to do when a query returns no rows or a tool errors) to strengthen the validation checkpoint.

Include a few more copy-paste-ready query templates covering common cases (replication status, slow-query ranking) to round out actionability.

Tighten the ProfileEvents section by collapsing the map-vs-flattened explanation into a single compact rule plus one example.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence and avoids explaining what ClickHouse is; the ProfileEvents map-vs-flattened aside and the illustrative SQL earn their tokens, though a few lines could still be trimmed, so not 5.

4 / 5

Actionability

Provides executable SQL examples and concrete tool-selection rules (search_query_log vs execute_sql, default LIMIT 50); not 5 because examples are illustrative rather than covering the full range of common cases.

4 / 5

Workflow Clarity

Clear four-step sequence with a reference-load checkpoint and explicit guardrails; no explicit error-recovery feedback loop, but the skill is read-only inspection (not destructive/batch), so the 3-cap does not apply and 5 is withheld only for the missing recovery loop.

4 / 5

Progressive Disclosure

Concise overview body pointing to a single one-level-deep, clearly signaled, real reference (references/system-query-log.md), with content appropriately split — matching the top anchor.

5 / 5

Total

17

/

20

Passed

Description

92%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 well-crafted description with concrete capabilities, explicit trigger guidance, and a clear niche. Minor room to broaden natural trigger synonyms.

DimensionReasoningScore

Specificity

Lists four concrete actions — "inspect query logs", "monitor cluster health", "check replication status", "analyze slow queries" — matching the comprehensive-coverage anchor; not 4 because coverage is broad rather than having minor gaps.

5 / 5

Completeness

Explicitly states what it does ("Query ClickHouse system tables to...") and when to use it ("Use when the user mentions...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases like "system tables", "query_log", "ClickHouse monitoring", "cluster status", and "slow queries" give good coverage, but a few natural synonyms (e.g. "replication lag", "query performance") are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

Narrow ClickHouse system-table operational niche with distinct triggers and minimal overlap risk; clearly distinguishable from general SQL skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
FrankChen021/datastoria
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.