optimize-clickhouse-sql

Optimize slow queries, analyze SQL performance, and collect evidence for expensive workloads.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/optimize-clickhouse-sql/SKILL.md

Quality

Content

75%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 content is well-structured, lean, and gives concrete tool-level guidance with a clear sequenced workflow and validation checkpoint. Closing the validation feedback loop and removing the duplicated query_id rule would push it higher.

Suggestions

Add an explicit validation feedback loop: if validate_sql fails, fix the SQL and re-validate before recommending, which would lift workflow_clarity.

Consolidate the two near-identical query_id-preference rules in the Rules section into one to remove redundancy and tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's SQL competence with no concept over-explanation; it is not a 5 because the Rules section contains two near-duplicate query_id-preference bullets that could be consolidated.	4 / 5
Actionability	It names exact tools with concrete arguments (e.g. the full ask_user_question option JSON, collect_sql_optimization_evidence params, and index-type guidance like "bloom_filter for high-cardinality equality filters"), but full tool signatures are not all spelled out.	4 / 5
Workflow Clarity	The pre-flight branching and 5-step Workflow are clearly sequenced with an explicit validate_sql checkpoint; it falls short of 5 because there is no explicit fix-then-revalidate feedback loop when validation fails.	4 / 5
Progressive Disclosure	The body is a well-sectioned overview with one clearly-signaled one-level-deep reference (references/system-query-log.md via skill_resource); it is not a 5 because that reference belongs to an external skill's bundle rather than being split from this skill's own content.	4 / 5
	Total	16 / 20 Passed

Description

66%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 and uses natural trigger terms, but it omits any explicit "when to use" guidance, capping its completeness. Adding a trigger clause and naming ClickHouse would meaningfully raise the score.

Suggestions

Append an explicit "Use when..." clause with concrete trigger phrases, e.g. "Use when a user asks to optimize, speed up, or tune a slow ClickHouse/SQL query, or mentions query performance or expensive workloads."

Add natural synonyms users say ("tune", "speed up", "query plan", "EXPLAIN") to broaden trigger-term coverage.

Name ClickHouse explicitly to sharpen distinctiveness and reduce overlap with generic SQL analysis skills.

Dimension	Reasoning	Score
Specificity	"Optimize slow queries, analyze SQL performance, and collect evidence for expensive workloads" names three concrete actions, matching the anchor-4 example of several specific actions with minor gaps; not a 5 because coverage stops at three rather than a comprehensive list.	4 / 5
Completeness	The description gives a clear "what" but has no "Use when..." clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	"slow queries", "SQL performance", and "expensive workloads" are natural phrases users would say, giving good keyword coverage; not a 5 because common synonyms like "tune", "speed up", or "query plan" are absent.	4 / 5
Distinctiveness Conflict Risk	Query optimization is a clear niche with distinct triggers, but the absence of "ClickHouse" leaves minor overlap risk with generic SQL-tuning skills, so it is mostly distinct rather than fully.	4 / 5
	Total	15 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: FrankChen021/datastoria
Path: resources/skills/optimize-clickhouse-sql/SKILL.md
Commit: d0859a2

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.