Diagnose ClickHouse cluster health and provide concrete remediation.
75
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./resources/skills/diagnose-clickhouse-clusters/SKILL.mdQuality
Discovery
40%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 identifies a clear niche (ClickHouse clusters) which provides good distinctiveness, but suffers from lack of explicit trigger guidance and insufficient specificity about what diagnostic/remediation actions are supported. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'ClickHouse issues', 'cluster problems', 'replication lag', 'query performance', 'node health'
List specific diagnostic actions such as 'check replication status', 'analyze slow queries', 'inspect disk space', 'review merge operations'
Include common user phrases like 'CH cluster', 'database is slow', 'nodes are down', 'queries timing out'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ClickHouse cluster health) and two general actions (diagnose, provide remediation), but lacks specific concrete actions like 'check replication lag', 'analyze query performance', or 'inspect disk usage'. | 2 / 3 |
Completeness | Describes what it does (diagnose and remediate) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'ClickHouse' and 'cluster health' which are relevant, but misses common variations users might say like 'CH', 'database issues', 'slow queries', 'replication problems', or 'node failures'. | 2 / 3 |
Distinctiveness Conflict Risk | ClickHouse is a specific database technology, making this clearly distinguishable from general database skills or other monitoring tools. Unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill that demonstrates excellent token efficiency while providing complete, actionable guidance. The severity thresholds table, output format specifications, and explicit rules create a clear contract for behavior. The skill appropriately constrains Claude's actions (no custom SQL, no assumptions) while providing concrete structure for outputs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what ClickHouse is or how clusters work. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides concrete tool calls, specific parameter values, exact output format with table structures, and clear severity thresholds. The workflow steps are explicit and executable. | 3 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing. The 'Rules' section enforces validation by requiring tool calls before any health assessment, creating a feedback loop that prevents premature conclusions. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Tools, Workflow, Thresholds, Output Format, Rules). Appropriately delegates visualization to another skill. Content is appropriately sized for a single file with no need for external references. | 3 / 3 |
Total | 12 / 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 | |
68a8440
Table of Contents
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.