optimizing-sql-queries

Execute use when you need to work with query optimization. This skill provides query performance analysis with comprehensive guidance and automation. Trigger with phrases like "optimize queries", "analyze performance", or "improve query speed".

Quality

91%

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

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is dense, actionable, and well-sequenced with validation, but it ignores its own bundled scripts/references entirely, leaving the progressive-disclosure structure disconnected from the workflow.

Suggestions

Wire the bundled scripts into the workflow, e.g. step 2 'Run python scripts/explain_query.py' to capture the plan and step 1 'Use scripts/analyze_query.py' to detect anti-patterns.

Add an explicit pointer to the scripts/references bundles (e.g. a 'Bundle' or 'Tools' section) so Claude knows where the automation lives instead of describing everything inline.

Dimension	Reasoning	Score
Conciseness	The body is lean and technical, assuming Claude's SQL competence without explaining basic concepts; parenthetical asides are brief justifications rather than padding, so every section earns its place.	3 / 3
Actionability	Guidance is concrete and executable: specific SQL rewrites (e.g. ROW_NUMBER() OVER (PARTITION BY ...), EXISTS (SELECT 1 ...)), EXPLAIN ANALYZE commands, and worked before/after examples with measured timings.	3 / 3
Workflow Clarity	A clear 10-step sequence culminates in an explicit validation step (step 9: re-run EXPLAIN ANALYZE and compare metrics) plus an error-handling table giving feedback loops, appropriate for database operations.	3 / 3
Progressive Disclosure	The bundle provides scripts (analyze_query.py, explain_query.py) and references, but the body never signals or links to any of them — instructions are written as if the scripts do not exist — so the structure is present but not clearly navigated.	2 / 3
	Total	11 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 cleanly states a clear niche with natural trigger terms and an explicit Use-when clause, but pads the capability statement with 'comprehensive guidance and automation' buzzwords instead of concrete actions.

Suggestions

Replace 'comprehensive guidance and automation' with concrete actions, e.g. 'Rewrite slow SQL, analyze EXPLAIN plans, and recommend indexes for PostgreSQL and MySQL'.

Remove the meta phrase 'Execute use when' which reads awkwardly; keep the cleaner 'Use when you need to work with query optimization.'

Dimension	Reasoning	Score
Specificity	Names the domain ('query performance analysis') but pairs it with fluffy over-claims ('comprehensive guidance and automation') rather than listing multiple concrete actions; closer to 'Names domain and some actions' than the multi-action level-3 anchor.	2 / 3
Completeness	It answers both what ('query performance analysis') and when, with an explicit 'Use when you need to work with query optimization' clause plus concrete trigger phrases, matching the level-3 anchor.	3 / 3
Trigger Term Quality	The triggers 'optimize queries', 'analyze performance', and 'improve query speed' are natural phrases a user would actually say, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The query-optimization niche with its specific trigger phrases is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/database/sql-query-optimizer/skills/optimizing-sql-queries/SKILL.md
Commit: c4eafaf

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.