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".
54
45%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/database/sql-query-optimizer/skills/optimizing-sql-queries/SKILL.mdQuality
Discovery
40%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 description suffers from vagueness in its capability claims, relying on buzzwords like 'comprehensive guidance and automation' rather than concrete actions. While it includes some trigger phrases, it lacks specificity about what kind of queries it handles and what concrete outputs or actions it performs. The awkward opening 'Execute use when' also suggests poor craftsmanship.
Suggestions
Replace vague capability claims with specific concrete actions, e.g., 'Analyzes SQL query execution plans, identifies missing indexes, rewrites slow joins, and suggests schema improvements'.
Specify the query type (SQL, NoSQL, etc.) and add more natural trigger term variations like 'slow query', 'execution plan', 'index optimization', 'database performance', '.sql'.
Restructure the 'when' clause to be more explicit, e.g., 'Use when the user asks about slow database queries, needs help reading execution plans, or wants to optimize SQL statements'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'query performance analysis with comprehensive guidance and automation' without listing any concrete actions. It doesn't specify what types of queries, what optimization techniques, or what outputs are produced. | 1 / 3 |
Completeness | It attempts to answer both 'what' and 'when' but the 'what' is extremely vague ('query performance analysis with comprehensive guidance and automation'), and the 'when' is present via trigger phrases but lacks specificity about the actual use cases. | 2 / 3 |
Trigger Term Quality | It includes some relevant trigger phrases like 'optimize queries', 'analyze performance', and 'improve query speed', but misses common variations like 'slow query', 'SQL optimization', 'execution plan', 'index', or 'database performance'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'query optimization' provides some specificity, but 'analyze performance' is generic enough to conflict with other performance-related skills. It doesn't specify the type of queries (SQL, NoSQL, API) which could cause overlap. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent SQL optimization skill with good coverage of anti-patterns, concrete examples, and a useful error handling table. Its main weaknesses are moderate verbosity (explaining SQL concepts Claude already knows), lack of explicit validation feedback loops in the workflow, and a monolithic structure that could benefit from splitting detailed references into supporting files. The examples are illustrative but could be more complete with actual EXPLAIN output.
Suggestions
Add an explicit validation feedback loop after step 9: 'If the rewritten query returns different results (verify with EXCEPT), revert and re-examine JOIN types and NULL handling before proceeding.'
Trim explanatory parentheticals that describe well-known SQL behavior (e.g., 'forces unnecessary I/O', 'EXISTS short-circuits after the first match') to reduce token usage.
Split the error handling table and detailed examples into separate bundle files (e.g., ERROR_HANDLING.md, EXAMPLES.md) and reference them from the main skill to improve scannability.
Include a complete runnable example with actual EXPLAIN ANALYZE output showing before/after plans, rather than just describing the performance improvement in prose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-written but includes some unnecessary verbosity. Explanations like 'forces unnecessary I/O', 'produces wrong results and poor plans', and general SQL knowledge that Claude already possesses add token overhead. The prerequisites section explains things Claude would know to ask for. However, it's not egregiously padded. | 2 / 3 |
Actionability | The skill provides concrete SQL examples and specific anti-patterns to look for, which is good. However, the instructions are more of a knowledge guide than executable steps—there are no copy-paste-ready scripts or commands for automating the analysis. The examples section provides before/after SQL but lacks complete, runnable test scenarios with EXPLAIN output. | 2 / 3 |
Workflow Clarity | The 10-step sequence is clearly numbered and logically ordered, culminating in testing with EXPLAIN ANALYZE (step 9) and documentation (step 10). However, there's no explicit validation checkpoint or feedback loop—step 9 says to compare but doesn't specify what to do if the rewrite is slower (that's buried in the error handling table). For a workflow involving query rewrites that could produce incorrect results, the validation loop should be more prominent. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources), but it's a monolithic document with no bundle files. The detailed error handling table, extensive examples, and resources could be split into separate reference files. For a skill of this length (~100+ lines of substantive content), some progressive disclosure into supporting files would improve scannability. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.