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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

The content is a tight, highly actionable SQL-optimization workflow with a clear sequenced process and an explicit validation step. Its main weakness is progressive disclosure: bundled scripts and references exist but are never linked from the body, leaving supporting material orphaned.

Suggestions

Link the bundled helper scripts from the Instructions (e.g., point step 2 to scripts/explain_query.py and analysis to scripts/analyze_query.py) so supporting material is one level deep and clearly signaled.

Move the inline external documentation URLs in the Resources section into references/ and reference them, keeping the body as an overview that points to detail.

Surface the example_queries.sql asset noted in assets/README.md as a referenced testing fixture in the Examples or Prerequisites section.

Dimension	Reasoning	Score
Conciseness	The body is lean technical prose that assumes Claude's SQL competence and avoids explaining basic concepts (no 'what a JOIN is' filler); each instruction earns its place with domain-specific rationale. It is not level 2 because there is no concept-padding and the content could not be materially tightened without losing actionable detail.	3 / 3
Actionability	It provides concrete, executable guidance: specific SQL rewrites, copy-paste-ready before/after examples, concrete commands ('EXPLAIN ANALYZE', 'SET enable_seqscan = off', 'ANALYZE'), and precise index recommendations like '(customer_id, created_at DESC)'. It is not level 2 because the examples are complete and executable rather than pseudocode.	3 / 3
Workflow Clarity	A clear 10-step numbered sequence includes an explicit validation checkpoint (step 9: test with EXPLAIN ANALYZE and compare) plus a documentation step, with error-recovery guidance in the Error Handling table. It is not level 2 because an explicit validation step is present and the guideline's cap-at-2 (missing validation in risky ops) does not apply.	3 / 3
Progressive Disclosure	The body has well-organized internal sections, but bundled files (scripts/analyze_query.py, scripts/explain_query.py, references/, assets/) are never referenced or linked from the body, so helper content that exists separately is not navigated to. It is above level 1 because the body is sectioned rather than a monolithic wall of text, but below level 3 because the bundle is not signaled and one-level-deep references are absent.	2 / 3
	Total	11 / 12 Passed

Description

90%

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 has strong trigger-term coverage and a clear, distinct niche with explicit when-guidance, but its 'what' statement relies on vague fluff ('comprehensive guidance and automation') rather than concrete capability actions. Tightening the capability clause with specific actions would raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('query optimization', 'query performance analysis') and several actions, but the concrete capabilities only appear as trigger phrases ('optimize queries', 'analyze performance', 'improve query speed') while the capability statement is padded with vague fluff ('comprehensive guidance and automation'). It is above level 1 because it does name a domain and multiple actions, but below level 3 because it does not list multiple specific concrete capability actions.	2 / 3
Completeness	It explicitly answers both 'what' (query performance analysis / optimization) and 'when' via an explicit trigger clause ('Execute use when...', 'Trigger with phrases like...'). It is not level 2 because the explicit 'Use when'-style trigger clause is present, which the guidelines require for level 3.	3 / 3
Trigger Term Quality	It includes natural phrases a user would actually say — 'optimize queries', 'analyze performance', and 'improve query speed' — giving good coverage of common variations. It is not level 2 because the keyword coverage is broad and natural rather than partial.	3 / 3
Distinctiveness Conflict Risk	SQL query optimization is a clear niche with distinct triggers ('optimize queries', 'improve query speed') unlikely to fire for unrelated skills. It is not level 2 because the scope and triggers are specific enough to avoid meaningful overlap.	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
Commit: 3022dd3

Reviewed: 2 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.