CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnose-clickhouse-errors

Diagnose ClickHouse runtime query failures when the user wants database-level cause and fix guidance from an error or numeric error code, not source-code root cause analysis.

72

Quality

90%

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

93%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 tight, highly actionable overview that delegates per-error detail to one-level-deep reference files and gives exact tool-invocation and response-format specifications. Its only weakness is a lighter error-recovery/feedback loop in the workflow, which keeps workflow clarity just below full marks.

DimensionReasoningScore

Conciseness

The body is lean and action-first with no concept padding about ClickHouse basics; directives like 'Keep answers brief and action-first. Do not repeat the raw error verbatim.' show it assumes Claude's competence, and every line earns its place.

5 / 5

Actionability

Provides fully executable guidance: an exact ask_user_question payload (header + options JSON), a concrete skill_resource path pattern, and a precise three-section response structure with localization rules — copy-paste ready across common cases.

5 / 5

Workflow Clarity

Six steps are clearly sequenced with an explicit gating check (step 1) and a missing-code fallback (step 3), but error-recovery/feedback loops are only lightly specified (step 6's 'returns nothing' branch), leaving minor validation gaps versus the explicit validate-fix-retry anchor at 5.

4 / 5

Progressive Disclosure

The SKILL.md is a concise overview that delegates per-code detail one level deep to references/<code>.md (verified to exist: 42, 47, 60, 115, 342), with a clearly signaled example path and well-organized sections (When Not To Use, Workflow, Response format) for easy navigation.

5 / 5

Total

19

/

20

Passed

Description

87%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 is specific, action-oriented, and clearly scopes both the task and the trigger conditions, with explicit boundary guidance against source-code analysis. It is concise without padding and reads as a strong, low-conflict trigger.

DimensionReasoningScore

Specificity

Names the ClickHouse domain and several concrete actions (database-level cause, fix guidance, intake from an error or numeric error code), with only minor coverage gaps; sits above the '1-2 concrete actions' anchor but below the fully comprehensive list at 5.

4 / 5

Completeness

Explicitly answers both 'what' (diagnose ClickHouse runtime query failures; give cause and fix guidance) and 'when' (when the user wants database-level cause and fix guidance from an error or numeric error code) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('ClickHouse', 'runtime query failures', 'error code') a user would say, though a few common variations ('ClickHouse error', 'query failed') are absent, keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (database-level diagnosis from error codes) explicitly contrasted against source-code root cause analysis, giving minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

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.