sql-query-optimizer
Sql Query Optimizer - Auto-activating skill for Data Analytics. Triggers on: sql query optimizer, sql query optimizer Part of the Data Analytics skill category.
32
0%
Does it follow best practices?
Impact
91%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/12-data-analytics/sql-query-optimizer/SKILL.mdQuality
Discovery
0%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 an extremely weak description that is essentially auto-generated boilerplate with no substantive content. It fails on all dimensions: it describes no concrete actions, includes no natural trigger terms, lacks both 'what' and 'when' guidance, and is indistinguishable from other data-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes SQL queries for performance bottlenecks, suggests index additions, rewrites inefficient joins, and explains execution plans.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to optimize SQL queries, improve query performance, fix slow queries, analyze execution plans, or mentions keywords like slow query, query tuning, SQL performance, or database optimization.'
Remove the duplicate trigger term 'sql query optimizer' and replace with diverse natural language variations users would actually say, such as 'slow SQL', 'query performance', 'optimize my query', 'database tuning'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states the skill name 'Sql Query Optimizer' and that it's for 'Data Analytics' without describing what it actually does (e.g., rewrite queries, add indexes, analyze execution plans). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no description of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sql query optimizer' repeated twice. This misses natural user phrases like 'slow query', 'optimize SQL', 'query performance', 'execution plan', 'speed up database query', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Data Analytics' could overlap with many other skills. Without specific actions or file types, it would be difficult to distinguish this from any other SQL or data-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is entirely a placeholder/template with no actual content about SQL query optimization. It contains only self-referential meta-descriptions ('this skill provides assistance for sql query optimizer') without any concrete techniques, code examples, optimization strategies, or actionable guidance. It would provide zero value to Claude when activated.
Suggestions
Add concrete SQL optimization techniques with before/after query examples (e.g., replacing subqueries with JOINs, adding appropriate indexes, using EXPLAIN ANALYZE output interpretation)
Include executable code examples showing common optimization patterns such as index usage, query rewriting, and partitioning strategies
Define a clear workflow for query optimization: 1) Analyze with EXPLAIN, 2) Identify bottlenecks, 3) Apply specific optimization, 4) Validate performance improvement
Replace all meta-description sections ('This skill provides...', 'When to Use...', 'Example Triggers...') with actual instructional content about SQL query optimization
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual SQL query optimization knowledge, techniques, or code. Every token is wasted on boilerplate that tells Claude nothing it doesn't already know. | 1 / 3 |
Actionability | There is zero concrete guidance—no SQL examples, no optimization techniques, no executable queries, no specific commands. The content only describes itself in vague terms like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains no steps whatsoever. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-descriptions with no meaningful structure. There are no references to detailed materials, no links to examples or advanced content, and the sections that exist are purely boilerplate headers with no substantive content. | 1 / 3 |
Total | 4 / 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
933cf26
- 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.