optimize-clickhouse-queries
Optimize slow queries, analyze SQL performance, and collect evidence for expensive workloads.
83
80%
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/optimize-clickhouse-queries/SKILL.mdQuality
Discovery
60%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 effectively communicates specific SQL performance-related capabilities with concrete actions. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill. Adding natural user terms and clarifying the 'when' would significantly improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause with trigger terms like 'slow query', 'query optimization', 'database performance', 'EXPLAIN plan', or 'query tuning'
Include common file/technology variations users might mention such as 'PostgreSQL', 'MySQL', 'execution plan', or 'index optimization'
Clarify 'expensive workloads' to be more SQL-specific, e.g., 'resource-intensive database queries' to reduce potential overlap with non-SQL optimization skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Optimize slow queries', 'analyze SQL performance', and 'collect evidence for expensive workloads'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with three specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance to indicate when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Contains relevant keywords like 'slow queries', 'SQL performance', and 'expensive workloads', but missing common variations users might say like 'query optimization', 'database performance', 'EXPLAIN', 'execution plan', or 'query tuning'. | 2 / 3 |
Distinctiveness Conflict Risk | Focuses on SQL performance which is somewhat specific, but could overlap with general database skills or code optimization skills. The term 'expensive workloads' is ambiguous and could apply to non-SQL contexts. | 2 / 3 |
Total | 9 / 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 excellent skill that demonstrates strong token efficiency while providing comprehensive, actionable guidance for SQL optimization workflows. The pre-flight routing logic, clear tool preferences, and explicit validation requirements make it highly effective. The evidence-driven approach with specific rules about when to use query_id vs SQL shows thoughtful design.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose and the content assumes Claude's competence with SQL and optimization concepts. | 3 / 3 |
Actionability | Provides concrete, specific guidance with exact tool names, parameter names, and clear decision criteria. The workflow steps are explicit about which tools to call and when, with specific examples like the UI trigger block. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit validation checkpoint (step 5: validate_sql). Pre-flight check provides unambiguous routing logic. The discovery-to-evidence-to-recommendation flow is well-sequenced with explicit feedback loops. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections that progress logically. References external skill and resource (clickhouse-system-queries, system-query-log.md) at one level deep with clear signaling for when to use them. | 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 | |
- 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.