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.
73
62%
Does it follow best practices?
Impact
93%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/sql-optimization-patterns/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with explicit 'Use when' triggers and good natural keyword coverage for database performance scenarios. Its main weaknesses are slightly vague capability descriptions (topic areas rather than concrete actions) and some marketing language ('dramatically improve', 'Master', 'eliminate') that adds fluff without improving skill selection. The description could also be more distinctive to avoid overlap with general database or schema design skills.
Suggestions
Replace topic-area language with concrete actions, e.g., 'Analyzes EXPLAIN plans, recommends index creation, rewrites slow SQL queries, identifies missing indexes and N+1 patterns'
Remove marketing fluff like 'Master', 'dramatically improve', and 'eliminate' which don't help Claude select the right skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SQL/database performance) and some actions (query optimization, indexing strategies, EXPLAIN analysis), but these are more like topic areas than concrete discrete actions. Compare to the level 3 example which lists specific verbs like 'extract', 'fill', 'merge'. | 2 / 3 |
Completeness | Clearly answers both what ('SQL query optimization, indexing strategies, and EXPLAIN analysis') and when ('Use when debugging slow queries, designing database schemas, or optimizing application performance') with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'slow queries', 'database performance', 'SQL query optimization', 'indexing', 'EXPLAIN', 'database schemas'. These cover common ways users describe database performance problems. | 3 / 3 |
Distinctiveness Conflict Risk | While SQL optimization is a reasonably specific niche, terms like 'database schemas' and 'application performance' could overlap with general database design skills or broader performance tuning skills. The 'dramatically improve' phrasing is marketing fluff rather than distinctive scoping. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive SQL optimization reference but fails as a SKILL.md by being far too verbose and monolithic. It explains many concepts Claude already knows (basic index types, what EXPLAIN metrics mean, why SELECT * is bad) and dumps everything into a single file rather than using progressive disclosure. The actionability is strong with excellent executable examples, but the lack of a systematic diagnostic workflow and missing bundle files significantly reduce its effectiveness.
Suggestions
Reduce the body to ~100 lines focusing on a systematic optimization workflow (diagnose with EXPLAIN → identify bottleneck → apply pattern → verify improvement) and move detailed patterns into referenced bundle files.
Remove explanations of concepts Claude already knows (what B-Tree indexes are, why SELECT * is bad, what Seq Scan means) and focus on decision-making heuristics and non-obvious gotchas.
Add explicit validation checkpoints: after each optimization step, instruct to re-run EXPLAIN ANALYZE and compare before/after metrics to verify the change actually helped.
Create the referenced bundle files (references/postgres-optimization-guide.md, assets/index-strategy-checklist.md, etc.) and move the detailed code examples into them, keeping only a concise overview in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines, covering broad SQL optimization topics that Claude already understands well. It explains basic concepts like what a Seq Scan is, what B-Tree indexes are, and includes extensive code examples for well-known patterns. Much of this is textbook knowledge that doesn't need to be spelled out for Claude. | 1 / 3 |
Actionability | The skill provides fully executable SQL and Python code examples throughout. Every pattern includes concrete before/after examples with copy-paste ready queries, index creation statements, and monitoring queries. | 3 / 3 |
Workflow Clarity | While individual optimization patterns are clearly presented with bad/good/better progressions, there's no overarching workflow for how to systematically diagnose and fix a slow query. Missing explicit validation checkpoints — e.g., after creating an index, re-run EXPLAIN ANALYZE to verify improvement. The 'When to Use' section lists triggers but doesn't sequence them into a diagnostic process. | 2 / 3 |
Progressive Disclosure | The file is a monolithic wall of text with everything inline. It references 7 bundle files (references/, assets/, scripts/) in the Resources section, but none of these files actually exist in the bundle. The content that could be split into separate reference files (e.g., index strategies, monitoring queries, advanced techniques) is all crammed into the main SKILL.md. | 1 / 3 |
Total | 7 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (510 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
99da384
- 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.