diagnose-clickhouse-errors
Diagnose ClickHouse query failures when the user provides a numeric error code, symbolic error name such as UNKNOWN_SETTING, or raw DB::Exception text and wants a cause and fix.
93
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope (ClickHouse error diagnosis), specifies concrete inputs and outputs, and includes natural trigger terms that users would actually use when encountering ClickHouse errors. The description is concise yet comprehensive, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Diagnose ClickHouse query failures' with clear input types (numeric error code, symbolic error name, raw DB::Exception text) and outputs (cause and fix). | 3 / 3 |
Completeness | Clearly answers both what (diagnose ClickHouse query failures, provide cause and fix) and when (when user provides error code, symbolic error name, or DB::Exception text). The 'when the user provides...' clause serves as explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'ClickHouse', 'query failures', 'error code', 'UNKNOWN_SETTING', 'DB::Exception' - these are exactly what users encountering ClickHouse errors would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with ClickHouse-specific terminology (DB::Exception, UNKNOWN_SETTING) that would not conflict with generic database or error handling skills. Clear niche for ClickHouse error diagnosis specifically. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured index skill that efficiently delegates to reference files for specific error codes. The response format is clearly defined and the workflow is unambiguous. The main weakness is the lack of a concrete example showing what a complete Cause/Fix/Example response looks like, which would improve actionability.
Suggestions
Add one concrete example showing a complete Cause/Fix/Example response for a sample error to demonstrate the expected output format
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only essential information about response format, reference usage, and covered error codes without explaining what ClickHouse is or how error handling works in general. | 3 / 3 |
Actionability | Provides clear response format structure and references to follow, but lacks concrete examples of the expected output format or sample error-to-response mappings that would make it fully copy-paste actionable. | 2 / 3 |
Workflow Clarity | Clear workflow: receive error code → load matching reference with skill_resource → follow that file's workflow → output in Cause/Fix/Example format. Fallback for unsupported codes is also explicit. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview pointing to one-level-deep reference files for specific error codes. Navigation is clear with explicit file paths for each supported error. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- FrankChen021/datastoria
- Commit
68a8440
- 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.