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 description is essentially a placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be indistinguishable from other data or SQL-related skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes SQL queries for performance bottlenecks, suggests index optimizations, 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, speed up a slow query, analyze an execution plan, improve database performance, or review query efficiency.'
Include common keyword variations users might naturally say, such as 'slow query', 'query performance', 'execution plan', 'database optimization', 'SQL tuning', and 'index optimization'.
| 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., analyze query plans, suggest indexes, rewrite slow queries). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sql query optimizer' repeated twice. It misses natural user phrases like 'slow query', 'optimize SQL', 'query performance', 'execution plan', 'index suggestion', or 'speed up database query'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Data Analytics' could overlap with dozens of other skills. Without specific actions or distinct triggers, it would be nearly impossible to distinguish from other SQL or data-related skills. | 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 an empty shell with no substantive content. It consists entirely of boilerplate meta-descriptions that tell Claude about the skill's existence rather than teaching any SQL query optimization techniques. There are no code examples, no optimization strategies (e.g., indexing, EXPLAIN plans, query rewriting), and no actionable guidance whatsoever.
Suggestions
Add concrete SQL optimization techniques with executable before/after query examples (e.g., adding indexes, rewriting subqueries as JOINs, using EXPLAIN ANALYZE output).
Include a step-by-step workflow for diagnosing and optimizing slow queries: identify slow query → run EXPLAIN → analyze bottleneck → apply optimization → validate improvement.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual optimization content such as common anti-patterns, indexing strategies, and query rewriting rules.
Add references to advanced topics like partitioning strategies, materialized views, or database-specific optimizations in separate linked files if needed.
| 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 section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no SQL examples, no optimization techniques, no executable queries, no specific commands. The content only describes what the skill would do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. Claims like 'provides step-by-step guidance' and 'validates outputs' are stated but never substantiated with any actual steps or validation procedures. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed materials, no links to examples or advanced topics, and the sections are redundant rather than progressively informative. | 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
4dee593
- 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.