sql-optimization-patterns

Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.

0.98x

Quality

—

Does it follow best practices?

Impact

93%

0.98x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with extensive executable examples, but it is verbose and organized as a monolithic reference rather than a lean overview pointing to detail files. The referenced bundle files do not exist, and no validation checkpoints frame the optimization workflow.

Suggestions

Add a short sequenced workflow with validation checkpoints (e.g., 1. EXPLAIN ANALYZE the query, 2. identify seq scans / high-cost nodes, 3. add targeted index, 4. re-run EXPLAIN ANALYZE to confirm improvement) instead of only cataloguing patterns.

Trim generic filler sentences ('Indexes are the most powerful optimization tool.', 'Understanding EXPLAIN output is fundamental to optimization.') and move Postgres/MySQL-specific deep dives into the referenced files to slim the inline body.

Create the referenced bundle files (references/postgres-optimization-guide.md, references/mysql-optimization-guide.md, assets/*, scripts/*) or remove the dangling Resource links so progressive disclosure points to real material.

Dimension	Reasoning	Score
Conciseness	The ~510-line body is mostly efficient code, but includes redundant filler sentences like 'Indexes are the most powerful optimization tool.' and 'Understanding EXPLAIN output is fundamental to optimization.' that explain what Claude already knows, so it is not the lean level-3 anchor and not vague enough for level 1.	2 / 3
Actionability	Abundant copy-paste-ready executable SQL and Python with explicit Bad/Good/Better variants, matching the fully-executable anchor rather than pseudocode or vague direction.	3 / 3
Workflow Clarity	Patterns are catalogued but there is no sequenced optimization workflow with validation checkpoints (e.g., EXPLAIN -> diagnose -> index -> re-verify); per the rubric, database/batch operations lacking validate->fix->retry feedback loops cap this at 2 rather than 3.	2 / 3
Progressive Disclosure	The Resources section signals one-level-deep references, but none of the referenced files (references/, assets/, scripts/) actually exist, and Postgres/MySQL-specific material that should be split out is inlined into a monolithic body — better organized than a score-1 wall but not the clean level-3 split.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 concise, specific, and clearly answers both what the skill does and when to use it with natural trigger terms. Minor fluff ('dramatically improve', 'eliminate slow queries') does not detract from its strong specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'SQL query optimization, indexing strategies, and EXPLAIN analysis' — matching the 'lists multiple specific concrete actions' anchor; not the level below which only names a domain and some actions.	3 / 3
Completeness	Explicitly answers both what ('Master SQL query optimization, indexing strategies, and EXPLAIN analysis...') and when ('Use when debugging slow queries, designing database schemas, or optimizing application performance.'), satisfying the explicit-trigger anchor.	3 / 3
Trigger Term Quality	Triggers like 'debugging slow queries, designing database schemas, or optimizing application performance' are natural phrasings a user would actually say, giving good coverage rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	SQL query optimization is a clear niche with distinct triggers unlikely to fire for unrelated skills; not merely 'somewhat specific but could overlap'.	3 / 3
	Total	12 / 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
skill_md_line_count	SKILL.md is long (510 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Commit: e9f9b67

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